cancel
Showing results for 
Search instead for 
Did you mean: 

Help with new Hyper-V intelligent policy

spitman
Level 5

We've been running VMware intelligent policies for a while; but this is the first Hyper-V one I have set up.

It was working ok for a couple days; then it came up and said "snapshot error encountered," and that's about it. According to the Windows admin, there is no snapshot on that system. He is working on getting me access now so I can view the environment (again--I've never worked on it before).

Here is the output from the parent job:


01/07/2016 08:52:24 - Info nbjm (pid=3719) starting backup job (jobid=1827809) for client rtxhypwp01, policy vm_hyperv, schedule weekly_full
01/07/2016 08:52:24 - Info nbjm (pid=3719) requesting MEDIA_SERVER_ONLY resources from RB for backup job (jobid=1827809, request id:{4323208E-B54E-11E5-BB67-06DFB447BED8})
01/07/2016 08:52:24 - requesting resource rtxdxip01-stg-itg
01/07/2016 08:52:24 - requesting resource kronos.NBU_POLICY.MAXJOBS.vm_hyperv
01/07/2016 08:52:24 - requesting resource kronos.NBU_CLIENT.MAXJOBS.rtxhypwp01
01/07/2016 08:52:24 - granted resource  kronos.NBU_POLICY.MAXJOBS.vm_hyperv
01/07/2016 08:52:24 - granted resource  kronos.NBU_CLIENT.MAXJOBS.rtxhypwp01
01/07/2016 08:52:24 - estimated 0 kbytes needed
01/07/2016 08:52:24 - begin Parent Job
01/07/2016 08:52:24 - begin Application Resolver: Start Notify Script
01/07/2016 08:52:24 - Info RUNCMD (pid=15067) started
01/07/2016 08:52:24 - Info RUNCMD (pid=15067) exiting with status: 0
Operation Status: 0
01/07/2016 08:52:24 - end Application Resolver: Start Notify Script; elapsed time 0:00:00
01/07/2016 08:52:24 - begin Application Resolver: Step By Condition
Operation Status: 0
01/07/2016 08:52:24 - end Application Resolver: Step By Condition; elapsed time 0:00:00
01/07/2016 08:52:24 - begin Application Resolver: Resolver Discovery
Operation Status: 0
01/07/2016 08:52:39 - end Application Resolver: Resolver Discovery; elapsed time 0:00:15
01/07/2016 08:52:39 - begin Application Resolver: Policy Execution Manager Preprocessed
Operation Status: 156

01/07/2016 08:54:02 - end Application Resolver: Policy Execution Manager Preprocessed; elapsed time 0:01:23
01/07/2016 08:54:02 - begin Application Resolver: Stop On Error
Operation Status: 0
01/07/2016 08:54:02 - end Application Resolver: Stop On Error; elapsed time 0:00:00
01/07/2016 08:54:02 - begin Application Resolver: End Notify Script
01/07/2016 08:54:02 - Info RUNCMD (pid=15219) started
01/07/2016 08:54:02 - Info RUNCMD (pid=15219) exiting with status: 0
Operation Status: 0
01/07/2016 08:54:02 - end Application Resolver: End Notify Script; elapsed time 0:00:00
Operation Status: 156

01/07/2016 08:54:02 - end Parent Job; elapsed time 0:01:38
snapshot error encountered  (156)

 

Here is the output from the child job (currently there is only one client called out in the policy):


