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 PoNutsSolved4KViews0likes6Comments