There are various reasons why the WSB plug-in could fail, such as:
SymptomOne such reason is that the required VSS writer is missing. The System State plug-in using WSB fails during the back up with the following error in the Server Edition backup log:
To confirm the staus of the System State backup and help determine the failure, run the following command:
C:\>wbadmin get status
Example of output:
Note the last line in the output above.
The System State VSS writer is not found and is the cause of the failure.
Full Microsoft Knowledge Base article: http://support.microsoft.com/kb/2009272
To resolve this issue, type the following commands from an elevated Command Prompt:
Run the following command to verify that the system writer is now listed:
SymptomAnother reason why the WSB plug-in could fail is specific to Windows 2008 R2 machines running within VMWare, and relates to the SCSI controller drivers. The System State plug-in using WSB fails during the back up (after some time) with the following error in the Server Edition backup log:
In the event logs, an event ID 517 sourced from 'Backup' is logged, containing the following:
This issue is specific to Windows 2008 R2 machines running within VMware, and relates to the SCSI controller drivers.
More details can be found on the following Technet page:
Further discussion of the problem can be found here:
SymptomSystem State backup fails at the SplitVHD stage with the following messages:
The backupservice.log file shows a stack trace of the file collection error, but no other details:
2012-06-18 11:16:52,372 ERROR errorlog - could not create backup: File collection interruptedThe SplitVHD.log shows a "Substream extends beyond end of parent stream" error:
Reading 4,481 VHD allocation blocks
CauseSplitVHD is failing as the Master File Table (MFT) of the VHD file is corrupt. The most likely cause of this is due to corruption in the MFT of the actual system volume. Running a ChkDsk in read-only mode (which is possible without rebooting) will reveal if this is the cause of the problem.
Run the command "chkdsk" from the Command Prompt to run a read-only check.
SolutionIf errors are found, run "chkdsk" with "/f" to fix errors.
More details can be found on the following MS Technet page: http://technet.microsoft.com/en-us/library/cc730714%28v=ws.10%29.aspx
When the MFT of the system volume is fixed, allow a fresh backup to run. After Windows Server Backup (WSB) writes out the VHD to disk, SplitVHD will be able to read the .VHD file successfully and split this into its component parts. This in turn will allow Attix5 Pro to de-duplicate the contents of the VHD and back up successfully.
SymptomThe System State (using WSB) plug-in is installed, but is not shown in the Backup Client's plug-in menu. Therefore it cannot be configured.
CauseJava is used to detect the operating system version, and this is used to determine which System State plug-in is loaded. If Java is an older version it might identify the operating system incorrectly, e.g. it might identify Windows 2008 as Windows Vista. The incorrect operating system is then presented to Attix5 Pro which does not have a corresponding System State plug-in for the OS and therefore does not load one.
SolutionIf Java is an older version, the solution is to update the Java installation so that the correct OS version is detected. With the correct OS detected, Attix5 Pro loads the correct System State plug-in. If the Java version is earlier than 1.6.0_16, Windows 2008 is identified as Windows Vista. Java will need to be updated to 1.6.0_16 or a later Java 6 version.
Note: Java 7 is not yet supported by Attix5 Pro.
Follow the solution section of FAQ 141 for details on updating Java: http://v6.attix5.com/kb/?View=entry&EntryID=141.