cancel
Showing results forΒ 
Search instead forΒ 
Did you mean:Β 

snapshot error encountered(156)

Agadge
Level 3

Hello Team,

 


since few weeks i am facing some issues with SQL server backup.Its not getting completed withn following error.We have  master server 7.5.0.6 and same client version.

Logs

8/20/2013 6:35:13 AM - Info nbjm(pid=7672) starting backup job (jobid=16677) for client ABC.Avi.com, policy P-Backup-1, schedule CIM

8/20/2013 6:35:13 AM - estimated 128158000 Kbytes needed

8/20/2013 6:35:13 AM - Info nbjm(pid=7672) started backup (backupid=ABC.Avi.com_1376994913) job for client ABC.Avi.com, policy P-Backup-1, schedule CIM on storage unit CNA-Dedupe

8/20/2013 6:35:13 AM - started process bpbrm (14128)

8/20/2013 6:35:13 AM - started

8/20/2013 6:35:18 AM - Info bpbrm(pid=14128) ABC.Avi.com is the host to backup data from   

8/20/2013 6:35:18 AM - Info bpbrm(pid=14128) reading file list from client      

8/20/2013 6:35:19 AM - Info bpbrm(pid=14128) accelerator enabled         

8/20/2013 6:35:20 AM - connecting

8/20/2013 6:35:23 AM - Info bpbrm(pid=14128) starting bpbkar32 on client       

8/20/2013 6:35:23 AM - connected; connect time: 00:00:03

8/20/2013 6:35:24 AM - Info bpbkar32(pid=65576) Backup started         

8/20/2013 6:35:24 AM - Info bptm(pid=9188) start          

8/20/2013 6:35:24 AM - Info bptm(pid=9188) using 262144 data buffer size      

8/20/2013 6:35:24 AM - Info bptm(pid=9188) setting receive network buffer to 1049600 bytes     

8/20/2013 6:35:24 AM - Info bptm(pid=9188) using 128 data buffers       

8/20/2013 6:35:25 AM - Info bptm(pid=9188) start backup         

8/20/2013 6:35:33 AM - Info bptm(pid=9188) backup child process is pid 5328.13800     

8/20/2013 6:35:33 AM - Info bptm(pid=5328) start          

8/20/2013 6:35:33 AM - begin writing

8/20/2013 6:59:04 AM - Info bpbkar32(pid=65576) change journal NOT enabled for <C:\>     

8/20/2013 6:59:04 AM - Warning bpbrm(pid=14128) from client ABC.Avi.com: WRN - old TIR info file 'C:\Program Files\VERITAS\NetBackup\tir_info\C\NetBackup_file_info.P-Backup-1' is missing. Backing up everything in 'C:'

8/20/2013 7:31:43 AM - Info bpbkar32(pid=65576) change journal NOT enabled for <D:\>     

8/20/2013 7:31:43 AM - Warning bpbrm(pid=14128) from client ABC.Avi.com: WRN - old TIR info file 'C:\Program Files\VERITAS\NetBackup\tir_info\D\NetBackup_file_info.P-Backup-1' is missing. Backing up everything in 'D:'

8/20/2013 10:18:39 AM - Info bpbkar32(pid=65576) change journal NOT enabled for <E:\>     

8/20/2013 10:18:39 AM - Warning bpbrm(pid=14128) from client ABC.Avi.com: WRN - old TIR info file 'C:\Program Files\VERITAS\NetBackup\tir_info\E\NetBackup_file_info.P-Backup-1' is missing. Backing up everything in 'E:'

8/20/2013 6:03:05 PM - Error bpbrm(pid=14128) from client ABC.Avi.com: ERR - failure reading file: E:\Historian\Data\A120601_001\valueD4_1.sdt (WIN32 2: The system cannot find the file specified. )

8/20/2013 6:03:35 PM - Warning bpbrm(pid=14128) from client ABC.Avi.com: WRN - can't open directory: E:\Historian\Data\A120601_002 (WIN32 2: The system cannot find the file specified. )

