snapshot error encountered (156)

9 sept. 2019 03:33:16 - Info nbjm (pid=8396) starting backup job (jobid=36305) for client MPX-VM-NAVINT01, policy MPX-CHYV16-01_P, schedule Full
9 sept. 2019 03:33:16 - Info nbjm (pid=8396) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=36305, request id:{BA183B15-136C-4FC1-A84D-4A17106EB873})
9 sept. 2019 03:33:16 - requesting resource NETBACKUP_POOL-stu
9 sept. 2019 03:33:16 - requesting resource mpx-py-bkup02.snmvt.intra.NBU_CLIENT.MAXJOBS.MPX-VM-NAVINT01
9 sept. 2019 03:33:16 - requesting resource mpx-py-bkup02.snmvt.intra.NBU_POLICY.MAXJOBS.MPX-CHYV16-01_P
9 sept. 2019 03:33:16 - granted resource  mpx-py-bkup02.snmvt.intra.NBU_CLIENT.MAXJOBS.MPX-VM-NAVINT01
9 sept. 2019 03:33:16 - granted resource  mpx-py-bkup02.snmvt.intra.NBU_POLICY.MAXJOBS.MPX-CHYV16-01_P
9 sept. 2019 03:33:16 - granted resource  MediaID=@aaaab;DiskVolume=G:\;DiskPool=NETBACKUP_POOL;Path=G:\;StorageServer=mpx-py-bkup02.snmvt.intra;MediaServer=mpx-py-bkup02.snmvt.intra
9 sept. 2019 03:33:16 - granted resource  NETBACKUP_POOL-stu
9 sept. 2019 03:33:16 - estimated 385623315 kbytes needed
9 sept. 2019 03:33:16 - begin Parent Job
9 sept. 2019 03:33:16 - begin Hyper-V: Start Notify Script
9 sept. 2019 03:33:16 - Info RUNCMD (pid=11592) started
9 sept. 2019 03:33:17 - Info RUNCMD (pid=11592) exiting with status: 0
Operation Status: 0
9 sept. 2019 03:33:17 - end Hyper-V: Start Notify Script; elapsed time 0:00:01
9 sept. 2019 03:33:17 - begin Hyper-V: Step By Condition
Operation Status: 0
9 sept. 2019 03:33:17 - end Hyper-V: Step By Condition; elapsed time 0:00:00
Operation Status: 0
9 sept. 2019 03:33:17 - end Parent Job; elapsed time 0:00:01
9 sept. 2019 03:33:17 - begin Hyper-V: Create Snapshot
9 sept. 2019 03:33:17 - started process bpbrm (pid=13088)
9 sept. 2019 03:33:24 - Info bpbrm (pid=13088) MPX-VM-NAVINT01 is the host to backup data from
9 sept. 2019 03:33:24 - Info bpbrm (pid=13088) reading file list for client
9 sept. 2019 03:33:24 - Info bpbrm (pid=13088) start bpfis on client
9 sept. 2019 03:33:24 - Info bpbrm (pid=13088) Starting create snapshot processing
9 sept. 2019 03:33:24 - Info bpfis (pid=14912) Backup started
9 sept. 2019 03:36:28 - Critical bpbrm (pid=13088) from client MPX-VM-NAVINT01: FTL - vfm_freeze_commit: method: Hyper-V_v2, type: FIM, function: Hyper-V_v2_make
9 sept. 2019 03:36:28 - Critical bpbrm (pid=13088) from client MPX-VM-NAVINT01: FTL - snapshot services: snapshot creation failed: unknown error.
9 sept. 2019 03:36:28 - Critical bpbrm (pid=13088) from client MPX-VM-NAVINT01: FTL - vfm_freeze_commit: method: Hyper-V_v2, type: FIM, function: Hyper-V_v2_make
9 sept. 2019 03:36:28 - Critical bpbrm (pid=13088) from client MPX-VM-NAVINT01: FTL - snapshot services: snapshot creation failed: unknown error.
9 sept. 2019 03:36:28 - Critical bpbrm (pid=13088) from client MPX-VM-NAVINT01: FTL - snapshot processing failed, status 156
9 sept. 2019 03:36:28 - Critical bpbrm (pid=13088) from client MPX-VM-NAVINT01: FTL - snapshot creation failed, status 156
9 sept. 2019 03:36:28 - Warning bpbrm (pid=13088) from client MPX-VM-NAVINT01: WRN - ALL_LOCAL_DRIVES is not frozen
9 sept. 2019 03:36:28 - Info bpfis (pid=14912) done. status: 156
9 sept. 2019 03:36:28 - end Hyper-V: Create Snapshot; elapsed time 0:03:11
9 sept. 2019 03:36:28 - Info bpfis (pid=14912) done. status: 156: snapshot error encountered
9 sept. 2019 03:36:28 - end writing
Operation Status: 156
9 sept. 2019 03:36:28 - begin Hyper-V: Stop On Error
Operation Status: 0
9 sept. 2019 03:36:28 - end Hyper-V: Stop On Error; elapsed time 0:00:00
9 sept. 2019 03:36:28 - begin Hyper-V: Delete Snapshot
9 sept. 2019 03:36:28 - started process bpbrm (pid=11916)
9 sept. 2019 03:36:33 - Info bpbrm (pid=11916) Starting delete snapshot processing
9 sept. 2019 03:36:34 - Info bpfis (pid=19792) Backup started
9 sept. 2019 03:36:34 - Warning bpbrm (pid=11916) from client MPX-VM-NAVINT01: cannot open C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.MPX-VM-NAVINT01_1567996396.1.0
9 sept. 2019 03:36:34 - Info bpfis (pid=19792) done. status: 4207
9 sept. 2019 03:36:34 - end Hyper-V: Delete Snapshot; elapsed time 0:00:06
9 sept. 2019 03:36:34 - Info bpfis (pid=19792) done. status: 4207: Could not fetch snapshot metadata or state files
9 sept. 2019 03:36:34 - end writing
Operation Status: 4207
9 sept. 2019 03:36:34 - begin Hyper-V: End Notify Script
9 sept. 2019 03:36:34 - Info RUNCMD (pid=9944) started
9 sept. 2019 03:36:34 - Info RUNCMD (pid=9944) exiting with status: 0
Operation Status: 0
9 sept. 2019 03:36:34 - end Hyper-V: End Notify Script; elapsed time 0:00:00
Operation Status: 156
9 sept. 2019 08:17:30 - job 36305 was restarted as job 36306
snapshot error encountered  (156)

 hello how can i troubleshooting this issus ??where the space free of backp is 500 go /7 To 

