Posted 15 March 2012 - 06:31 AM
What exactly is an "archive backup?" My machines back up automatically daily, although sometimes I kick off a manual backup, and they're all set to be managed automatically. And yet this error comes and goes on most of the machines.
The alert that bugs me more is the "A new hard drive should be backed up." This little bundle of joy shows up on both my work-issued laptop and my personal one, and it used to show up on what is now the Windows 8 box (which hasn't been connected to the server).
It didn't take me long to realize that the "new" hard drive was the USB drive(s) attached to each PC were the guilty parties. The best I can figure is that because, unlike "internal" (SATA/eSATA/SAS/IDE) disks, USB disks encrypted with BitLocker do not auto-unlock at boot time even when auto-unlock is enabled on them. They unlock when the user who enabled auto unlock logs on. Since the WHS services start before the user logs on, I'm guessing the service sees a drive letter/mount point but the file system is unreadable (since it's locked).
WHS v1 took this in stride, and just logged an error if the server tried to kick off backup and the disk was locked. WHS 2011, however, notifies the server, which lovingly disables backup on that disk, so the next time the disk is unlocked, the alert appears. The only way to fix it is to go into the Dashboard and re-enabled backup on that disk -- it apparently isn't smart enough to see that the disk is back. If they can automatically disable it, why can't they automatically re-enable it?
Interestingly, if I boot the machine without the disk(s) attached, log in and attach the disk(s) after logon, this problem does not occur.
Some might say the easy solution is to not use BitLocker, but I say nay-nay. That's akin to leaving a Mercedes parked in a rough neighborhood with the keys in it and the windows down.
Owner, Dojo North Software, LLC