8/20/2013 6:04:35 PM - Warning bpbrm(pid=14128) from client ABC.Avi.com: WRN - can't open directory: E:\Historian\Data\A120601_003 (WIN32 2: The system cannot find the file specified. )

8/20/2013 6:05:35 PM - Warning bpbrm(pid=14128) from client ABC.Avi.com: WRN - can't open directory: E:\Historian\Data\A120602_001 (WIN32 2: The system cannot find the file specified. )

8/20/2013 6:06:35 PM - Warning bpbrm(pid=14128) from client ABC.Avi.com: WRN - can't open directory: E:\Historian\Data\A120602_002 (WIN32 2: The system cannot find the file specified. )

8/20/2013 6:07:35 PM - Warning bpbrm(pid=14128) from client ABC.Avi.com: WRN - can't open directory: E:\Historian\Data\A120602_003 (WIN32 2: The system cannot find the file specified. )

8/20/2013 6:08:35 PM - Warning bpbrm(pid=14128) from client ABC.Avi.com: WRN - can't open directory: E:\Historian\Data\A120603_001 (WIN32 2: The system cannot find the file specified. )

8/20/2013 6:09:35 PM - Warning bpbrm(pid=14128) from client ABC.Avi.com: WRN - can't open directory: E:\Historian\Data\A120603_002 (WIN32 2: The system cannot find the file specified. )

8/20/2013 6:10:35 PM - Warning bpbrm(pid=14128) from client ABC.Avi.com: WRN - can't open directory: E:\Historian\Data\A120603_003 (WIN32 2: The system cannot find the file specified. )

8/20/2013 6:11:35 PM - Warning bpbrm(pid=14128) from client ABC.Avi.com: WRN - can't open directory: E:\Historian\Data\A120604_001 (WIN32 2: The system cannot find the file specified. )

8/20/2013 6:12:35 PM - Warning bpbrm(pid=14128) from client ABC.Avi.com: WRN - can't open directory: E:\Historian\Data\A120604_002 (WIN32 2: The system cannot find the file specified. )

8/20/2013 6:12:35 PM - Info bpbrm(pid=14128) from client ABC.Avi.com: TRV - last message being suppressed after 10 occurrences

8/20/2013 6:23:19 PM - Error bpbrm(pid=14128) from client ABC.Avi.com: ERR - Snapshot Error while enumerating: GLOBALROOT\Device\HarddiskVolumeShadowCopy170\Historian\Data\A120607_002\ 

8/20/2013 6:23:19 PM - Critical bpbrm(pid=14128) from client ABC.Avi.com: FTL - Backup operation aborted!   

8/20/2013 6:23:19 PM - Info bpbkar32(pid=65576) accelerator sent 420445535232 bytes out of 420027470848 bytes to server, optimization 0.0%

8/20/2013 6:23:29 PM - Info EFG.Avi.com(pid=9188) StorageServer=PureDisk:EFG.Avi.com; Report=PDDO Stats for (EFG.Avi.com): scanned: 410187391 KB, CR sent: 856211 KB, CR sent over FC: 0 KB, dedup: 99.8%

8/20/2013 6:23:31 PM - Error bpbrm(pid=14128) could not send server status message     

8/20/2013 6:23:34 PM - Info bpbkar32(pid=65576) done. status: 156: snapshot error encountered     

8/20/2013 6:23:34 PM - end writing; write time: 11:48:01

8/20/2013 6:23:35 PM - Info bpbrm(pid=12880) Starting delete snapshot processing       

8/20/2013 6:23:35 PM - Info bpfis(pid=0) Snapshot will not be deleted      

8/20/2013 6:23:38 PM - Info bpfis(pid=65092) Backup started         

8/20/2013 6:23:38 PM - Critical bpbrm(pid=12880) from client ABC.Avi.com: cannot open C:\Program Files\VERITAS\NetBackup\online_util\fi_cntl\bpfis.fim.ABC.Avi.com_1376994913.1.0    

