08-30-2015 05:46 AM
Hello,
NetBackup 7.6.0.4
Standart OS Windows 2008 64 Bit
Windows Server 2012 R2 HyperV
When sauvragarde of HyperV machine cold, it ends successfully, but when I run the VM sauvrgarde hot error message "Incorrect configuration snapshot method or snapshot method not compliant for protecting protective backup selection entries. (4201 ) "
Solved! Go to Solution.
09-01-2015 01:22 AM
There is something about the configuration of the VM which dis-allows the feature of "on-line backup without suspension" - i.e. there is something about the VM that prevents an onlline backup of the running VM.
Take a look at this:
https://www-secure.symantec.com/connect/forums/hyper-v-vms-are-saved-state-after-backup
.
You may be able to allow backups to suspend the VM, but then this may not suit your environment. Remember, Hyper-V is no where near as advanced as VMware - in fact Microsoft's support for backups of their own hypervisor is pretty basic and fairly limited in support scope. At the moment Hyper-V is a cheap hypervisor, and I guess you're now finding out why it was so cheap.
09-01-2015 01:28 AM
For Hyper-V hot backup to works you have to ensure that all those conditions are met:
https://support.symantec.com/en_US/article.HOWTO70797.html#v19618155
Now, there is also a nasty Microsoft bug in Hyper-V 2012 R2 make the online backup throwing a 4207. To solve this, go to your WM properties / integration Services, unckeck the "backup" option then apply. Go back to properties, re-check the "backup" option and apply.
Fabrice
08-30-2015 06:24 AM
Error 4201 is a bit too generic for us to be able to help very much, e.g. lots of different causes:
https://www-secure.symantec.com/connect/forums/hyper-v-2012-r2-backups-failing-4201-nb-7603
https://support.symantec.com/en_US/article.TECH211023.html
https://www-secure.symantec.com/connect/de/forums/netbackup-76x-ms-hyper-v-2012-r2
.
Can you share the backup policy configuration details? And the virtual machine details please? Are all servers and all clients running NetBackup v7.6.0.4? Can you post entire job details - for the backup that works and for the backup that does not work, please? Thanks.
08-30-2015 07:52 AM
Hello,
virtual machines on Windows 2008 \ 2003 system
the server and the clients are running NetBackup v 7.6.0.4
retail for backup works
30/08/2015 15:21:54 - Info nbjm(pid=10956) starting backup job (jobid=749) for client Test, policy AZ-WIN-SAGE-TEST-F-D, schedule Full
30/08/2015 15:21:54 - Info nbjm(pid=10956) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=749, request id:{31EAD9E3-6D9A-4932-83EB-72CC1EE59506})
30/08/2015 15:21:54 - requesting resource NB2D
30/08/2015 15:21:54 - requesting resource dzazrpw29.NBU_CLIENT.MAXJOBS.Test
30/08/2015 15:21:54 - requesting resource dzazrpw29.NBU_POLICY.MAXJOBS.AZ-WIN-SAGE-TEST-F-D
30/08/2015 15:21:54 - granted resource dzazrpw29.NBU_CLIENT.MAXJOBS.Test
30/08/2015 15:21:54 - granted resource dzazrpw29.NBU_POLICY.MAXJOBS.AZ-WIN-SAGE-TEST-F-D
30/08/2015 15:21:54 - granted resource MediaID=@aaaab;Path=H:\NB2D;MediaServer=dzazrpw29
30/08/2015 15:21:54 - granted resource NB2D
30/08/2015 15:21:54 - estimated 0 Kbytes needed
30/08/2015 15:21:54 - begin Parent Job
30/08/2015 15:21:54 - begin Hyper-V, Start Notify Script
30/08/2015 15:21:54 - Info RUNCMD(pid=6392) started
30/08/2015 15:21:54 - Info RUNCMD(pid=6392) exiting with status: 0
Status 0
30/08/2015 15:21:54 - end Hyper-V, Start Notify Script; elapsed time: 0:00:00
30/08/2015 15:21:54 - begin Hyper-V, Step By Condition
Status 0
30/08/2015 15:21:54 - end Hyper-V, Step By Condition; elapsed time: 0:00:00
30/08/2015 15:21:54 - begin Hyper-V, Read File List
Status 0
30/08/2015 15:21:54 - end Hyper-V, Read File List; elapsed time: 0:00:00
30/08/2015 15:21:54 - begin Hyper-V, Create Snapshot
30/08/2015 15:21:54 - started
30/08/2015 15:21:55 - started process bpbrm (9064)
30/08/2015 15:22:07 - Info bpbrm(pid=9064) Test is the host to backup data from
30/08/2015 15:22:07 - Info bpbrm(pid=9064) reading file list for client
30/08/2015 15:22:07 - Info bpbrm(pid=9064) start bpfis on client
30/08/2015 15:22:08 - Info bpbrm(pid=9064) Starting create snapshot processing
30/08/2015 15:22:09 - Info bpfis(pid=9828) Backup started
30/08/2015 15:22:50 - Info bpfis(pid=9828) done. status: 0
30/08/2015 15:22:50 - end writing
Status 0
30/08/2015 15:22:50 - end Hyper-V, Create Snapshot; elapsed time: 0:00:56
30/08/2015 15:22:50 - Info nbjm(pid=10956) snapshotid=Test_1440944514
30/08/2015 15:22:50 - begin Hyper-V, Policy Execution Manager Preprocessed
30/08/2015 15:22:50 - end Hyper-V, Policy Execution Manager Preprocessed; elapsed time: 0:00:00
30/08/2015 15:22:50 - Info bpfis(pid=9828) done. status: 0: the requested operation was successfully completed
Status 0
30/08/2015 15:52:24 - end Parent Job; elapsed time: 0:30:30
30/08/2015 15:52:24 - begin Hyper-V, Validate Image
Status 0
30/08/2015 15:52:24 - end Hyper-V, Validate Image; elapsed time: 0:00:00
30/08/2015 15:52:24 - begin Hyper-V, Delete Snapshot
30/08/2015 15:52:24 - started process bpbrm (1508)
30/08/2015 15:52:34 - Info bpbrm(pid=1508) Starting delete snapshot processing
30/08/2015 15:52:38 - Info bpfis(pid=9272) Backup started
30/08/2015 15:52:45 - Info bpfis(pid=9272) done. status: 0
30/08/2015 15:52:45 - end Hyper-V, Delete Snapshot; elapsed time: 0:00:21
30/08/2015 15:52:45 - Info bpfis(pid=9272) done. status: 0: the requested operation was successfully completed
30/08/2015 15:52:45 - end writing
Status 0
30/08/2015 15:52:45 - end operation
30/08/2015 15:52:45 - begin Hyper-V, End Notify Script
30/08/2015 15:52:45 - Info RUNCMD(pid=8376) started
30/08/2015 15:52:45 - Info RUNCMD(pid=8376) exiting with status: 0
Status 0
30/08/2015 15:52:45 - end Hyper-V, End Notify Script; elapsed time: 0:00:00
Status 0
30/08/2015 15:52:45 - end operation
the requested operation was successfully completed(0)
////////////////////////////////////////////////////////////////////////////////////////////////
retail for backup does not work
30/08/2015 11:28:30 - Info nbjm(pid=10956) starting backup job (jobid=747) for client WSUS_Arzew, policy AZ-WIN-SAGE-TEST-F-D, schedule Full
30/08/2015 11:28:30 - Info nbjm(pid=10956) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=747, request id:{FBDAFA89-08C2-48EA-B20A-3041DEDC2AB0})
30/08/2015 11:28:30 - requesting resource NB2D
30/08/2015 11:28:30 - requesting resource dzazrpw29.NBU_CLIENT.MAXJOBS.WSUS_Arzew
30/08/2015 11:28:30 - requesting resource dzazrpw29.NBU_POLICY.MAXJOBS.AZ-WIN-SAGE-TEST-F-D
30/08/2015 11:28:30 - granted resource dzazrpw29.NBU_CLIENT.MAXJOBS.WSUS_Arzew
30/08/2015 11:28:30 - granted resource dzazrpw29.NBU_POLICY.MAXJOBS.AZ-WIN-SAGE-TEST-F-D
30/08/2015 11:28:30 - granted resource MediaID=@aaaab;Path=H:\NB2D;MediaServer=dzazrpw29
30/08/2015 11:28:30 - granted resource NB2D
30/08/2015 11:28:30 - estimated 0 Kbytes needed
30/08/2015 11:28:30 - begin Parent Job
30/08/2015 11:28:30 - begin Hyper-V, Start Notify Script
30/08/2015 11:28:30 - Info RUNCMD(pid=1096) started
30/08/2015 11:28:30 - Info RUNCMD(pid=1096) exiting with status: 0
Status 0
30/08/2015 11:28:30 - end Hyper-V, Start Notify Script; elapsed time: 0:00:00
30/08/2015 11:28:30 - begin Hyper-V, Step By Condition
Status 0
30/08/2015 11:28:30 - end Hyper-V, Step By Condition; elapsed time: 0:00:00
30/08/2015 11:28:30 - begin Hyper-V, Read File List
Status 0
30/08/2015 11:28:30 - end Hyper-V, Read File List; elapsed time: 0:00:00
30/08/2015 11:28:30 - begin Hyper-V, Create Snapshot
30/08/2015 11:28:30 - started
30/08/2015 11:28:31 - started process bpbrm (12684)
30/08/2015 11:28:42 - Info bpbrm(pid=12684) WSUS_Arzew is the host to backup data from
30/08/2015 11:28:42 - Info bpbrm(pid=12684) reading file list for client
30/08/2015 11:28:42 - Info bpbrm(pid=12684) start bpfis on client
30/08/2015 11:28:44 - Info bpbrm(pid=12684) Starting create snapshot processing
30/08/2015 11:28:45 - Info bpfis(pid=2980) Backup started
30/08/2015 11:29:13 - Critical bpbrm(pid=12684) from client WSUS_Arzew: FTL - vfm_freeze_commit: method: Hyper-V_v2, type: FIM, function: Hyper-V_v2_prepare
30/08/2015 11:29:13 - Critical bpbrm(pid=12684) from client WSUS_Arzew: FTL - snapshot services: snapshot preparation failed: provider-private error.
30/08/2015 11:29:13 - Critical bpbrm(pid=12684) from client WSUS_Arzew: FTL - vfm_freeze_commit: method: Hyper-V_v2, type: FIM, function: Hyper-V_v2_prepare
30/08/2015 11:29:13 - Critical bpbrm(pid=12684) from client WSUS_Arzew: FTL - snapshot services: snapshot preparation failed: provider-private error.
30/08/2015 11:29:13 - Critical bpbrm(pid=12684) from client WSUS_Arzew: FTL - snapshot processing failed, status 4201
30/08/2015 11:29:13 - Critical bpbrm(pid=12684) from client WSUS_Arzew: FTL - snapshot creation failed, status 4201
30/08/2015 11:29:13 - Warning bpbrm(pid=12684) from client WSUS_Arzew: WRN - ALL_LOCAL_DRIVES is not frozen
30/08/2015 11:29:13 - Info bpfis(pid=2980) done. status: 4201
30/08/2015 11:29:13 - end Hyper-V, Create Snapshot; elapsed time: 0:00:43
30/08/2015 11:29:13 - Info bpfis(pid=2980) done. status: 4201: Incorrect snapshot method configuration or snapshot method not compatible for protecting backup selection entries.
30/08/2015 11:29:13 - end writing
Status 4201
30/08/2015 11:29:13 - end Parent Job; elapsed time: 0:00:43
30/08/2015 11:29:13 - begin Hyper-V, Stop On Error
Status 0
30/08/2015 11:29:13 - end Hyper-V, Stop On Error; elapsed time: 0:00:00
30/08/2015 11:29:13 - begin Hyper-V, Delete Snapshot
30/08/2015 11:29:13 - started process bpbrm (8780)
30/08/2015 11:29:23 - Info bpbrm(pid=8780) Starting delete snapshot processing
30/08/2015 11:29:25 - Info bpfis(pid=11240) Backup started
30/08/2015 11:29:25 - Critical bpbrm(pid=8780) from client WSUS_Arzew: cannot open C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.WSUS_Arzew_1440930510.1.0
30/08/2015 11:29:26 - Info bpfis(pid=11240) done. status: 4207
30/08/2015 11:29:26 - end Hyper-V, Delete Snapshot; elapsed time: 0:00:13
30/08/2015 11:29:26 - Info bpfis(pid=11240) done. status: 4207: Could not fetch snapshot metadata or state files
30/08/2015 11:29:26 - end writing
Status 4207
30/08/2015 11:29:26 - end Parent Job; elapsed time: 0:00:56
30/08/2015 11:29:26 - begin Hyper-V, End Notify Script
30/08/2015 11:29:27 - Info RUNCMD(pid=3248) started
30/08/2015 11:29:27 - Info RUNCMD(pid=3248) exiting with status: 0
Status 0
30/08/2015 11:29:27 - end Hyper-V, End Notify Script; elapsed time: 0:00:01
Status 4201
30/08/2015 11:29:27 - end operation
Incorrect snapshot method configuration or snapshot method not compatible for protecting backup selection entries.(4201)
08-30-2015 09:15 AM
Post the bpfis log please
08-30-2015 10:51 AM
I think we should ignore the fact that one backup works yet another different backup does work. There are just too many variables between the two. I think we're better off concentrating on the client that fails.
Is the Hyper-V configuration a cluster of two or more Hyper-V hosts?
Does the VM named "WSUS_Arzew" reside upon a CSV volume?
You mention Windows 2003... is WSUS_Arzew a Windows 2003 guest?
08-31-2015 01:01 AM
Hello,
virtual machines on Windows 2008 system
the server and the clients are running NetBackup v 7.6.0.4
hereinafter retail the same VM, the backup was cold and the other warm
/////////////////////////////////////////////////////////////////////
retail for backup works
30/08/2015 15:21:54 - Info nbjm(pid=10956) starting backup job (jobid=749) for client Test, policy AZ-WIN-SAGE-TEST-F-D, schedule Full
30/08/2015 15:21:54 - Info nbjm(pid=10956) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=749, request id:{31EAD9E3-6D9A-4932-83EB-72CC1EE59506})
30/08/2015 15:21:54 - requesting resource NB2D
30/08/2015 15:21:54 - requesting resource dzazrpw29.NBU_CLIENT.MAXJOBS.Test
30/08/2015 15:21:54 - requesting resource dzazrpw29.NBU_POLICY.MAXJOBS.AZ-WIN-SAGE-TEST-F-D
30/08/2015 15:21:54 - granted resource dzazrpw29.NBU_CLIENT.MAXJOBS.Test
30/08/2015 15:21:54 - granted resource dzazrpw29.NBU_POLICY.MAXJOBS.AZ-WIN-SAGE-TEST-F-D
30/08/2015 15:21:54 - granted resource MediaID=@aaaab;Path=H:\NB2D;MediaServer=dzazrpw29
30/08/2015 15:21:54 - granted resource NB2D
30/08/2015 15:21:54 - estimated 0 Kbytes needed
30/08/2015 15:21:54 - begin Parent Job
30/08/2015 15:21:54 - begin Hyper-V, Start Notify Script
30/08/2015 15:21:54 - Info RUNCMD(pid=6392) started
30/08/2015 15:21:54 - Info RUNCMD(pid=6392) exiting with status: 0
Status 0
30/08/2015 15:21:54 - end Hyper-V, Start Notify Script; elapsed time: 0:00:00
30/08/2015 15:21:54 - begin Hyper-V, Step By Condition
Status 0
30/08/2015 15:21:54 - end Hyper-V, Step By Condition; elapsed time: 0:00:00
30/08/2015 15:21:54 - begin Hyper-V, Read File List
Status 0
30/08/2015 15:21:54 - end Hyper-V, Read File List; elapsed time: 0:00:00
30/08/2015 15:21:54 - begin Hyper-V, Create Snapshot
30/08/2015 15:21:54 - started
30/08/2015 15:21:55 - started process bpbrm (9064)
30/08/2015 15:22:07 - Info bpbrm(pid=9064) Test is the host to backup data from
30/08/2015 15:22:07 - Info bpbrm(pid=9064) reading file list for client
30/08/2015 15:22:07 - Info bpbrm(pid=9064) start bpfis on client
30/08/2015 15:22:08 - Info bpbrm(pid=9064) Starting create snapshot processing
30/08/2015 15:22:09 - Info bpfis(pid=9828) Backup started
30/08/2015 15:22:50 - Info bpfis(pid=9828) done. status: 0
30/08/2015 15:22:50 - end writing
Status 0
30/08/2015 15:22:50 - end Hyper-V, Create Snapshot; elapsed time: 0:00:56
30/08/2015 15:22:50 - Info nbjm(pid=10956) snapshotid=Test_1440944514
30/08/2015 15:22:50 - begin Hyper-V, Policy Execution Manager Preprocessed
30/08/2015 15:22:50 - end Hyper-V, Policy Execution Manager Preprocessed; elapsed time: 0:00:00
30/08/2015 15:22:50 - Info bpfis(pid=9828) done. status: 0: the requested operation was successfully completed
Status 0
30/08/2015 15:52:24 - end Parent Job; elapsed time: 0:30:30
30/08/2015 15:52:24 - begin Hyper-V, Validate Image
Status 0
30/08/2015 15:52:24 - end Hyper-V, Validate Image; elapsed time: 0:00:00
30/08/2015 15:52:24 - begin Hyper-V, Delete Snapshot
30/08/2015 15:52:24 - started process bpbrm (1508)
30/08/2015 15:52:34 - Info bpbrm(pid=1508) Starting delete snapshot processing
30/08/2015 15:52:38 - Info bpfis(pid=9272) Backup started
30/08/2015 15:52:45 - Info bpfis(pid=9272) done. status: 0
30/08/2015 15:52:45 - end Hyper-V, Delete Snapshot; elapsed time: 0:00:21
30/08/2015 15:52:45 - Info bpfis(pid=9272) done. status: 0: the requested operation was successfully completed
30/08/2015 15:52:45 - end writing
Status 0
30/08/2015 15:52:45 - end operation
30/08/2015 15:52:45 - begin Hyper-V, End Notify Script
30/08/2015 15:52:45 - Info RUNCMD(pid=8376) started
30/08/2015 15:52:45 - Info RUNCMD(pid=8376) exiting with status: 0
Status 0
30/08/2015 15:52:45 - end Hyper-V, End Notify Script; elapsed time: 0:00:00
Status 0
30/08/2015 15:52:45 - end operation
the requested operation was successfully completed(0)
////////////////////////////////////////////////////////////////////////////////////////////////
after I turn on the VM in question, I start backup
retail for backup does not work
31/08/2015 08:55:23 - Info nbjm(pid=10956) starting backup job (jobid=772) for client Test, policy AZ-WIN-SAGE-TEST-F-D, schedule Full
31/08/2015 08:55:23 - Info nbjm(pid=10956) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=772, request id:{1A3B9C3B-0AD4-4643-AF00-509723BF0058})
31/08/2015 08:55:23 - requesting resource NB2D
31/08/2015 08:55:23 - requesting resource dzazrpw29.NBU_CLIENT.MAXJOBS.Test
31/08/2015 08:55:23 - requesting resource dzazrpw29.NBU_POLICY.MAXJOBS.AZ-WIN-SAGE-TEST-F-D
31/08/2015 08:55:23 - granted resource dzazrpw29.NBU_CLIENT.MAXJOBS.Test
31/08/2015 08:55:23 - granted resource dzazrpw29.NBU_POLICY.MAXJOBS.AZ-WIN-SAGE-TEST-F-D
31/08/2015 08:55:23 - granted resource MediaID=@aaaab;Path=H:\NB2D;MediaServer=dzazrpw29
31/08/2015 08:55:23 - granted resource NB2D
31/08/2015 08:55:23 - estimated 0 Kbytes needed
31/08/2015 08:55:23 - begin Parent Job
31/08/2015 08:55:23 - begin Hyper-V, Start Notify Script
31/08/2015 08:55:23 - Info RUNCMD(pid=5448) started
31/08/2015 08:55:23 - Info RUNCMD(pid=5448) exiting with status: 0
Status 0
31/08/2015 08:55:23 - end Hyper-V, Start Notify Script; elapsed time: 0:00:00
31/08/2015 08:55:23 - begin Hyper-V, Step By Condition
Status 0
31/08/2015 08:55:23 - end Hyper-V, Step By Condition; elapsed time: 0:00:00
31/08/2015 08:55:23 - begin Hyper-V, Read File List
Status 0
31/08/2015 08:55:23 - end Hyper-V, Read File List; elapsed time: 0:00:00
31/08/2015 08:55:23 - begin Hyper-V, Create Snapshot
31/08/2015 08:55:23 - started process bpbrm (8452)
31/08/2015 08:55:23 - started
31/08/2015 08:55:40 - Info bpbrm(pid=8452) Test is the host to backup data from
31/08/2015 08:55:40 - Info bpbrm(pid=8452) reading file list for client
31/08/2015 08:55:40 - Info bpbrm(pid=8452) start bpfis on client
31/08/2015 08:55:41 - Info bpbrm(pid=8452) Starting create snapshot processing
31/08/2015 08:55:43 - Info bpfis(pid=4652) Backup started
31/08/2015 08:56:13 - Critical bpbrm(pid=8452) from client Test: FTL - vfm_freeze_commit: method: Hyper-V_v2, type: FIM, function: Hyper-V_v2_prepare
31/08/2015 08:56:13 - Critical bpbrm(pid=8452) from client Test: FTL - snapshot services: snapshot preparation failed: provider-private error.
31/08/2015 08:56:13 - Critical bpbrm(pid=8452) from client Test: FTL - vfm_freeze_commit: method: Hyper-V_v2, type: FIM, function: Hyper-V_v2_prepare
31/08/2015 08:56:13 - Critical bpbrm(pid=8452) from client Test: FTL - snapshot services: snapshot preparation failed: provider-private error.
31/08/2015 08:56:13 - Critical bpbrm(pid=8452) from client Test: FTL - snapshot processing failed, status 4201
31/08/2015 08:56:13 - Critical bpbrm(pid=8452) from client Test: FTL - snapshot creation failed, status 4201
31/08/2015 08:56:13 - Warning bpbrm(pid=8452) from client Test: WRN - ALL_LOCAL_DRIVES is not frozen
31/08/2015 08:56:13 - Info bpfis(pid=4652) done. status: 4201
31/08/2015 08:56:13 - end Hyper-V, Create Snapshot; elapsed time: 0:00:50
31/08/2015 08:56:13 - Info bpfis(pid=4652) done. status: 4201: Incorrect snapshot method configuration or snapshot method not compatible for protecting backup selection entries.
31/08/2015 08:56:13 - end writing
Status 4201
31/08/2015 08:56:13 - end Parent Job; elapsed time: 0:00:50
31/08/2015 08:56:13 - begin Hyper-V, Stop On Error
Status 0
31/08/2015 08:56:13 - end Hyper-V, Stop On Error; elapsed time: 0:00:00
31/08/2015 08:56:13 - begin Hyper-V, Delete Snapshot
31/08/2015 08:56:13 - started process bpbrm (9232)
31/08/2015 08:56:22 - Info bpbrm(pid=9232) Starting delete snapshot processing
31/08/2015 08:56:25 - Info bpfis(pid=16960) Backup started
31/08/2015 08:56:25 - Critical bpbrm(pid=9232) from client Test: cannot open C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.Test_1441007723.1.0
31/08/2015 08:56:26 - Info bpfis(pid=16960) done. status: 4207
31/08/2015 08:56:26 - end Hyper-V, Delete Snapshot; elapsed time: 0:00:13
31/08/2015 08:56:26 - Info bpfis(pid=16960) done. status: 4207: Could not fetch snapshot metadata or state files
31/08/2015 08:56:26 - end writing
Status 4207
31/08/2015 08:56:26 - end operation
31/08/2015 08:56:26 - begin Hyper-V, End Notify Script
31/08/2015 08:56:26 - Info RUNCMD(pid=12052) started
31/08/2015 08:56:26 - Info RUNCMD(pid=12052) exiting with status: 0
Status 0
31/08/2015 08:56:26 - end Hyper-V, End Notify Script; elapsed time: 0:00:00
Status 4201
31/08/2015 08:56:26 - end operation
Incorrect snapshot method configuration or snapshot method not compatible for protecting backup selection entries.(4201)
09-01-2015 01:22 AM
There is something about the configuration of the VM which dis-allows the feature of "on-line backup without suspension" - i.e. there is something about the VM that prevents an onlline backup of the running VM.
Take a look at this:
https://www-secure.symantec.com/connect/forums/hyper-v-vms-are-saved-state-after-backup
.
You may be able to allow backups to suspend the VM, but then this may not suit your environment. Remember, Hyper-V is no where near as advanced as VMware - in fact Microsoft's support for backups of their own hypervisor is pretty basic and fairly limited in support scope. At the moment Hyper-V is a cheap hypervisor, and I guess you're now finding out why it was so cheap.
09-01-2015 01:28 AM
For Hyper-V hot backup to works you have to ensure that all those conditions are met:
https://support.symantec.com/en_US/article.HOWTO70797.html#v19618155
Now, there is also a nasty Microsoft bug in Hyper-V 2012 R2 make the online backup throwing a 4207. To solve this, go to your WM properties / integration Services, unckeck the "backup" option then apply. Go back to properties, re-check the "backup" option and apply.
Fabrice