cancel
Showing results for 
Search instead for 
Did you mean: 

Backup failing on Hyper-V 2012 Server

lalajee
Level 4

Hi,

We have windows 2012 STD R2 running on Windows Core 2008 R2.

All of the backups are running but only this 2012 server is not backing up.

 

03/29/2016 14:35:23 - Info nbjm (pid=5940) starting backup job (jobid=2512553) for client PC_NAME.DOMIAN.com, policy CLU01, schedule Weekly
03/29/2016 14:35:23 - Info nbjm (pid=5940) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=2512553, request id:{463A0D86-373C-419D-BCA2-5B81F6ECC223})
03/29/2016 14:35:23 - requesting resource dedupe_ssERVER.DOMIAN.com
03/29/2016 14:35:23 - requesting resource gbprbu01.NBU_CLIENT.MAXJOBS.PC_NAME.DOMIAN.com
03/29/2016 14:35:23 - requesting resource gbprbu01.NBU_POLICY.MAXJOBS.CLU01
03/29/2016 14:35:24 - granted resource  gbprbu01.NBU_CLIENT.MAXJOBS.PC_NAME.DOMIAN.com
03/29/2016 14:35:24 - granted resource  gbprbu01.NBU_POLICY.MAXJOBS.CLU01
03/29/2016 14:35:24 - granted resource  MediaID=@aaabK;DiskVolume=PureDiskVolume;DiskPool=dedupe_sERVER.DOMAIN.com;Path=PureDiskVolume;StorageServer=ssERVER.DOMAIN.com;MediaServer=ssERVER.DOMAIN.com
03/29/2016 14:35:24 - granted resource  dedupe_sERVER.DOMAIN.com
03/29/2016 14:35:24 - estimated 0 kbytes needed
03/29/2016 14:35:24 - begin Parent Job
03/29/2016 14:35:24 - begin Hyper-V: Start Notify Script
03/29/2016 14:35:25 - Info RUNCMD (pid=2956) started
03/29/2016 14:35:25 - Info RUNCMD (pid=2956) exiting with status: 0
Operation Status: 0
03/29/2016 14:35:25 - end Hyper-V: Start Notify Script; elapsed time 0:00:01
03/29/2016 14:35:25 - begin Hyper-V: Step By Condition
Operation Status: 0
03/29/2016 14:35:25 - end Hyper-V: Step By Condition; elapsed time 0:00:00
Operation Status: 0
03/29/2016 14:35:25 - end Parent Job; elapsed time 0:00:01
03/29/2016 14:35:25 - begin Hyper-V: Create Snapshot
03/29/2016 14:35:27 - started process bpbrm (pid=155356)
03/29/2016 14:36:08 - Info bpbrm (pid=155356) PC_NAME.DOMAIN.com is the host to backup data from
03/29/2016 14:36:08 - Info bpbrm (pid=155356) reading file list for client
03/29/2016 14:36:08 - Info bpbrm (pid=155356) start bpfis on client
03/29/2016 14:36:09 - Info bpbrm (pid=155356) Starting create snapshot processing
03/29/2016 14:36:10 - Info bpfis (pid=14300) Backup started
03/29/2016 14:36:53 - Info bpfis (pid=14300) Backup type of VM is OFFLINE and configuration parameter [allowOfflineBackup] is not set. To backup this VM, set [allowOfflineBackup] configuration parameter.
03/29/2016 14:36:53 - Critical bpbrm (pid=155356) from client PC_NAME.Domian.com: FTL - vfm_freeze_commit: method: Hyper-V_v2, type: FIM, function: Hyper-V_v2_prepare
03/29/2016 14:36:53 - Critical bpbrm (pid=155356) from client PC_NAME.Domian.com: FTL - snapshot services: snapshot preparation failed: provider-private error.
03/29/2016 14:36:53 - Critical bpbrm (pid=155356) from client PC_NAME.Domian.com: FTL - vfm_freeze_commit: method: Hyper-V_v2, type: FIM, function: Hyper-V_v2_prepare
03/29/2016 14:36:53 - Critical bpbrm (pid=155356) from client PC_NAME.Domian.com: FTL - snapshot services: snapshot preparation failed: provider-private error.
03/29/2016 14:36:53 - Critical bpbrm (pid=155356) from client PC_NAME.Domian.com: FTL - snapshot processing failed, status 4201

03/29/2016 14:36:53 - Critical bpbrm (pid=155356) from client PC_NAME.Domian.com: FTL - snapshot creation failed, status 4201

03/29/2016 14:36:53 - Warning bpbrm (pid=155356) from client PC_NAME.Domian.com: WRN - ALL_LOCAL_DRIVES is not frozen
03/29/2016 14:36:53 - Info bpfis (pid=14300) done. status: 4201

03/29/2016 14:36:53 - end Hyper-V: Create Snapshot; elapsed time 0:01:28
03/29/2016 14:36:53 - Info bpfis (pid=14300) done. status: 4201: Incorrect snapshot method configuration or snapshot method not compatible for protecting backup selection entries.
03/29/2016 14:36:53 - end writing
Operation Status: 4201