8/20/2013 6:23:38 PM - Info bpfis(pid=65092) done. status: 1542        

8/20/2013 6:23:38 PM - end operation

8/20/2013 6:23:38 PM - Info bpfis(pid=0) done. status: 1542: An existing snapshot is no longer valid and cannot be mounted for subsequent operations

snapshot error encountered(156)

 

 

 

 

4 ACCEPTED SOLUTIONS

Accepted Solutions

quebek
Moderator
Moderator
   VIP    Certified

Looks like the E drive ran out of disk space during backups and the snapshot that NBU took using VSS was destroyed.

I would check the VSS setting on this volume - increased the amount of MB for snapshots or even put no limit, made more space on E volume. Also please create the bpfis legacy logging to know more about root cause of the snapshot failure.

Rerun the job...

View solution in original post

inn_kam
Level 6
Partner Accredited

 

NetBackup VSS snapshot error encountered (156)

Article:TECH75214  |  Created: 2009-01-02  |  Updated: 2013-05-03  |  Article URL http://www.symantec.com/docs/TECH75214

 

 

 

View solution in original post

Thiago_Pereira
Level 4

You have a lot of problems....

  1. Why you do C: backup? Its for BMR?
  2. Check the folders or files in Backup Selection, apparently you're pointing to folders on drive E: that do not exist or that the account you are using to backup does not have permission to access this folders.
  3. Check the VSS writers. How? Open Command prompt in client and tap this:

vssadmin list writers

Check if any Writes have status different of "No error", if has to solved this you need a reboot. Check in drive properties if the "Shadow Copies" -> Settings, check "No limit" for the drivers you want to backup.

  1. Make sure you have space in the drives when the backup run.

View solution in original post

Agadge
Level 3

Hi Thiago,

 

C: Drive for BMR.

Shadow copies are disable on  this server as change rate is too high.

Its a 1.32 TB Drive with 125 GB free space.

E: Drive exist and have a proper permissions.

Its a SQL box

 

 

 

 

 

View solution in original post

5 REPLIES 5

quebek
Moderator
Moderator
   VIP    Certified

Looks like the E drive ran out of disk space during backups and the snapshot that NBU took using VSS was destroyed.

I would check the VSS setting on this volume - increased the amount of MB for snapshots or even put no limit, made more space on E volume. Also please create the bpfis legacy logging to know more about root cause of the snapshot failure.

Rerun the job...

inn_kam
Level 6
Partner Accredited

 

NetBackup VSS snapshot error encountered (156)

Article:TECH75214  |  Created: 2009-01-02  |  Updated: 2013-05-03  |  Article URL http://www.symantec.com/docs/TECH75214

 

 

 

Thiago_Pereira
Level 4

You have a lot of problems....

  1. Why you do C: backup? Its for BMR?
  2. Check the folders or files in Backup Selection, apparently you're pointing to folders on drive E: that do not exist or that the account you are using to backup does not have permission to access this folders.
  3. Check the VSS writers. How? Open Command prompt in client and tap this:

vssadmin list writers

Check if any Writes have status different of "No error", if has to solved this you need a reboot. Check in drive properties if the "Shadow Copies" -> Settings, check "No limit" for the drivers you want to backup.

  1. Make sure you have space in the drives when the backup run.

Agadge
Level 3

Hi Thiago,

 

C: Drive for BMR.

Shadow copies are disable on  this server as change rate is too high.

Its a 1.32 TB Drive with 125 GB free space.

E: Drive exist and have a proper permissions.

Its a SQL box

 

 

 

 

 

Thiago_Pereira
Level 4

OK,

You check the VSS writers? even with the Shadow copies disabled, the NetBackup uses these settings, I've had problems that were only solved after the change to "No limit" on Shadow Copies, even with it disabled for that drive.

I dont no if your problem is the same but give a try.