Highlighted

Snapshot / checkpoint a windows 2016 server with VSS (Error 4201)

Hi, 

Pre info: I have a good working snapshot policy with 10-15 clients that i take checkpoint everyday all of the working clients is windows 2012r2. Then i have one windows 2016 and that one gives me error (read more below). 

  • Netbackup 8.0 on Windowns Server 2012r2 (latest greatest patch). 
  • Client on host netbackup 8.0 (but shouldnt be neede due to checkpoint/snapshot). 
  • Client os Windows 2016 (latest greatest). 
  • HyperV cluster with Windows 2012r2 (almost latest greatest one patch behind). 

I added the host through browse as I did with the other, no worries there. then started manually task: gives me error: 

2017-maj-10 12:52:05 - Info nbjm (pid=4932) starting backup job (jobid=514756) for client TBKONTEKWEB01, policy HYPV-SERVERS-DMZ, schedule Fullbackup_Daily
2017-maj-10 12:52:05 - Info nbjm (pid=4932) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=514756, request id:{8D546C81-5555-4E98-BB04-639EA9D9B67B})
2017-maj-10 12:52:05 - requesting resource bkbackupmed01_dedup
2017-maj-10 12:52:05 - requesting resource bkbackupmaster.borlange.local.NBU_CLIENT.MAXJOBS.TBKONTEKWEB01
2017-maj-10 12:52:05 - requesting resource bkbackupmaster.borlange.local.NBU_POLICY.MAXJOBS.HYPV-SERVERS-DMZ
2017-maj-10 12:52:05 - granted resource bkbackupmaster.borlange.local.NBU_CLIENT.MAXJOBS.TBKONTEKWEB01
2017-maj-10 12:52:05 - granted resource bkbackupmaster.borlange.local.NBU_POLICY.MAXJOBS.HYPV-SERVERS-DMZ
2017-maj-10 12:52:05 - granted resource MediaID=@aaaab;DiskVolume=PureDiskVolume;DiskPool=bkbackupmed01_dedup;Path=PureDiskVolume;StorageServer=bkbackupmed01.borlange.local;MediaServer=bkbackupmed01.borlange.local
2017-maj-10 12:52:05 - granted resource bkbackupmed01_dedup
2017-maj-10 12:52:05 - estimated 0 kbytes needed
2017-maj-10 12:52:05 - begin Parent Job
2017-maj-10 12:52:05 - begin Hyper-V: Start Notify Script
2017-maj-10 12:52:05 - Info RUNCMD (pid=8816) started
2017-maj-10 12:52:05 - Info RUNCMD (pid=8816) exiting with status: 0
Operation Status: 0
2017-maj-10 12:52:05 - end Hyper-V: Start Notify Script; elapsed time 0:00:00
2017-maj-10 12:52:05 - begin Hyper-V: Step By Condition
Operation Status: 0
2017-maj-10 12:52:05 - end Hyper-V: Step By Condition; elapsed time 0:00:00
Operation Status: 0
2017-maj-10 12:52:05 - end Parent Job; elapsed time 0:00:00
2017-maj-10 12:52:05 - begin Hyper-V: Create Snapshot
2017-maj-10 12:52:06 - started process bpbrm (pid=4272)
2017-maj-10 12:53:40 - Info bpbrm (pid=4272) TBKONTEKWEB01 is the host to backup data from
2017-maj-10 12:53:40 - Info bpbrm (pid=4272) reading file list for client
2017-maj-10 12:53:40 - Info bpbrm (pid=4272) start bpfis on client
2017-maj-10 12:53:40 - Info bpbrm (pid=4272) Starting create snapshot processing
2017-maj-10 12:53:41 - Info bpfis (pid=395212) Backup started
2017-maj-10 12:54:31 - Info bpfis (pid=395212) Backup type of VM is OFFLINE and configuration parameter [allowOfflineBackup] is not set. To backup this VM, set [allowOfflineBackup] configuration parameter.
2017-maj-10 12:54:31 - Critical bpbrm (pid=4272) from client TBKONTEKWEB01: FTL - vfm_freeze_commit: method: Hyper-V_v2, type: FIM, function: Hyper-V_v2_prepare
2017-maj-10 12:54:31 - Critical bpbrm (pid=4272) from client TBKONTEKWEB01: FTL - snapshot services: snapshot preparation failed: provider-private error.
2017-maj-10 12:54:31 - Critical bpbrm (pid=4272) from client TBKONTEKWEB01: FTL - vfm_freeze_commit: method: Hyper-V_v2, type: FIM, function: Hyper-V_v2_prepare
2017-maj-10 12:54:31 - Critical bpbrm (pid=4272) from client TBKONTEKWEB01: FTL - snapshot services: snapshot preparation failed: provider-private error.
2017-maj-10 12:54:31 - Critical bpbrm (pid=4272) from client TBKONTEKWEB01: FTL - snapshot processing failed, status 4201
2017-maj-10 12:54:31 - Critical bpbrm (pid=4272) from client TBKONTEKWEB01: FTL - snapshot creation failed, status 4201
2017-maj-10 12:54:31 - Warning bpbrm (pid=4272) from client TBKONTEKWEB01: WRN - ALL_LOCAL_DRIVES is not frozen
2017-maj-10 12:54:31 - Info bpfis (pid=395212) done. status: 4201
2017-maj-10 12:54:31 - end writing
Operation Status: 4201
2017-maj-10 12:54:31 - end Hyper-V: Create Snapshot; elapsed time 0:02:26
2017-maj-10 12:54:31 - begin Hyper-V: Stop On Error
Operation Status: 0
2017-maj-10 12:54:31 - end Hyper-V: Stop On Error; elapsed time 0:00:00
2017-maj-10 12:54:31 - begin Hyper-V: Delete Snapshot
2017-maj-10 12:54:31 - end Hyper-V: Delete Snapshot; elapsed time 0:00:00
2017-maj-10 12:54:31 - Info bpfis (pid=395212) done. status: 4201: Incorrect snapshot method configuration or snapshot method not compatible for protecting backup selection entries.
2017-maj-10 12:54:32 - started process bpbrm (pid=7280)
2017-maj-10 12:55:21 - Info bpbrm (pid=7280) Starting delete snapshot processing
2017-maj-10 12:55:23 - Info bpfis (pid=396560) Backup started
2017-maj-10 12:55:23 - Warning bpbrm (pid=7280) from client TBKONTEKWEB01: cannot open C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.TBKONTEKWEB01_1494413525.1.0
2017-maj-10 12:55:23 - Info bpfis (pid=396560) done. status: 4207
2017-maj-10 12:55:23 - Info bpfis (pid=396560) done. status: 4207: Could not fetch snapshot metadata or state files
2017-maj-10 12:55:23 - end writing
Operation Status: 4207
2017-maj-10 12:55:23 - begin Hyper-V: End Notify Script
2017-maj-10 12:55:23 - Info RUNCMD (pid=11596) started
2017-maj-10 12:55:23 - Info RUNCMD (pid=11596) exiting with status: 0
Operation Status: 0
2017-maj-10 12:55:23 - end Hyper-V: End Notify Script; elapsed time 0:00:00
Operation Status: 4201
Incorrect snapshot method configuration or snapshot method not compatible for protecting backup selection entries (4201)