03/29/2016 14:36:53 - begin Hyper-V: Stop On Error
Operation Status: 0
03/29/2016 14:36:53 - end Hyper-V: Stop On Error; elapsed time 0:00:00
03/29/2016 14:36:53 - begin Hyper-V: Delete Snapshot
03/29/2016 14:36:56 - started process bpbrm (pid=155878)
03/29/2016 14:37:37 - Info bpbrm (pid=155878) Starting delete snapshot processing
03/29/2016 14:37:40 - Info bpfis (pid=11128) Backup started
03/29/2016 14:37:40 - Warning bpbrm (pid=155878) from client PC_NAME.Domian.com: cannot open C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.PC_NAME.Domian.com_1459258524.1.0
03/29/2016 14:37:41 - Info bpfis (pid=11128) done. status: 4207

03/29/2016 14:37:41 - end Hyper-V: Delete Snapshot; elapsed time 0:00:48
03/29/2016 14:37:41 - Info bpfis (pid=11128) done. status: 4207: Could not fetch snapshot metadata or state files
03/29/2016 14:37:41 - end writing
Operation Status: 4207

03/29/2016 14:37:41 - begin Hyper-V: End Notify Script
03/29/2016 14:37:41 - Info RUNCMD (pid=1900) started
03/29/2016 14:37:41 - Info RUNCMD (pid=1900) exiting with status: 0
Operation Status: 0
03/29/2016 14:37:41 - 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)

1 ACCEPTED SOLUTION

Accepted Solutions

lalajee
Level 4

Already try this patch/hotfix but still same problem. Spoken with Veritas who told me its Microsoft problem. Spoken with Microsoft and they told me Server 2012 R2 is not supported on 2008 R2

View solution in original post

13 REPLIES 13

Will_Restore
Level 6

You have to fix this

"Backup type of VM is OFFLINE and configuration parameter [allowOfflineBackup] is not set. To backup this VM, set [allowOfflineBackup] configuration parameter."

 

See technote: http://www.veritas.com/docs/000067981

 

lalajee
Level 4

we cant set the offline option of ploicy because that would interrupted system.

 

Capture.PNG

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified
Then you will simply need to accept that backup of offline VMs will fail.

lalajee
Level 4

The backups which are running on 2012 are online not offline.

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Then you need to troubleshoot the snapshot error.

 

Start with this TN:

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

lalajee
Level 4

I have  troubleshoot the snapshot error from this article but still having same problem

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

 

Everything is working but not with server 2012. If we installed VM Guest on server 2012 core then it works but when we installed the VM Guest  (Server 2012) on 2008 core then we get above failures

lalajee
Level 4

I have try all of the things which are in these 3 articles.

 

SCSI Controller is added in.

VSS integration service is enabled

I have remove the Backup service and then re-added back in again.

 

Still same problem

lalajee
Level 4


03/31/2016 11:00:13 - Info nbjm (pid=5940) starting backup job (jobid=2517533) for client SERVER.DOMAIN.com, policy VM_CLU01, schedule Daily
03/31/2016 11:00:13 - Info nbjm (pid=5940) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=2517533, request id:{CDE59E42-AC64-4D03-B779-3F7E8FF0B706})
03/31/2016 11:00:13 - requesting resource dedupe_SERVER.DOMAIN.com
03/31/2016 11:00:13 - requesting resource MASTER_SERVER.NBU_CLIENT.MAXJOBS.SERVER.DOMAIN.com
03/31/2016 11:00:13 - requesting resource MASTER_SERVER.NBU_POLICY.MAXJOBS.VM_CLU01
03/31/2016 11:00:13 - granted resource  MASTER_SERVER.NBU_CLIENT.MAXJOBS.SERVER.DOMAIN.com
03/31/2016 11:00:13 - granted resource  MASTER_SERVER.NBU_POLICY.MAXJOBS.VM_CLU01
03/31/2016 11:00:13 - granted resource  MediaID=@aaabK;DiskVolume=PureDiskVolume;DiskPool=dedupe_SERVER.DOMAIN.com;Path=PureDiskVolume;StorageServer=SERVER.DOMAIN.com;MediaServer=SERVER.DOMAIN.com
03/31/2016 11:00:13 - granted resource  dedupe_SERVER.DOMAIN.com
03/31/2016 11:00:14 - estimated 0 kbytes needed
03/31/2016 11:00:14 - begin Parent Job
03/31/2016 11:00:14 - begin Hyper-V: Start Notify Script
03/31/2016 11:00:14 - Info RUNCMD (pid=9660) started
03/31/2016 11:00:14 - Info RUNCMD (pid=9660) exiting with status: 0
Operation Status: 0
03/31/2016 11:00:14 - end Hyper-V: Start Notify Script; elapsed time 0:00:00
03/31/2016 11:00:14 - begin Hyper-V: Step By Condition
Operation Status: 0
03/31/2016 11:00:14 - end Hyper-V: Step By Condition; elapsed time 0:00:00
Operation Status: 0
03/31/2016 11:00:14 - end Parent Job; elapsed time 0:00:00
03/31/2016 11:00:14 - begin Hyper-V: Create Snapshot
03/31/2016 11:00:17 - started process bpbrm (pid=303955)
03/31/2016 11:00:57 - Info bpbrm (pid=303955) SERVER.DOMAIN.com is the host to backup data from
03/31/2016 11:00:57 - Info bpbrm (pid=303955) reading file list for client
03/31/2016 11:00:57 - Info bpbrm (pid=303955) start bpfis on client
03/31/2016 11:00:58 - Info bpbrm (pid=303955) Starting create snapshot processing
03/31/2016 11:00:59 - Info bpfis (pid=5060) Backup started
03/31/2016 11:01:42 - Info bpfis (pid=5060) Backup type of VM is OFFLINE and configuration parameter [allowOfflineBackup] is not set. To backup this VM, set [allowOfflineBackup] configuration parameter.
03/31/2016 11:01:42 - Critical bpbrm (pid=303955) from client SERVER.DOMAIN.com: FTL - vfm_freeze_commit: method: Hyper-V_v2, type: FIM, function: Hyper-V_v2_prepare
03/31/2016 11:01:42 - Critical bpbrm (pid=303955) from client SERVER.DOMAIN.com: FTL - snapshot services: snapshot preparation failed: provider-private error.
03/31/2016 11:01:42 - Critical bpbrm (pid=303955) from client SERVER.DOMAIN.com: FTL - vfm_freeze_commit: method: Hyper-V_v2, type: FIM, function: Hyper-V_v2_prepare
03/31/2016 11:01:42 - Critical bpbrm (pid=303955) from client SERVER.DOMAIN.com: FTL - snapshot services: snapshot preparation failed: provider-private error.
03/31/2016 11:01:42 - Critical bpbrm (pid=303955) from client SERVER.DOMAIN.com: FTL - snapshot processing failed, status 4201

