snapshot error encountered (156)
Hello,
Windows FS Full schedule backup is failing after writing 4+TB with below error, incremental backup is working ok.
Communication looks ok between client and NBu master/media. please assist.
Master OS and vers. - Linux 7.7.2
07/29/2018 06:00:09 - begin writing
07/30/2018 03:21:53 - Warning bpbrm (pid=17518) from client xxx: WRN - can't open file: E:\SFTP\VZW\SDF\download\SDR\Archive\NPHASE_20180729_030451_0441825_FRM3.txt (WIN32 55: The specified network resource or device is no longer available. )
07/30/2018 03:21:53 - Error bpbrm (pid=17518) from client xxx: ERR - Snapshot Error while opening file: GLOBALROOT\Device\HarddiskVolumeShadowCopy629\SFTP\VZW\SDF\download\SDR\Archive\NPHASE_20180729_030451_0441825_FRM3.txt
07/30/2018 03:21:53 - Critical bpbrm (pid=17518) from client xxx: FTL - Backup operation aborted!
07/30/2018 03:21:55 - Error bptm (pid=17525) media manager terminated by parent process
07/30/2018 03:22:03 - Info bpbkar (pid=22216) done. status: 156: snapshot error encountered
07/30/2018 03:22:04 - Info bpbrm (pid=75665) Starting delete snapshot processing
07/30/2018 03:25:22 - Info bpfis (pid=8516) Backup started
07/30/2018 03:25:22 - Critical bpbrm (pid=75665) from client xxx: cannot open C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.xxx_1532844003.1.0
07/30/2018 03:25:43 - Info bpfis (pid=8516) done. status: 4207
07/30/2018 03:25:43 - Info bpfis (pid=8516) done. status: 4207: Could not fetch snapshot metadata or state files
07/30/2018 04:45:13 - end writing; write time: 22:45:04
snapshot error encountered (156)
Thanks
When you see this from bpbrm, look at the client log to find out what happened:
>Warning bpbrm (pid=17518) from client...
>Error bpbrm (pid=17518) from client...In this case, get a bpfis log. Make sure the NetBackup\logs\bpfis folder exists and set the general logging setting to 5 and the logging under Windows Client / Client Settings to 2.
The path in the warning may not be the file that couldn't be opened. It probably refers to the file on the snapshot, as in the error line.
I don't think it's the VSS state in this case. It looks like you're using hardware provider snapshots and something's wrong with your disk array. I could be way off. Look at the bpfis log.