cancel
Showing results for 
Search instead for 
Did you mean: 

Hyper-V backup failing with snapshot error encountered (156)

Sagar_Kolhe
Level 6

Hi All,

 

HYPER V backup failing with 156 status. below is the detailed. Please help

 

09/13/2016 21:09:36 - begin Parent Job
09/13/2016 21:09:36 - begin Hyper-V: Start Notify Script
09/13/2016 21:09:36 - Info RUNCMD (pid=81325) started
09/13/2016 21:09:36 - Info RUNCMD (pid=81325) exiting with status: 0
Operation Status: 0
09/13/2016 21:09:36 - end Hyper-V: Start Notify Script; elapsed time 0:00:00
09/13/2016 21:09:36 - begin Hyper-V: Step By Condition
Operation Status: 0
09/13/2016 21:09:36 - end Hyper-V: Step By Condition; elapsed time 0:00:00
Operation Status: 0
09/13/2016 21:09:36 - end Parent Job; elapsed time 0:00:00
09/13/2016 21:09:36 - begin Hyper-V: Create Snapshot
09/13/2016 21:09:37 - started process bpbrm (pid=44897)
09/13/2016 21:15:33 - Info bpbrm (pid=44897) xxxxx is the host to backup data from
09/13/2016 21:15:33 - Info bpbrm (pid=44897) reading file list for client
09/13/2016 21:15:33 - Info bpbrm (pid=44897) start bpfis on client
09/13/2016 21:15:38 - Info bpbrm (pid=44897) Starting create snapshot processing
09/13/2016 21:15:44 - Info bpfis (pid=24796) Backup started
09/13/2016 21:27:17 - Critical bpbrm (pid=44897) from client xxxxx: FTL - vfm_freeze_commit: method: Hyper-V_v2, type: FIM, function: Hyper-V_v2_make
09/13/2016 21:27:17 - Critical bpbrm (pid=44897) from client xxxxx: FTL - snapshot services: snapshot creation failed: unknown error.
09/13/2016 21:27:17 - Critical bpbrm (pid=44897) from client xxxxx: FTL - vfm_freeze_commit: method: Hyper-V_v2, type: FIM, function: Hyper-V_v2_make
09/13/2016 21:27:17 - Critical bpbrm (pid=44897) from client xxxxx: FTL - snapshot services: snapshot creation failed: unknown error.
09/13/2016 21:27:17 - Critical bpbrm (pid=44897) from client xxxxx: FTL - snapshot processing failed, status 156

09/13/2016 21:27:17 - Critical bpbrm (pid=44897) from client xxxxx: FTL - snapshot creation failed, status 156

09/13/2016 21:27:17 - Warning bpbrm (pid=44897) from client xxxxx: WRN - ALL_LOCAL_DRIVES is not frozen
09/13/2016 21:27:17 - Info bpfis (pid=24796) done. status: 156

09/13/2016 21:27:17 - end Hyper-V: Create Snapshot; elapsed time 0:17:41
09/13/2016 21:27:17 - Info bpfis (pid=24796) done. status: 156: snapshot error encountered
09/13/2016 21:27:17 - end writing
Operation Status: 156

09/13/2016 21:27:17 - begin Hyper-V: Stop On Error
Operation Status: 0
09/13/2016 21:27:17 - end Hyper-V: Stop On Error; elapsed time 0:00:00
09/13/2016 21:27:17 - begin Hyper-V: Delete Snapshot
09/13/2016 21:27:17 - started process bpbrm (pid=45765)
09/13/2016 21:33:13 - Info bpbrm (pid=45765) Starting delete snapshot processing
09/13/2016 21:33:24 - Info bpfis (pid=4616) Backup started
09/13/2016 21:33:24 - Warning bpbrm (pid=45765) from client xxxxx: cannot open C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.xxxxx_1473781176.1.0
09/13/2016 21:33:25 - Info bpfis (pid=4616) done. status: 4207

09/13/2016 21:33:25 - end Hyper-V: Delete Snapshot; elapsed time 0:06:08
09/13/2016 21:33:25 - Info bpfis (pid=4616) done. status: 4207: Could not fetch snapshot metadata or state files
09/13/2016 21:33:25 - end writing
Operation Status: 4207

09/13/2016 21:33:25 - begin Hyper-V: End Notify Script
09/13/2016 21:33:25 - Info RUNCMD (pid=109046) started
09/13/2016 21:33:25 - Info RUNCMD (pid=109046) exiting with status: 0
Operation Status: 0
09/13/2016 21:33:25 - end Hyper-V: End Notify Script; elapsed time 0:00:00
Operation Status: 156

snapshot error encountered  (156)

 

Regards,

Sagar

3 REPLIES 3

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Only Job details without background info does not help.

OS/Hyper-V version? 

NBU version? (on master, media server and Hyper-V server)

Has this worked before?
If no, and this is new installation and config, have you carefully read through and confirmed all the requirements in NBU for Hyper-V Admin Guide?

Some TNs:

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

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

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

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

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

 

 

This is old configuration. Previousely it was working.

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

So, if it was working before and NOTHING has changed from NBU point of view, then the Hyper-V admin needs to check what has changed or gone wrong on that side.

The TNs that I have shared explain different possible reasons as well as logs that can be checked.