I was just reviewing my master (Windows 2008 Server) backups today and I found to my horror things are not at all correct.
Seems that my most recent backups are again failing because Windows erroneously regards by P: as a Critical Volume. P: however contains no OS information, nor swap file nor hibernation file relevent to the OS. Indeed as a test I can boot the computer without the P:
Lets look at the problem:
C:\Windows\system32>wbadmin get versions
wbadmin 1.0 - Backup command-line tool
(C) Copyright 2004 Microsoft Corp.
Backup time: 2009-01-19 19:53
Backup target: Fixed Disk labeled backup(Y:)
Version identifier: 01/19/2009-18:53
Can Recover: Volume(s), File(s), Application(s), Bare Metal Recovery, System State
Backup time: 2009-02-09 10:15
Backup target: Fixed Disk labeled backup(Y:)
Version identifier: 02/09/2009-09:15
Can Recover: Volume(s), File(s), Application(s)
So the backup of 9th February is not bare metal recoverable because although it was made with the command
wbadmin start systemstatebackup -backuptarget:y:
at the time of the command the P: existed and was online. Let me look at my P: for signs that it is a Critical Volume:
DISKPART> select disk 5
Disk 5 is now the selected disk.
DISKPART> attributes disk
Read-only : No
Boot Disk : No
Pagefile Disk : No
Hibernation File Disk : No
Crashdump Disk : No
DISKPART> list vol
Volume ### Ltr Label Fs Type Size Status
Volume 6 P code NTFS Partition 1397 GB Healthy
DISKPART> select volume 6
Volume 6 is the selected volume.
DISKPART> attributes volume
Read-only : No
Hidden : No
No Default Drive Letter: No
Shadow Copy : No
Therefore I have absolutely no idea why Windows considers this disk critical?
So what is a Critical Volume? Here is a good quote:
System state includes more data on Windows Server 2008 than in the Windows Server 2003 operating system. In Windows Server 2008, the exact system components which make up the system state depend on the configuration of the computer. System state data includes at least the following and may include additional data that is configuration dependent:
- Registry.
- COM+ class registration database.
- Boot files, including system files.
- Certificate Services database.
- Active Directory Domain Services.
- SYSVOL directory.
- Cluster Service information.
- Microsoft Internet Information Services (IIS) meta-directory.
- System files that are under Windows File Protection (WFP).
System state can be backed up separately at the command prompt only (using PowerShell):
wbadmin start systemstatebackup -backupTarget: [-quiet]
Critical volumes (volumes storing system components including NTDS.dit, SYSVOL and %windir%) can be backed up. On domain controllers which are using the DFS Replication service for SYSVOL replication (i.e. Windows Server 2008 domain functional level), the DFS Replication service co-operates with Windows Server Backup in order to backup the SYSVOL folder.
So here is the terribly kludgy workaround:
a) Locate the P: drive and set it offline
diskpart
DISKPART> select disk 5
Disk 5 is now the selected disk.
Microsoft DiskPart version 6.0.6001
DISK - Offline a disk that is currently marked as online.
DISKPART> offline disk
DiskPart successfully offlined the selected disk.
b) Start the enhanced backup
C:\Windows\system32>wbadmin start backup -allcritical -backuptarget:y:
wbadmin 1.0 - Backup command-line tool
(C) Copyright 2004 Microsoft Corp.
Retrieving volume information...
This would backup volume boot(C:) to y:.
Do you want to start the backup operation?
[Y] Yes [N] No Y
Running backup of volume boot(C:), copied (99%).
Backup of volume boot(C:) completed successfully.
Backup completed successfully.
Summary of backup:
------------------
Backup of volume boot(C:) completed successfully.
c) online back the troublesome disk
DISKPART> online disk
DiskPart successfully onlined the selected disk.
d) check backup it because I am paranoid
Backup time: 2009-02-18 22:26
Backup target: Fixed Disk labeled backup(Y:)
Version identifier: 02/18/2009-21:26
Can Recover: Volume(s), File(s), Application(s), Bare Metal Recovery, System State
So overall if somebody can enlighten me how to detect why Windows 2008 server believes my P: is a system volume, and then how to correct it, I'd be most grateful.