03/31/2016 11:01:42 - Critical bpbrm (pid=303955) from client SERVER.DOMAIN.com: FTL - snapshot creation failed, status 4201

03/31/2016 11:01:42 - Warning bpbrm (pid=303955) from client SERVER.DOMAIN.com: WRN - ALL_LOCAL_DRIVES is not frozen
03/31/2016 11:01:42 - Info bpfis (pid=5060) done. status: 4201

03/31/2016 11:01:42 - end Hyper-V: Create Snapshot; elapsed time 0:01:28
03/31/2016 11:01:42 - Info bpfis (pid=5060) done. status: 4201: Incorrect snapshot method configuration or snapshot method not compatible for protecting backup selection entries.
03/31/2016 11:01:42 - end writing
Operation Status: 4201

03/31/2016 11:01:42 - begin Hyper-V: Stop On Error
Operation Status: 0
03/31/2016 11:01:42 - end Hyper-V: Stop On Error; elapsed time 0:00:00
03/31/2016 11:01:42 - begin Hyper-V: Delete Snapshot
03/31/2016 11:01:44 - started process bpbrm (pid=304668)
03/31/2016 11:02:25 - Info bpbrm (pid=304668) Starting delete snapshot processing
03/31/2016 11:02:27 - Info bpfis (pid=8572) Backup started
03/31/2016 11:02:27 - Warning bpbrm (pid=304668) from client SERVER.DOMAIN.com: cannot open C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.SERVER.DOMAIN.com_1459418413.1.0
03/31/2016 11:02:28 - Info bpfis (pid=8572) done. status: 4207

03/31/2016 11:02:28 - end Hyper-V: Delete Snapshot; elapsed time 0:00:46
03/31/2016 11:02:28 - Info bpfis (pid=8572) done. status: 4207: Could not fetch snapshot metadata or state files
03/31/2016 11:02:29 - end writing
Operation Status: 4207

03/31/2016 11:02:29 - begin Hyper-V: End Notify Script
03/31/2016 11:02:29 - Info RUNCMD (pid=11796) started
03/31/2016 11:02:29 - Info RUNCMD (pid=11796) exiting with status: 0
Operation Status: 0
03/31/2016 11:02:29 - 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)

 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

You will need to check logs to troubleshoot snapshot errors.

Have you created bpfis log folder as per the docs provided?
You will need to increase logging level to 3 or higher.

 

Khalid_Mashaykh
Level 4
Partner Accredited

Try to istall the below MS hotfix and try the backup again ..

https://support.microsoft.com/en-us/kb/3063283

 

 

lalajee
Level 4

Already try this patch/hotfix but still same problem. Spoken with Veritas who told me its Microsoft problem. Spoken with Microsoft and they told me Server 2012 R2 is not supported on 2008 R2

RamBS
Level 1

I had same issue recently on odd servers, but the issue is fixed once i have restarted follwing services

Volume shadow copy

Hyper-V volume shadow copy

Virtual disk service