Highlighted

job backup error

hello 


21 juil. 2019 21:45:39 - Info nbjm (pid=3288) starting backup job (jobid=34387) for client MPX-VM-LB-01, policy MPX-CHYV16-01_P, schedule Full
21 juil. 2019 21:45:39 - Info nbjm (pid=3288) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=34387, request id:{0813633E-8067-4782-B144-B42988F4ABEC})
21 juil. 2019 21:45:39 - requesting resource NETBACKUP_POOL-stu
21 juil. 2019 21:45:39 - requesting resource mpx-py-bkup02.snmvt.intra.NBU_CLIENT.MAXJOBS.MPX-VM-LB-01
21 juil. 2019 21:45:39 - requesting resource mpx-py-bkup02.snmvt.intra.NBU_POLICY.MAXJOBS.MPX-CHYV16-01_P
21 juil. 2019 21:45:39 - awaiting resource NETBACKUP_POOL-stu. Maximum job count has been reached for the storage unit.
21 juil. 2019 21:45:58 - granted resource mpx-py-bkup02.snmvt.intra.NBU_CLIENT.MAXJOBS.MPX-VM-LB-01
21 juil. 2019 21:45:58 - granted resource mpx-py-bkup02.snmvt.intra.NBU_POLICY.MAXJOBS.MPX-CHYV16-01_P
21 juil. 2019 21:45:58 - granted resource MediaID=@aaaab;DiskVolume=G:\;DiskPool=NETBACKUP_POOL;Path=G:\;StorageServer=mpx-py-bkup02.snmvt.intra;MediaServer=mpx-py-bkup02.snmvt.intra
21 juil. 2019 21:45:58 - granted resource NETBACKUP_POOL-stu
21 juil. 2019 21:45:58 - estimated 0 kbytes needed
21 juil. 2019 21:45:58 - begin Parent Job
21 juil. 2019 21:45:58 - begin Hyper-V: Start Notify Script
21 juil. 2019 21:45:58 - Info RUNCMD (pid=12192) started
21 juil. 2019 21:45:58 - Info RUNCMD (pid=12192) exiting with status: 0
Operation Status: 0
21 juil. 2019 21:45:58 - end Hyper-V: Start Notify Script; elapsed time 0:00:00
21 juil. 2019 21:45:58 - begin Hyper-V: Step By Condition
Operation Status: 0
21 juil. 2019 21:45:58 - end Hyper-V: Step By Condition; elapsed time 0:00:00
Operation Status: 0
21 juil. 2019 21:45:58 - end Parent Job; elapsed time 0:00:00
21 juil. 2019 21:45:58 - begin Hyper-V: Create Snapshot
21 juil. 2019 21:45:59 - started process bpbrm (pid=2188)
21 juil. 2019 21:46:02 - Info bpbrm (pid=2188) MPX-VM-LB-01 is the host to backup data from
21 juil. 2019 21:46:02 - Info bpbrm (pid=2188) reading file list for client
21 juil. 2019 21:46:02 - Info bpbrm (pid=2188) start bpfis on client
21 juil. 2019 21:46:02 - Info bpbrm (pid=2188) Starting create snapshot processing
21 juil. 2019 21:46:02 - Info bpfis (pid=43768) Backup started
21 juil. 2019 21:46:58 - Critical bpbrm (pid=2188) from client MPX-VM-LB-01: FTL - vfm_freeze_commit: method: Hyper-V_v2, type: FIM, function: Hyper-V_v2_make
21 juil. 2019 21:46:58 - Critical bpbrm (pid=2188) from client MPX-VM-LB-01: FTL - snapshot services: snapshot creation failed: unknown error.
21 juil. 2019 21:46:58 - Critical bpbrm (pid=2188) from client MPX-VM-LB-01: FTL - vfm_freeze_commit: method: Hyper-V_v2, type: FIM, function: Hyper-V_v2_make
21 juil. 2019 21:46:58 - Critical bpbrm (pid=2188) from client MPX-VM-LB-01: FTL - snapshot services: snapshot creation failed: unknown error.
21 juil. 2019 21:46:58 - Critical bpbrm (pid=2188) from client MPX-VM-LB-01: FTL - snapshot processing failed, status 4258
21 juil. 2019 21:46:58 - Critical bpbrm (pid=2188) from client MPX-VM-LB-01: FTL - snapshot creation failed, status 4258
21 juil. 2019 21:46:58 - Warning bpbrm (pid=2188) from client MPX-VM-LB-01: WRN - ALL_LOCAL_DRIVES is not frozen
21 juil. 2019 21:46:58 - Info bpfis (pid=43768) done. status: 4258
21 juil. 2019 21:46:58 - end Hyper-V: Create Snapshot; elapsed time 0:01:00
21 juil. 2019 21:46:58 - Info bpfis (pid=43768) done. status: 4258: Transient error encountered while taking Hyper-V VM snapshot.
21 juil. 2019 21:46:58 - end writing
Operation Status: 4258
21 juil. 2019 21:46:58 - begin Hyper-V: Stop On Error
Operation Status: 0
21 juil. 2019 21:46:58 - end Hyper-V: Stop On Error; elapsed time 0:00:00
21 juil. 2019 21:46:58 - begin Hyper-V: Delete Snapshot
21 juil. 2019 21:46:58 - started process bpbrm (pid=13584)
21 juil. 2019 21:47:01 - Info bpbrm (pid=13584) Starting delete snapshot processing
21 juil. 2019 21:47:02 - Info bpfis (pid=21676) Backup started
21 juil. 2019 21:47:02 - Warning bpbrm (pid=13584) from client MPX-VM-LB-01: cannot open C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.MPX-VM-LB-01_1563741958.1.0
21 juil. 2019 21:47:02 - Info bpfis (pid=21676) done. status: 4207
21 juil. 2019 21:47:02 - end Hyper-V: Delete Snapshot; elapsed time 0:00:04
21 juil. 2019 21:47:02 - Info bpfis (pid=21676) done. status: 4207: Could not fetch snapshot metadata or state files
21 juil. 2019 21:47:02 - end writing
Operation Status: 4207
21 juil. 2019 21:47:02 - begin Hyper-V: End Notify Script
21 juil. 2019 21:47:02 - Info RUNCMD (pid=12456) started
21 juil. 2019 21:47:02 - Info RUNCMD (pid=12456) exiting with status: 0
Operation Status: 0
21 juil. 2019 21:47:02 - end Hyper-V: End Notify Script; elapsed time 0:00:00
Operation Status: 4258
Transient error encountered while taking Hyper-V VM snapshot (4258)

Tags (2)
2 Replies

Re: job backup error

Use the Hyper-V Manager GUI to check the Hyper-V host(s) and if the Hyper-V host is a member of a Hyper-V cluster then check every Hyper-V host in the Hyper-V cluster... things to check for are :

1) is the client VM stuck in a "Backing up." state ?  try to migrate it to another host ?  or you may have to drain the host and reboot it.

2) any stale checkpoints on the VMs ?

3) any stale VSS snapshots on the Hyper-V hosts ?

Re: job backup error

I found the following on a Microsoft forum: 

https://social.technet.microsoft.com/Forums/en-US/2db242dc-0d63-4394-b719-a860676d99e3/vm-machines-a...

VOX discussion about status 4257  - not possible to take Hyper-V backup with passthrough disk:
https://vox.veritas.com/t5/NetBackup/Status-code-156-or-4258-for-Hyper-V/td-p/852289

The NBU for Hyper-V manual also has a troubleshooting chapter - there is a section with possible reasons for snapshot errors. If you want to download the manual, you can find links for all supported NBU versions in 'Handy NBU links' in my signature.

Online manual for 8.1: https://www.veritas.com/content/support/en_US/doc/21357025-127305010-0/v18522639-127305010