cancel
Showing results for 
Search instead for 
Did you mean: 

Failed WORM backup (status 4207)

perez_cmz
Level 6

I checked the definition for this status code in the reference guide, and confirmed the client can communicate with the master. This client has been successfully backed up previously using a regular Windows type policy.

The following is the detailed status for the initial failed job. It's failed twice already.

Can anyone offer some guidance ?


03/08/2017 06:22:06 - Info nbjm (pid=2846) starting backup job (jobid=244750416) for client sv193571.ztb.icb.commerzbank.com, policy US_NYK_WIN_WORM_TEST, schedule Full_WORM
03/08/2017 06:22:06 - Info nbjm (pid=2846) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=244750416, request id:{76925B90-03F1-11E7-8B33-F9BF3E50BA33})
03/08/2017 06:22:06 - requesting resource WORM_NYK_LTO6
03/08/2017 06:22:06 - requesting resource nmausp01.zit.commerzbank.com.NBU_CLIENT.MAXJOBS.sv193571.ztb.icb.commerzbank.com
03/08/2017 06:22:06 - requesting resource nmausp01.zit.commerzbank.com.NBU_POLICY.MAXJOBS.US_NYK_WIN_WORM_TEST
03/08/2017 06:22:07 - awaiting resource WORM_NYK_LTO6. No drives are available.
03/08/2017 06:25:20 - Waiting for scan drive stop IBM.ULT3580-TD6.007, Media server: mediany1p01.zit.commerzbank.com
03/08/2017 06:25:22 - granted resource  nmausp01.zit.commerzbank.com.NBU_CLIENT.MAXJOBS.sv193571.ztb.icb.commerzbank.com
03/08/2017 06:25:22 - granted resource  nmausp01.zit.commerzbank.com.NBU_POLICY.MAXJOBS.US_NYK_WIN_WORM_TEST
03/08/2017 06:25:22 - granted resource  NYW002
03/08/2017 06:25:22 - granted resource  IBM.ULT3580-TD6.007
03/08/2017 06:25:22 - granted resource  WORM_NYK_MS1_LTO6
03/08/2017 06:25:22 - estimated 0 kbytes needed
03/08/2017 06:25:22 - Info nbjm (pid=2846) started backup (backupid=sv193571.ztb.icb.commerzbank.com_1488972322) job for client sv193571.ztb.icb.commerzbank.com, policy US_NYK_WIN_WORM_TEST, schedule Full_WORM on storage unit WORM_NYK_MS1_LTO6
03/08/2017 06:25:25 - started process bpbrm (pid=2739)
03/08/2017 06:25:28 - Info bpbrm (pid=2739) sv193571.ztb.icb.commerzbank.com is the host to backup data from
03/08/2017 06:25:28 - Info bpbrm (pid=2739) reading file list for client
03/08/2017 06:25:29 - connecting
03/08/2017 06:25:31 - Info bpbrm (pid=2739) starting bpbkar on client
03/08/2017 06:25:31 - connected; connect time: 0:00:00
03/08/2017 06:25:32 - Info bpbkar (pid=7148) Backup started
03/08/2017 06:25:32 - Info bpbrm (pid=2739) bptm pid: 2765
03/08/2017 06:25:32 - Info bpbkar (pid=7148) change time comparison:<disabled>
03/08/2017 06:25:32 - Info bpbkar (pid=7148) archive bit processing:<enabled>
03/08/2017 06:25:32 - Info bptm (pid=2765) start
03/08/2017 06:25:34 - Info bpbkar (pid=7148) not using change journal data for <C:\>: not enabled
03/08/2017 06:25:35 - Info bptm (pid=2765) using 262144 data buffer size
03/08/2017 06:25:35 - Info bptm (pid=2765) setting receive network buffer to 262144 bytes
03/08/2017 06:25:35 - Info bptm (pid=2765) using 32 data buffers
03/08/2017 06:25:36 - Info bptm (pid=2765) start backup
03/08/2017 06:25:37 - Info bptm (pid=2765) backup child process is pid 2770
03/08/2017 06:25:37 - Info bptm (pid=2765) Waiting for mount of media id NYW002 (copy 1) on server mediany1p01.zit.commerzbank.com.
03/08/2017 06:25:37 - mounting NYW002
03/08/2017 06:26:05 - Info bptm (pid=2765) media id NYW002 mounted on drive index 7, drivepath /dev/nst2, drivename IBM.ULT3580-TD6.007, copy 1
03/08/2017 06:26:06 - mounted NYW002; mount time: 0:00:29
03/08/2017 06:26:06 - positioning NYW002 to file 1
03/08/2017 06:26:30 - positioned NYW002; position time: 0:00:24
03/08/2017 06:26:30 - begin writing
03/08/2017 06:40:15 - Error bpbrm (pid=2739) from client sv193571.ztb.icb.commerzbank.com: ERR - failure reading file: C:\ProgramData\Solarwinds\JobEngine.v2\SchedulerResults\2e86add6-8e01-48eb-b041-b5760a75e8b0.result (WIN32 2: The system cannot find the file specified. )
03/08/2017 06:40:17 - Error bpbrm (pid=2739) from client sv193571.ztb.icb.commerzbank.com: ERR - Snapshot Error while reading file: GLOBALROOT\Device\HarddiskVolumeShadowCopy2\ProgramData\Solarwinds\JobEngine.v2\SchedulerResults\2e86add6-8e01-48eb-b041-b5760a75e8b0.result
03/08/2017 06:40:17 - Critical bpbrm (pid=2739) from client sv193571.ztb.icb.commerzbank.com: FTL - Backup operation aborted!
03/08/2017 06:40:20 - Error bptm (pid=2765) media manager terminated by parent process
03/08/2017 06:40:30 - Error bpbrm (pid=2739) could not send server status message
03/08/2017 06:40:31 - Info bpbkar (pid=7148) done. status: 156: snapshot error encountered
03/08/2017 06:40:31 - end writing; write time: 0:14:01
03/08/2017 06:40:37 - Info bpbrm (pid=17806) Starting delete snapshot processing
03/08/2017 06:40:41 - Info bpfis (pid=24404) Backup started
03/08/2017 06:40:41 - Warning bpbrm (pid=17806) from client sv193571.ztb.icb.commerzbank.com: WRN - cannot open d:\Apps\VERITAS\NetBackup\online_util\fi_cntl\bpfis.fim.sv193571.ztb.icb.commerzbank.com_1488972322.1.0
03/08/2017 06:40:42 - Info bpfis (pid=24404) done. status: 4207

