I am continuously receiving the same error 156

[ambitiousgirl]

I am continuously receiving the same error 156 when completing certain backups. I don't know what to do to resolve the error. If someone could please help. I am a new user.

12/14/2011 8:53:13 PM - estimated 598094401 Kbytes needed
12/14/2011 8:53:14 PM - started process bpbrm (15988)
12/14/2011 8:53:36 PM - connecting
12/14/2011 8:53:53 PM - connected; connect time: 00:00:17
12/14/2011 8:54:00 PM - mounting 0009L1
12/14/2011 8:54:36 PM - mounted; mount time: 00:00:36
12/14/2011 8:54:36 PM - positioning 0009L1 to file 44
12/14/2011 8:57:05 PM - Error bptm(pid=15668) ioctl (MTWEOF) failed on media id 0009L1, drive index 1, The physical end of the tape has been reached. (1100) (bptm.c.21330)
12/14/2011 8:57:05 PM - Error bptm(pid=15668) FROZE media id 0009L1, could not write tape mark to begin new image
12/14/2011 8:57:05 PM - current media 0009L1 complete, requesting next resource Any
12/14/2011 8:57:43 PM - granted resource 0022L1
12/14/2011 8:57:43 PM - granted resource IBM.ULTRIUM-TD2.001
12/14/2011 8:57:43 PM - granted resource glc-apps-01-hcart2-robot-tld-0
12/14/2011 8:57:43 PM - mounting 0022L1
12/14/2011 8:58:20 PM - mounted; mount time: 00:00:37
12/14/2011 8:58:20 PM - positioning 0022L1 to file 42
12/14/2011 9:00:24 PM - Error bptm(pid=15668) ioctl (MTWEOF) failed on media id 0022L1, drive index 1, The physical end of the tape has been reached. (1100) (bptm.c.21330)
12/14/2011 9:00:24 PM - Error bptm(pid=15668) FROZE media id 0022L1, could not write tape mark to begin new image
12/14/2011 9:00:24 PM - current media 0022L1 complete, requesting next resource Any
12/14/2011 9:01:02 PM - granted resource 0007L1
12/14/2011 9:01:02 PM - granted resource IBM.ULTRIUM-TD2.001
12/14/2011 9:01:02 PM - granted resource glc-apps-01-hcart2-robot-tld-0
12/14/2011 9:01:02 PM - mounting 0007L1
12/14/2011 9:01:40 PM - mounted; mount time: 00:00:38
12/14/2011 9:01:40 PM - positioning 0007L1 to file 4
12/14/2011 9:03:03 PM - positioned 0007L1; position time: 00:01:23
12/14/2011 9:03:03 PM - begin writing
12/15/2011 8:59:51 AM - current media 0007L1 complete, requesting next resource Any
12/15/2011 8:59:51 AM - current media -- complete, awaiting next media Any Reason: Drives are in use, Media Server: glc-apps-01,
  Robot Number: 0, Robot Type: TLD, Media ID: N/A, Drive Name: N/A,
  Volume Pool: File_Pool, Storage Unit: glc-apps-01-hcart2-robot-tld-0, Drive Scan Host: N/A
 
12/15/2011 9:00:31 AM - granted resource 0086L1
12/15/2011 9:00:31 AM - granted resource IBM.ULTRIUM-TD2.001
12/15/2011 9:00:31 AM - granted resource glc-apps-01-hcart2-robot-tld-0
12/15/2011 9:00:31 AM - mounting 0086L1
12/15/2011 9:01:08 AM - mounted; mount time: 00:00:37
12/15/2011 9:01:08 AM - positioning 0086L1 to file 1
12/15/2011 9:01:12 AM - positioned 0086L1; position time: 00:00:04
12/15/2011 9:01:12 AM - begin writing
12/15/2011 2:36:43 PM - Error bpbrm(pid=15988) from client glc-file-01: ERR - failure reading file: E:\LANGUAGE FOLDERS\MLI Shared\2008 LANGUAGE COMPETITION\RUSSIAN\2008 Language Competition\20 Questions\2006\Cuts\smotr 26jan06.mpg (WIN32 21: The device is not ready. )
12/15/2011 2:36:43 PM - Error bpbrm(pid=15988) from client glc-file-01: ERR - Snapshot Error while reading file: GLOBALROOT\Device\HarddiskVolumeShadowCopy129\LANGUAGE FOLDERS\MLI Shared\2008 LANGUAGE COMPETITION\RUSSIAN\2008 Language Competition\20 Questions\2006\Cuts\smotr 26jan06.mpg
12/15/2011 2:36:43 PM - Critical bpbrm(pid=15988) from client glc-file-01: FTL - Backup operation aborted!    
12/15/2011 2:37:27 PM - Error bpbrm(pid=15988) could not send server status message      
12/15/2011 2:37:35 PM - end writing; write time: 05:36:23
snapshot error encountered(156) 

[Will_Restore]

That's a Windows problem that must be addressed before successful client backup.

Also it looks like you have some bad tapes: 0022L1 and 0009L1

[Marianne · Accepted solution]

Please let us know which NBU version and OS on client glc-file-01.

If OS is W2003 or later, ensure that VSS is used for WOFB:
Host Properties -> Master Server -> Client Attributes
If client glc-file-01 does not appear in the list, add it.
In Windows Open File Backup tab, select Volume Shadow Copy Service.

Also create bpfis folder on the client under ...\Veritas\netbackup\logs.

Post bpfis log as attachment if backup fails again.
 

[VirtualED]

You can see this problem when you are backing up a service path that is in an invalid location.  For example, if it is the passive node of a cluster and a service is set to use a shared location that is not available on the passive node.  Then Shadow Copy Components will fails with Status 156 or Status 13 depending on the version of NetBackup.

http://www.symantec.com/docs/TECH128805

Here are some other possibilities:

http://www.symantec.com/docs/TECH158127

http://www.symantec.com/docs/TECH162645

http://www.symantec.com/docs/TECH141518

[sunnyc_up]

i am also facing the same problem of 156.

[g_man1]

From past experiences, I have seen a 156 also if MS Windows updates have been downloaded and/or installed but the server has not been rebooted. This could happen if you have the updates configured to automatically download.

I have also encountered a 156 when one or more of the hard disks is about full. If using VSS for open file backup, you need enough disk space on the local drive for VSS to create the image.

Lastly, I have seen a 156 occur is the space allocated in Windows for VSS is not large enough.

Hope this helps!

[SRP]

I would agree with g_man's comments about windows updates having been installed without a reboot taking place - this seems to happen quite a bit with my servers.

[ambitiousgirl]

NBU version 7.0.1 and OS on client glc-file-01 is W2003

Thank you for all of your advice. It is very helpful.

[Douglas_A]

Looks like a windows issue with snapshot.. Try disabling open file backup on this host to see if you get a successfull backup.

Typically windows has issues sometimes snapping media files, i have seen this a few times now. the file "smotr 26jan06.mpg" may suggest someone is running this movie file somewhere and windows just cant snap it since its open. If you disable open file and it works you may check with the sys admin to see what the status of the file is.