A backup of the Shadow Copy Components of Windows 2008 server / Windows Vista fails with error 0xE000FEDD: A failure occurred accessing the object list.

Article:TECH87247  |  Created: 2009-01-07  |  Updated: 2014-01-09  |  Article URL http://www.symantec.com/docs/TECH87247
Article Type
Technical Solution

Product(s)

Issue



A backup of Shadow Copy Components of Windows 2008 server / Windows Vista/ Windows 7 fails with error "can't open object: Shadow Copy Components:\System State\Active Directory\E:_NTDS\ntds (BEDS 0xE000FEDD: A failure occurred accessing the object list.) The requested operation was partially successful(1)".


Error



Can't open object: Shadow Copy Components:\System State\Active Directory\E:_NTDS\ntds (BEDS 0xE000FEDD: A failure occurred accessing the object list.) The requested operation was partially successful(1).

When a backup of Shadow Copy Components fails on Windows Vista, Windows 7 and Windows 2008 server, the BPBKAR log may show the following errors: 
2:50:44.473 PM: [1476.1864] <2> ov_log::V_GlobalLog: INF - v_beds::V_FindNext() EXIT Name: bRC:false LastError:0xFFFFFE07:0xa000fe07 (2684419591)
2:50:44.473 PM: [1476.1864] <2> ov_log::V_GlobalLog: INF - v_beds::V_FindNext() EXIT Name: bRC:false LastError:0xFFFFFE07:0xa000fe07 (2684419591)
2:50:46.407 PM: [1476.1864] <2> <FROM BEDS>: Calling VssSnapshotVolume::GetBackupComponentDocument in SHADOW::GenerateBackupComponentDocument
2:50:46.407 PM: [1476.1864] <2> <FROM BEDS>: VssSnapshotVolume::GetBackupComponentDocument: Error. No data in bstrBCDXML_!
2:50:46.407 PM: [1476.1864] <2> <FROM BEDS>: Status FAILURE (0x00000001) returned saving Backup Component Document in SHADOW::GenerateBackupComponentDocument
2:50:46.407 PM: [1476.1864] <2> <FROM BEDS>: Status FS_BACKUP_COMPONENT_DOCUMENT_FAILENT_FAILURE (0xE000FECB) generating Backup Component Document in SHADOW::OpenVcb
2:50:46.407 PM: [1476.1864] <2> ov_log::V_GlobalLogEx: ERR - beds_base::V_OpenForRead():FS_OpenObj() Failed! (0xE000FECB: A failure occurred accessing the backup component document.)
2:50:46.407 PM: [1476.1864] <4> tar_base::V_vTarMsgW: INF - tar message received from dos_backup::tfs_readopen
2:50:46.407 PM: [1476.1864] <2> tar_base::V_vTarMsgW: WRN - can't open object: Shadow Copy Components: (BEDS 0xE000FECB: A failure occurred accessing the backup component document.

Environment



Windows 2008 /Windows Vista/ Windows 7


Solution



The error is quite generic in nature and is not specific to Windows 2008 / Win7 or Win Vista OS. It may occur on Win2003 x86 / 64-bit / R2 platforms as well. Usually a reboot of the client should reset the VSS writers and should fix the problem. 

If unresolved, we need to determine if the issue could be with the OS, file-system or the VSS writers. Run a backup using the Windows 2008 built-in backup tool called WBAdmin. The procedures to run a backup using WBAdmin is discussed below in this document.

Applying Windows 2008 Service pack 2 has been known to resolve this error. 
 
Check for these services on Windows 2008 server / Windows VistaEnsure that the 'Startup' type is set to MANUAL for following Windows Services:
Microsoft Software Shadow Copy Provider (SVPRV)
Volume Shadow Copy (VSS)
Block Level Backup Engine service (WBEngine)
 

Additional information on using WBAdmin on Windows 2008 Server:
WBAdmin CLI of Windows server 2008 can be used for testing the backup of "Shadow Copy Components" and for testing VSS functionality. (The wbadmin command replaces the ntbackup command that was released with previous versions of Windows.)
 
How does WBAdmin Backup work in Windows Server 2008? 
  • Windows Server 2008 Backup (and its command line interface wbadmin.exe) are the new block-level backup infrastructure built into Microsoft's Windows Server 2008 and Windows Vista operating systems.
  • The wbadmin command replaces the ntbackup command that was released with previous versions of Windows.
  • Using WBAdmin you can only select entire volumes for backup, not individual files and directories.
  • The resulting backup file is a VHD file.
  • The entire backup system is based on VSS.
  • The backup is a selective image - not a forensic clone - of the source volumes. This means that things like blank space, the page file, hibernate file, and certain folders are not backed up.
  • Can only select local volumes to backup, not network shares
How to execute a backup using WBAdmin?
 
Example 1: 
wbadmin start systemstatebackup -backupTarget:e:
(A system state backup to a shared network folder is not supported.)
Example 2: 
wbadmin start backup -include:c:,d:,e: -backupTarget:\\SERVER\SHARE -quiet
(A local drive backup to a shared network folder is supported. Optionally, you can use the -user and -password options to explicitly specify the username and password to use when connecting to the share.)
Example 3 
wbadmin start backup -vssFull -include:c:,d: -backupTarget:e:
(You may use the -vssFull parameter to check the functionality of VSS writers. If specified, performs a full backup using the Volume Shadow Copy Service (VSS). Each file's history is updated to reflect that it was backed up.)
Note: The wizards that Microsoft deploy with the operating system will only allow you to backup to USB, Firewire connected hard drives, locally connected hard drives or a Universal Naming Convention (UNC) path to a remote shared folder (\\<servername>\<sharename>\). Backing up to NAS device is not possible.
 
For a complete list of available parameters, refer to  http://technet.microsoft.com/en-us/library/cc742083.aspx
For a complete overview of WBAdmin, refer to  http://technet.microsoft.com/en-us/library/cc754015.aspx

For additional information kindly refer the related document section below.




Legacy ID



317208


Article URL http://www.symantec.com/docs/TECH87247


Terms of use for this information are found in Legal Notices