01/07/2016 08:52:39 - Info nbjm (pid=3719) starting backup job (jobid=1827810) for client rtxvmmwp01, policy vm_hyperv, schedule weekly_full
01/07/2016 08:52:39 - Info nbjm (pid=3719) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=1827810, request id:{4C1CE602-B54E-11E5-83C6-36A88C15EC5E})
01/07/2016 08:52:39 - requesting resource rtxdxip01-stg-itg
01/07/2016 08:52:39 - requesting resource kronos.NBU_CLIENT.MAXJOBS.rtxvmmwp01
01/07/2016 08:52:39 - granted resource  kronos.NBU_CLIENT.MAXJOBS.rtxvmmwp01
01/07/2016 08:52:39 - granted resource  MediaID=@aaaaj;DiskVolume=rtxdxip01-lsu;DiskPool=rtxdxip01-dp;Path=rtxdxip01-lsu;StorageServer=rtxdxip01-ss_167.254.103.89;MediaServer=rchnbump2
01/07/2016 08:52:39 - granted resource  rchnbump2-rtxdxip01
01/07/2016 08:52:39 - estimated 0 kbytes needed
01/07/2016 08:52:39 - begin Parent Job
01/07/2016 08:52:39 - begin Application Snapshot: Step By Condition
Operation Status: 0
01/07/2016 08:52:39 - end Application Snapshot: Step By Condition; elapsed time 0:00:00
01/07/2016 08:52:39 - begin Application Snapshot: Read File List
Operation Status: 0
01/07/2016 08:52:39 - end Application Snapshot: Read File List; elapsed time 0:00:00
01/07/2016 08:52:39 - begin Application Snapshot: Create Snapshot
01/07/2016 08:52:39 - started process bpbrm (pid=6951)
01/07/2016 08:52:43 - Info bpbrm (pid=6951) rtxvmmwp01 is the host to backup data from
01/07/2016 08:52:43 - Info bpbrm (pid=6951) reading file list for client
01/07/2016 08:52:43 - Info bpbrm (pid=6951) start bpfis on client
01/07/2016 08:52:43 - Info bpbrm (pid=6951) Starting create snapshot processing
01/07/2016 08:52:44 - Info bpfis (pid=5584) Backup started
01/07/2016 08:53:54 - Critical bpbrm (pid=6951) from client rtxvmmwp01: FTL - vfm_freeze_commit: method: Hyper-V_v2, type: FIM, function: Hyper-V_v2_make
01/07/2016 08:53:54 - Critical bpbrm (pid=6951) from client rtxvmmwp01: FTL - snapshot services: snapshot creation failed: unknown error.
01/07/2016 08:53:54 - Critical bpbrm (pid=6951) from client rtxvmmwp01: FTL - vfm_freeze_commit: method: Hyper-V_v2, type: FIM, function: Hyper-V_v2_make
01/07/2016 08:53:54 - Critical bpbrm (pid=6951) from client rtxvmmwp01: FTL - snapshot services: snapshot creation failed: unknown error.
01/07/2016 08:53:54 - Critical bpbrm (pid=6951) from client rtxvmmwp01: FTL - snapshot processing failed, status 156

01/07/2016 08:53:54 - Critical bpbrm (pid=6951) from client rtxvmmwp01: FTL - snapshot creation failed, status 156

01/07/2016 08:53:54 - Warning bpbrm (pid=6951) from client rtxvmmwp01: WRN - ALL_LOCAL_DRIVES is not frozen
01/07/2016 08:53:54 - Info bpfis (pid=5584) done. status: 156

01/07/2016 08:53:54 - end Application Snapshot: Create Snapshot; elapsed time 0:01:15
01/07/2016 08:53:54 - Info bpfis (pid=5584) done. status: 156: snapshot error encountered
01/07/2016 08:53:54 - end writing
Operation Status: 156

01/07/2016 08:53:54 - end Parent Job; elapsed time 0:01:15
01/07/2016 08:53:54 - begin Application Snapshot: Stop On Error
Operation Status: 0
01/07/2016 08:53:54 - end Application Snapshot: Stop On Error; elapsed time 0:00:00
01/07/2016 08:53:54 - begin Application Snapshot: Cleanup Resources
01/07/2016 08:53:54 - end Application Snapshot: Cleanup Resources; elapsed time 0:00:00
01/07/2016 08:53:54 - begin Application Snapshot: Delete Snapshot
01/07/2016 08:53:54 - started process bpbrm (pid=7138)
01/07/2016 08:53:56 - Info bpbrm (pid=7138) Starting delete snapshot processing
01/07/2016 08:54:01 - Info bpfis (pid=15276) Backup started
01/07/2016 08:54:01 - Warning bpbrm (pid=7138) from client rtxvmmwp01: cannot open C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.rtxvmmwp01_1452178359.1.0
01/07/2016 08:54:02 - Info bpfis (pid=15276) done. status: 4207

01/07/2016 08:54:02 - end Application Snapshot: Delete Snapshot; elapsed time 0:00:08
01/07/2016 08:54:02 - Info bpfis (pid=15276) done. status: 4207: Could not fetch snapshot metadata or state files
01/07/2016 08:54:02 - end writing
Operation Status: 4207

Operation Status: 156

snapshot error encountered  (156)

 

Thanks in advance for your help...

1 ACCEPTED SOLUTION

Accepted Solutions

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified
List of possible reasons for status 156: http://www.veritas.com/docs/000067928

View solution in original post

2 REPLIES 2

RiaanBadenhorst
Moderator
Moderator
Partner    VIP    Accredited Certified

Hi,

Troubleshooting would be the same as VMware, get the bpfis from the hyper-v host/parent (not the backup host as in VMware). If that looks OK, and the snapshot gets created, check VSS errors inisde the guest/host. Also check vxms logs on the host/parent (https://www.veritas.com/support/en_US/article.HOWTO70905)

And this one https://www.veritas.com/support/en_US/article.HOWTO70791

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified
List of possible reasons for status 156: http://www.veritas.com/docs/000067928