Backup of shadow copy components getting status 1

Article:TECH184153  |  Created: 2012-03-19  |  Updated: 2012-03-19  |  Article URL http://www.symantec.com/docs/TECH184153
Article Type
Technical Solution

Issue



A backup of a Windows 2008 R2 server is getting a status code 1 on a "Shadow Copy Components" backup.


Error



3:31:26.620 PM: [5156.11120] <2> ov_log::V_GlobalLog: INF - Status VSS_E_BAD_STATE (0x80042301) getting writer metadata count in SHADOW::GenerateLogicalBackupDirectoryTree
3:31:26.620 PM: [5156.11120] <2> ov_log::V_GlobalLog: INF -
3:31:26.620 PM: [5156.11120] <2> ov_log::V_GlobalLog: INF - ==================================================================================================
3:31:26.620 PM: [5156.11120] <2> ov_log::V_GlobalLog: INF -     ****** Tree - "SHADOW::LogicalDirectoryTree" ******
3:31:26.620 PM: [5156.11120] <2> ov_log::V_GlobalLog: INF - -----------------------------------------------------------------------------------
3:31:26.620 PM: [5156.11120] <2> ov_log::V_GlobalLog: INF - ==================================================================================================
3:31:26.620 PM: [5156.11120] <2> ov_log::V_GlobalLog: INF -
3:31:26.620 PM: [5156.11120] <2> ov_log::V_GlobalLog: INF - Status FS_WRITER_METADATA_FAILURE (0xE000FEC9) generating logical directory tree when attaching to Shadow?Copy?Components Dle
3:31:26.620 PM: [5156.11120] <2> ov_log::V_GlobalLog: INF -   AD:Status FS_WRITER_METADATA_FAILURE (0xE000FEC9) attaching 'Shadow?Copy?Components' in SystemState::InitializeShadowCopy:359
3:31:26.620 PM: [5156.11120] <2> ov_log::V_GlobalLog: INF -   AD:Status FS_WRITER_METADATA_FAILURE (0xE000FEC9) initializing Shadow Copy in SystemState::AttachToDLE:592
3:31:26.620 PM: [5156.11120] <2> ov_log::V_GlobalLog: ERR - BEDS_AttachToDLE():FS_AttachToDLE() DeviceName:'System?State' BackupReason:0x2 Failed! (0xE000FEC9:A failure occurred accessing the Writer metadata.
3:31:26.620 PM: [5156.11120] <2> ov_log::V_GlobalLog: INF -  v_beds::V_FindFirst() EXIT Name: bRC:false LastError:0xFFFFFEC9:0xa000fec9 (2684419785)
3:31:26.620 PM: [5156.11120] <4> tar_base::V_vTarMsgW: INF - tar message received from dos_backup::tfs_startdir
3:31:26.620 PM: [5156.11120] <2> tar_base::V_vTarMsgW: ERR - Unable to backup System State or Shadow Copy. Please check the state of VSS and associated Writers.3:31:26.620 PM: [5156.11120] <4> tar_backup::backup_done_state: INF - number of file directives not found: 3
3:31:26.620 PM: [5156.11120] <4> tar_backup::backup_done_state: INF -     number of file directives found: 2
3:31:26.620 PM: [5156.11120] <2> tar_base::V_vTarMsgW: INF - Client completed sending data for backup
3:31:26.620 PM: [5156.11120] <4> tar_base::stopKeepaliveThread: INF - waiting for keepalive thread to exit ...
3:31:26.620 PM: [5156.11120] <4> tar_base::stopKeepaliveThread: INF - keepalive thread has exited. (reason: WAIT_OBJECT_0)
3:31:26.620 PM: [5156.11120] <8> tar_backup_tfi::cleanupTemp: WRN - will not cleanup 'temp' directory, debug level(s) are too high
3:31:26.620 PM: [5156.11120] <2> tar_base::V_vTarMsgW: INF - EXIT STATUS 69: invalid filelist specification


Environment



Windows 2008 R2 server running NetBackup 7.1.0.2.


Cause



This issue was caused by a "Path to Executable" containing a foreign character.

- File List: Path = d:\oracle\11g\middleware\server_10.3\common\emnodemanager\..\..\server\bin, Filespec = beasvc.exe

This was found by reviewing the writer output of the command below.

Issue the following commands in order:

1. Open a command prompt and issue:

diskshadow /l <logfile> Example: diskshadow /l C:\writersout.txt

2. list writers detailed (it will scroll up the screen, but also log into the specified logfile - could take 2-3 minutes to complete)

3. Exit

4. Collect / Examine the specified logfile


Solution



After finding the problem service correct the "Path to Executable" using the absolute path to the executable.

Start\run\services.msc and then locate the problem service.  Right click\properties and then modify the path to executable of the problem executable.

 

 




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


Terms of use for this information are found in Legal Notices