Tags (2)
7 Replies

Re: snapshot error encountered (156)

@netbackup22 

You may want to have a look in NBU for Hyper-V manual for a list of possible reasons for status 156. 

Here is the online version:
https://www.veritas.com/content/support/en_US/doc/21357025-127305010-0/v18522639-127305010

You need bpfis log on the Hyper-V server to assist with troubleshooting. 

Re: snapshot error encountered (156)

hello leader

i don't have access to hyper-v  juste the NBU ? can i troubleshooting this form netbackup console to reconfigure the policies where the client is failed?

please how ?

Tags (2)

Re: snapshot error encountered (156)

You will need to work with the Hyper-V admin to troubleshoot. 

Show him/her the URL in my previous post and ask for assistance. 

Re: snapshot error encountered (156)

Don't forget you can probably use the "Logging Assistant" in the admin GUI (the last option on the left side) to enable and then collect the debug xlogs from the client. 

Create a new record (just put any text in for the case ID it requests - unless you actually have an open case), select the "Setup Debug Logging" option click next then enter the JobID of the failed job. The LA will then suggest appropriate logs to enable. 

You should now be able to go in and collect debug logs (using a suitable timeframe) - it will suggest a location to store them on the master server, but you are free to change this to a location with sufficient space. Once the logs have been collected, you can examine them on the master server. 

Re: snapshot error encountered (156)

@davidmoline 

Will the "Setup Debug Logging" create logs - such as bpfis and VxMS - on the backup host (in this case, the Hyper-V server) if they do not exist? 

Re: snapshot error encountered (156)

Yep - that's one of the great features of the assistant - you don't need to annoy admins (the target does need a functioning NetBackup client of course)

It increases the verbosity of logging as part of the setup process. It will also turn down logging or disable once finished as much as is possible (as some logs require NetBackup services to be restarted for logging changes to take effect).

Have a look at the FAQ https://www.veritas.com/content/support/en_US/article.100028985.html and also in the Using the Logging Assistant chapter in the Monitoring and Reporting section of the Admin Guide volume 1.

Highlighted

Re: snapshot error encountered (156)

Thanks for this info @davidmoline !