03/08/2017 06:40:42 - Info bpfis (pid=24404) done. status: 4207: Could not fetch snapshot metadata or state files
snapshot error encountered  (156)

1 ACCEPTED SOLUTION

Accepted Solutions

Nicolai
Moderator
Moderator
Partner    VIP   

VSS ran out of space during backup, refer to this tech note and scroll to the resolution. It describes to to adjust Windows VSS disk size.

VSS is a copy on write operation, that require a disk buffer. If this buffer run out of space during backup, Netbackup will fail with status 156.

http://www.veritas.com/docs/000040337

View solution in original post

3 REPLIES 3

Michal_Mikulik1
Moderator
Moderator
Partner    VIP    Accredited Certified

Hello,

seems not to be related to "WORM" in any way. Rather VSS problem on the client I think. Check Event Viewer for VSS errors on the client, also check free disk space there, too.

Also "vssadmin list writers" if there are not some failing writers

Regards

Nicolai
Moderator
Moderator
Partner    VIP   

VSS ran out of space during backup, refer to this tech note and scroll to the resolution. It describes to to adjust Windows VSS disk size.

VSS is a copy on write operation, that require a disk buffer. If this buffer run out of space during backup, Netbackup will fail with status 156.

http://www.veritas.com/docs/000040337

Thank you Nicolai