Regards PoNuts

Tags (2)
1 Solution

Accepted Solutions
Accepted Solution!

Re: Snapshot / checkpoint a windows 2016 server with VSS (Error 4201)

This is how it worked fine for me.. 

It's a close hybird solution to this backup/snapshot issue.. What i did was Changeing the Policy / Hyper-V / Advanced "Provider Type (0-auto 1-system 2-software 3-hardware) to 2-Software instead of 0-auto

Then it takes the backup without shutingdown the virtualhost. 

Yes.. there is still an issue left why we cannot take 100% vss snapshot without getting this "lockhost" minor than 10 sec. But for our consern it worksfine.. And our enviroment as desc. above is that we have not an genuin windows 2016 hyper-v cluster which in this case would be to prefer. 

Regards Pontus Ankarbåge

View solution in original post

Tags (2)
6 Replies

Re: Snapshot / checkpoint a windows 2016 server with VSS (Error 4201)

Is this setting adjusted ?

2017-maj-10 12:54:31 - Info bpfis (pid=395212) Backup type of VM is OFFLINE and configuration parameter [allowOfflineBackup] is not set. To backup this VM, set [allowOfflineBackup] configuration parameter.

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

Re: Snapshot / checkpoint a windows 2016 server with VSS (Error 4201)

In that case it shutdown the machine and take backup? And that i dont want to do..

