cancel
Showing results for 
Search instead for 
Did you mean: 

Hyper-V servers failing with error 4200 continuously

PavanK1
Level 2

Hi All,

 

We are using Hyper-V servers from a week these jobs are getting failed with the error code 4200, could any please help on this.

Thanks in advance

All servers are in Windows environment

Master Server: Windows 2008

Hyper-V Servers: Windows 2008

 

Job Details:

7/28/2016 4:08:34 PM - Info nbjm(pid=7660) starting backup job (jobid=147906) for client AMSDC1-V-56001B.shell.com, policy SVRState-02, schedule Full
7/28/2016 4:08:34 PM - Info nbjm(pid=7660) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=147906, request id:{2D56E7A7-151C-4A50-A39B-D009C2466727})
7/28/2016 4:08:34 PM - requesting resource SUG-NBU-MEDIASVRS-01
7/28/2016 4:08:34 PM - requesting resource AMSDC1-B-50702N.NBU_CLIENT.MAXJOBS.AMSDC1-V-56001B.shell.com
7/28/2016 4:08:34 PM - requesting resource AMSDC1-B-50702N.NBU_POLICY.MAXJOBS.SVRState-02
7/28/2016 4:08:36 PM - granted resource AMSDC1-B-50702N.NBU_CLIENT.MAXJOBS.AMSDC1-V-56001B.shell.com
7/28/2016 4:08:36 PM - granted resource AMSDC1-B-50702N.NBU_POLICY.MAXJOBS.SVRState-02
7/28/2016 4:08:36 PM - granted resource A1C361
7/28/2016 4:08:36 PM - granted resource AMSDC1TL50002-LTO4-04
7/28/2016 4:08:36 PM - granted resource AMSDC1-S-50705-hcart-robot-tld-0
7/28/2016 4:08:36 PM - estimated 0 Kbytes needed
7/28/2016 4:08:36 PM - begin Parent Job
7/28/2016 4:08:36 PM - begin Hyper-V, Start Notify Script
7/28/2016 4:08:36 PM - Info RUNCMD(pid=9012) started
7/28/2016 4:08:36 PM - Info RUNCMD(pid=9012) exiting with status: 0
Status 0
7/28/2016 4:08:36 PM - end Hyper-V, Start Notify Script; elapsed time: 0:00:00
7/28/2016 4:08:36 PM - begin Hyper-V, Step By Condition
Status 0
7/28/2016 4:08:36 PM - end Hyper-V, Step By Condition; elapsed time: 0:00:00
7/28/2016 4:08:36 PM - begin Hyper-V, Read File List
Status 0
7/28/2016 4:08:36 PM - end Hyper-V, Read File List; elapsed time: 0:00:00
7/28/2016 4:08:36 PM - begin Hyper-V, Create Snapshot
7/28/2016 4:08:36 PM - started
7/28/2016 4:08:39 PM - started process bpbrm (3228)
7/28/2016 4:08:59 PM - Info bpbrm(pid=3228) AMSDC1-V-56001B.shell.com is the host to backup data from
7/28/2016 4:08:59 PM - Info bpbrm(pid=3228) reading file list for client
7/28/2016 4:08:59 PM - Info bpbrm(pid=3228) start bpfis on client
7/28/2016 4:09:00 PM - Info bpbrm(pid=3228) Starting create snapshot processing
7/28/2016 4:09:02 PM - Info bpfis(pid=2100) Backup started
7/28/2016 5:09:04 PM - Warning bpbrm(pid=3228) from client AMSDC1-V-56001B.shell.com: WRN - ALL_LOCAL_DRIVES is not frozen
7/28/2016 5:09:04 PM - Info bpfis(pid=2100) done. status: 4200
7/28/2016 5:09:04 PM - end Hyper-V, Create Snapshot; elapsed time: 1:00:28
7/28/2016 5:09:04 PM - Info bpfis(pid=2100) done. status: 4200: Operation failed: Unable to acquire snapshot lock
7/28/2016 5:09:04 PM - end writing
Status 4200
7/28/2016 5:09:04 PM - end Parent Job; elapsed time: 1:00:28
7/28/2016 5:09:04 PM - begin Hyper-V, Stop On Error
Status 0
7/28/2016 5:09:04 PM - end Hyper-V, Stop On Error; elapsed time: 0:00:00
7/28/2016 5:09:04 PM - begin Hyper-V, Delete Snapshot
7/28/2016 5:09:06 PM - started process bpbrm (6692)
7/28/2016 5:09:24 PM - Info bpbrm(pid=6692) Starting delete snapshot processing
7/28/2016 5:09:28 PM - Info bpfis(pid=7020) Backup started
7/28/2016 6:09:29 PM - Info bpfis(pid=7020) done. status: 4200
7/28/2016 6:09:29 PM - end writing
Status 4200
7/28/2016 6:09:29 PM - end Hyper-V, Delete Snapshot; elapsed time: 1:00:25
7/28/2016 6:09:29 PM - begin Hyper-V, End Notify Script
7/28/2016 6:09:29 PM - end Hyper-V, End Notify Script; elapsed time: 0:00:00
7/28/2016 6:09:29 PM - Info bpfis(pid=7020) done. status: 4200: Operation failed: Unable to acquire snapshot lock
7/28/2016 6:09:29 PM - Info RUNCMD(pid=6364) started
7/28/2016 6:09:29 PM - Info RUNCMD(pid=6364) exiting with status: 0
Status 0
7/28/2016 6:09:29 PM - end operation
Status 4200
7/28/2016 6:09:29 PM - end operation
Operation failed: Unable to acquire snapshot lock(4200)

 

2 REPLIES 2

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

I have moved your post from 'General Veritas' to NetBackup forum.

Please work through this TN: for possible reasons:
http://www.veritas.com/docs/000044742 

stucci
Level 6

Hi Pavan,

Hi worked heavy with hyper-v. For my experience, job error 4200 show that your VM does'not support the "online backup". If you want to do an oline backup your VM must have follows requirments:

  • The Backup integration service must be enabled, so the operating system running on the virtual machine running must support Hyper-V integration services.
  • The guest operating system must support VSS (Windows 2003 server or later). Online backup isn’t supported if virtual machines are running Linux.
  • There should be no dynamic disks on the virtual machine.
  • All volumes must be NTFS
  • The VSS storage assigment for the volumes shouldn’t be modified.
  • The virtual machine must be running, and if the virtual machine is in a cluster the cluster resource group should be online. A Shadow Storage assignment of a volume inside the virtual machine mustn’t be explicitly set to a different volume other than itself.

YOu must share these information with your Microsoft support.

source:

https://technet.microsoft.com/en-us/library/hh757970.aspx?f=255&MSPPError=-2147217396

regards