This error mostly occurs when backing up a Windows server doing a Volume Shadow Copy (VSS) backup of the /CONFIGURATION object
[Critical] From: VBDA@mysys "mysys [/CONFIGURATION]" Time: 8/14/2013 10:29:20 AM
Fallback to legacy filesystem backup was not allowed. Aborting the backup.
The thing is that for /CONFIGURATION backup the code logic is a bit different and from a certain Windows version up VSS is always used. The fix tries to fallback to non-VSS backup the same way as for file system backups or for lower windows versions
If the error occurs on a Windows 2003 system, the only answer is to go into “File System -> WinFS” options, and disable Volume Shadow Copy for the /CONFIGURATION object only
If Windows 2008/Windows 7 or higher, your first check should always be the Application Event log on the Disk Agent machine being backed up, since this is nearly always a Windows issue
Unfortunately, this is a pretty generic error, with several different possible causes, so, here are listed the most common ones
=======================
With or without selecting the Use Shadow Copy option, Data Protector will use Volume Shadow Copy Service (VSS) to backup the configuration for Windows Vista, Windows 7, and Windows Server 2008 .
During an online backup VSS requires mounting the snapshotted volumes in order to revert them back to their proper state.
If automount is disabled, VSS cannot mount the snapshotted volumes as required.
Ref: http://support.microsoft.com/kb/2004712
1. Execute diskpart.exe:
C:\>diskpart
2.Configure the automount option:
DISKPART>automount
Automatic mounting of new volumes disabled.
3. Re-enable:
DISKPART>enable
4.Exit:
DISKPART>exit
To make this effective, a system reboot may be required
=================
There is part of Windows 2008/Windows 7 and higher called the System Reserved partition.
First, it holds the Boot Manager code and the Boot Configuration Database. Second, it reserves space for the startup files required by the BitLocker Drive Encryption feature. If you ever decide to encrypt your system drive using BitLocker, you won’t have to repartition your system drive to make it possible.
By default, this is installed without a Drive letter, and it can't actually be seen anywhere other than in Disk Management
The error can be worked around by assigning a drive letter to the SystemReserved Partition, or by not mounting the System Reserved partition to a NTFS folder, for example
C:\WINDOWS\SYSTEMRESERVEDDISK
====================
The problem may involve where the VSS mirror is being placed, and the snapshot querying the writer status
This is fixed by temporarily changing the location (drive letter) of the Shadow Copy, then changing it right back again
This can either be done from the VSS User Interface (Start -> Run -> vssuirun), or from the command line using the 'vssadmin' command. Since this is not directly related to Data Protector, this should be done by the Windows Administrator
=================
The VDS (Virtual Disk Service) may be running, which could impare the VSS service from initializing properly
=================
There were Data Protector Disk Agent patches issued to correct this problem, on DP 6.21 and 7.03. Make sure that your Disk Agent patches are up to date, and, that you are on the latest patch bundle