The reg-hack didnt help. 

And all other clients (windows server 2012r2) works superb. 

Re: Snapshot / checkpoint a windows 2016 server with VSS (Error 4201)

Not sure that a Windows 2016 VM can run backup through a Hyper-V 2012R2, as the backup method differs between Windows 2012R2 Hyper-V (VSS) and Windows 2016 Hyper-V (WMI).

 

 

The standard questions: Have you checked: 1) What has changed. 2) The manual 3) If there are any tech notes or VOX posts regarding the issue

Re: Snapshot / checkpoint a windows 2016 server with VSS (Error 4201)

Hi,

I found this information from Netbackup Support for NetBackup 7.x and 8.x in virtual environments. Have you opportunity to check this? See attached.

Hyper-V online backups with VSS require the proper version of Hyper-V integration services in the VM
To allow online backups of Hyper-V virtual machines using the VSS backup method, the proper version of the Hyper-V integration services must be installed in the virtual machines. Without the proper version, online backup may not succeed (NetBackup status 4201). The following may appear in the job's detailed status log:
2/17/2014 1:39:17 PM - Critical bpbrm(pid=7492) from client RHEL_60_GPT:FTL - snapshot processing failed, status 4201

2/17/2014 1:39:17 PM - Critical bpbrm(pid=7492) from client RHEL_60_GPT: FTL - snapshot creation failed, status 4201

Note: The WMI backup method (for Hyper-V Server 2016 and later) does not employ
online vs. offline backups.

For more information on the WMI method, see the
NetBackup for Hyper-V Administrator’s Guide for 8.0, available here:
http://www.veritas.com/docs/000003214

 Guest OS Notes and requirements on the integration services in the VM Required minimum versions of integration services:
■ Hyper-V server 2016: Integration services are automatically updated.
■ Hyper-V server 2012 R2: Integration services 6.3.9600.16384.
■ Hyper-V server 2012: The integration services are built in to the Windows 2012 guest OS.

For other guest operating systems, see "Software requirements (for supported guest operating
systems)" in the following Microsoft TechNet article: http://technet.microsoft.com/library/hh831531

■ Hyper-V server 2008 R2: Integration services 6.1.7600.16385
■ Hyper-V server 2008: Integration services 6.0.6001.18016.
To upgrade the integration services, see the TechNet article "Install Hyper-V and create a virtual machine:"
http://technet.microsoft.com/en-US/library/hh846766

Regards,

Thiago

Accepted Solution!

Re: Snapshot / checkpoint a windows 2016 server with VSS (Error 4201)

This is how it worked fine for me.. 

It's a close hybird solution to this backup/snapshot issue.. What i did was Changeing the Policy / Hyper-V / Advanced "Provider Type (0-auto 1-system 2-software 3-hardware) to 2-Software instead of 0-auto

Then it takes the backup without shutingdown the virtualhost. 

Yes.. there is still an issue left why we cannot take 100% vss snapshot without getting this "lockhost" minor than 10 sec. But for our consern it worksfine.. And our enviroment as desc. above is that we have not an genuin windows 2016 hyper-v cluster which in this case would be to prefer. 

Regards Pontus Ankarbåge

View solution in original post

Tags (2)

Re: Snapshot / checkpoint a windows 2016 server with VSS (Error 4201)

Nice to know that it can be brought to work.

The standard questions: Have you checked: 1) What has changed. 2) The manual 3) If there are any tech notes or VOX posts regarding the issue