Upwards with SBS – SBSisyphus’ Weblog

Entries categorized as ‘Disaster & Recovery’

SBS Backup ‘Completes’ & Labeled Green ‘Successful’ – Exchange Information Store Database Is Missing

September 2, 2008 · Leave a Comment

At the tail end of last week I discovered a SBS 2003 (R2) Backup ‘gotcha’ /bug that I think will affect others.  The triggering condition is a business has that been running the SBS Backup but didn’t initially configure Exchange.  Later Exchange is turned on by re-running the CEICW.  Furthermore the SBS Backup continues to complete and the Monitoring Report indicates that it is ‘complete’ and labeled a green ’successful’.  This is a false-positive in that the backup script is completing its tasks but is missing the Exchange First Storage Group database store backup.  Why?  The SBS Backup script is created upon running the SBS Backup Wizard.  Future wizard configuration does not in itself add the needed backup set.  Instead the SBS Backup must be fully disabled and then re-enable in order for the .bks script file to be rebuilt.

I discovered this situation by running the Exchange Best Practices Analyzer tool which reported that the Information Store database hadn’t a recent Full Backup date.

Categories: Disaster & Recovery · Exchange · SBS

Drive Formatting 16K Cluster to Avoid Loss of Volume Shadow Copy Snapshots

July 21, 2008 · 1 Comment

Recommended Reading: Shadow copies may be lost when you defragment a volume
http://support.microsoft.com/kb/312067/ – MS document on VSS 16KB cluster best practice

Well, after seeing System Error 25 VolSnap too many times and realizing each time it appears all  Volume Shadow Copy snapshots were being dumped, I decided to dig into this.  Why?  Because those VSS snapshots are very valuable safety nets that users rely on.  Things like redirected My Documents …etc are highly valuable and worth having an extra version to fall back to.

What I discovered is that whenever a defragmenter runs against the default 4 KB (SBS/Win2k3) cluster size these events occur.  I experienced this testing out Diskeeper and then PerfectDisk (Raxco) but also see this when running the native Microsoft defragmenter.  Further research shows that the cluster size needs to be 16 KB for VSS.

So next time you create a data partition my best practice advise to you is to raise the cluster size up from the default to 16 KB (or a greater size).

Although this blog was written a couple of years ago for Windows Server 2003 this still applies in the Server 2008 product.  How do I know?  I asked the Server 2008 VSS team in their blog at the time of launch earlier this year.  What was amazing is that they gave me the impression by the tone of their response that didn’t seem to understand that this issue was relevant or significant.

Here’s the 3/24/2008 response I got from Greg Jacklin via Jim Benton:

“Although volsnap and defrag/ntfs do their best to get along, it is still
best to format with a 16K cluster size for performance.
-Greg”

BTW if you think your heard about this before but you can’t remember where perhaps it was via Wayne Small or Microsoft.  Below are these historical references:

 

    There are some other planning & “hot fix” articles from MS that address some aspects of snapshot dumping; nevertheless, remember that the root cause is that your cluster size isn’t large enough.

Overview Info:

 

Hotfixes:

Categories: Admin Tools & Tips · Disaster & Recovery · SBS · Windows 2008 · Windows Server 2003

Wow! a $1,132 credit charge – fraud alert easy safety net

March 26, 2008 · Leave a Comment

Albeit a non-SBS topic – I thought what I’ve learned this week to be a useful story that may help some of you. Yes, besides all the other recent issues effecting me like the flooded basement, I received an alert last Friday evening on my phone that a large purchase had been placed on my credit card. What I discovered was that a $1,132.92 item was added to my card from Dell Online.

Since I and the Mrs. have a joint account (and we’ve done well that way for 8 years) I wasn’t too aroused but still was curious. So first thing Saturday morning I saw the accompanying email alert I also arranged to be sent to me in the event anything over $200 gets charged. For the most part this has been relatively painless as I don’t generally spend that much at any given time and when I do I know what to expect. It’s my Chase safety net.

So by this time I knew this wasn’t from me or Mrs. DUIT but I thought maybe the database at Dell had merely strayed across accounts. Although that would be a bad thing, even worse is someone actually calling Dell, placing an order, and verifying it. The Dell rep told me that was what occurred and it was a projector sent to:

Amy Martin
218 Country View Rd
Monticello, Arkansas 71655
( 716) 716-7165

The zip code was legitimate to the address so this was turning interesting.

You notice anything funny about the phone number and the zip code? Me too but apparently Dell didn’t. In any case by Saturday morning Dell had already shipped the item and they claimed they had no recourse in stopping the shipment. I asked if they were going to contact the destination’s local law enforcement? The answer was “No”. I was disappointed at this point as I wanted some satisfaction in knowing this thief would be thwarted but it was not to be. Later I was passed to someone else in Dell who offered reassurance, polite “we are sorry for your inconvenience” apologies, and what else could they really say? A case was opened up to formalize the affair and then that was it. An email arrived with this information and that was that.

Fraud was happening and I needed to stop my ID theft ASAP; so I contacted Chase Bank and did just that. Additionally I discovered through trial and error that of the three credit reporting companies, Transunion had a very simple and effective telephone “fraud alert” issuance service. 1-800-680-7289 This took less than 5 minutes to complete and they would notify the other two agencies, Equifax & Experian. This did not require me giving any reason and anyone could do this at any time even right now. This lasts for 90 days and if I want I can call again to refresh it indefinitely. This is the exact same service that companies such as LifeLock charge to maintain.

The benefit to the fraud alert is that if someone actually has my ID they cannot open any lines of credit without a phone call being first made directly to me. The net effect is safe credit today and Chase is issuing me new credit cards that will arrive sometime this week in time to reconfiguring my online bill payment system for the end of month blood-letting.  It’s an inconvenience but it could have been far worse exponentially.

From the initial text alert setup through Chase’s online services, to the Transunion fraud alert, to using www.live.maps.com to check the address, to receiving verification from Dell via email, to regaining access to my credit online immediately by phone to Chase …without technology this would have been so much worse. Technology saved the day.

To summarize:

1-800-680-7289

five minutes of phone pad answers places a 90 day fraud alert at all three US credit reporting agencies – also if you want your annual free credit report (all three agencies) go to https://www.annualcreditreport.com

Categories: Disaster & Recovery · Security

DriverQuery – Vista, Windows 2003, XP

January 1, 2008 · Leave a Comment

When information is power and you want information on drivers.  Follow the link to the article for some enhanced instructions on how using this in PowerShell gives you even more details (see comments).

DriverQuery

This little gem might seem like a font end to a PowerShell command, but for those not ready to bite off on PowerShell, here you go. This command line tools lets you display a list of installed device drivers. You’ll also find this in Windows 2003 and Windows XP.

DRIVERQUERY [/S system [/U username [/P [password]]]] [/FO format] [/NH] [/SI] [/V]

/S – optionally specifies a remote system to which you may connect
/U [domain\]user – optionally specifies the user context under which the command should be executed (if no domain is specified, current is assumed)
/P [password] – if specifying an alternate user, this argument may be used to specify the password for that user. If required and not specified, a password will be requested.
/FO format – optionally specifies the type of output to display (TABLE, LIST or CSV). Default is TABLE.
/NH – optionally used to indicate that a Column Header for TABLE and CSV output should not be provided
/SI – optionally provides information about signed drivers
/V – displays verbose output (not valid for signed drivers)

DriverQuery – Vista

Categories: Disaster & Recovery · Vista · Windows Server 2003 · XP
Tagged: , , ,