Unable to backup Windows server 2012 R2 in fail over cluster

[lalajee]

Hi,

We cant backup Windows 2012 R2 servers in our system if its part of failover cluster. Standalone 2012 R2 server are backup without any problems.

Currently we have all our servers 2008 R2 and failover cluster is same version as 2008 R2. 

06/01/2016 20:00:00 - Info nbjm (pid=5244) starting backup job (jobid=2623631) for client server.domain.com, policy po_name, schedule Daily
06/01/2016 20:00:00 - Info nbjm (pid=5244) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=2623631, request id:{7B34D0F5-5389-4FB6-A5B6-DC3BA13D9028})
06/01/2016 20:00:00 - requesting resource dedupe_server
06/01/2016 20:00:00 - requesting resource master_Server.NBU_CLIENT.MAXJOBS.server.domain.com
06/01/2016 20:00:00 - requesting resource master_Server.NBU_POLICY.MAXJOBS.po_name
06/01/2016 20:00:01 - awaiting resource dedupe_server. Maximum job count has been reached for the storage unit.
06/01/2016 20:21:10 - granted resource  master_Server.NBU_CLIENT.MAXJOBS.server.domain.com
06/01/2016 20:21:10 - granted resource  master_Server.NBU_POLICY.MAXJOBS.po_name
06/01/2016 20:21:10 - granted resource  MediaID=@aaabM;DiskVolume=PureDiskVolume;DiskPool=dedupe_server;Path=PureDiskVolume;StorageServer=Server.domain.com;MediaServer=Server.domain.com
06/01/2016 20:21:10 - granted resource  dedupe_server
06/01/2016 20:21:12 - estimated 0 kbytes needed
06/01/2016 20:21:12 - begin Parent Job
06/01/2016 20:21:12 - begin Hyper-V: Start Notify Script
06/01/2016 20:21:12 - Info RUNCMD (pid=12276) started
06/01/2016 20:21:12 - Info RUNCMD (pid=12276) exiting with status: 0
Operation Status: 0
06/01/2016 20:21:12 - end Hyper-V: Start Notify Script; elapsed time 0:00:00
06/01/2016 20:21:12 - begin Hyper-V: Step By Condition
Operation Status: 0
06/01/2016 20:21:12 - end Hyper-V: Step By Condition; elapsed time 0:00:00
Operation Status: 0
06/01/2016 20:21:12 - end Parent Job; elapsed time 0:00:00
06/01/2016 20:21:12 - begin Hyper-V: Create Snapshot
06/01/2016 20:21:13 - started process bpbrm (pid=210579)
06/01/2016 20:21:16 - Info bpbrm (pid=210579) server.domain.com is the host to backup data from
06/01/2016 20:21:16 - Info bpbrm (pid=210579) reading file list for client
06/01/2016 20:21:16 - Info bpbrm (pid=210579) start bpfis on client
06/01/2016 20:21:16 - Info bpbrm (pid=210579) Starting create snapshot processing
06/01/2016 20:21:17 - Info bpfis (pid=1436) Backup started
06/01/2016 20:21:41 - Critical bpbrm (pid=210579) from client server.domain.com: FTL - vfm_freeze_commit: method: Hyper-V_v2, type: FIM, function: Hyper-V_v2_prepare
06/01/2016 20:21:42 - Critical bpbrm (pid=210579) from client server.domain.com: FTL - snapshot services: snapshot preparation failed: provider-private error.
06/01/2016 20:21:42 - Critical bpbrm (pid=210579) from client server.domain.com: FTL - vfm_freeze_commit: method: Hyper-V_v2, type: FIM, function: Hyper-V_v2_prepare
06/01/2016 20:21:42 - Critical bpbrm (pid=210579) from client server.domain.com: FTL - snapshot services: snapshot preparation failed: provider-private error.
06/01/2016 20:21:42 - Critical bpbrm (pid=210579) from client server.domain.com: FTL - snapshot processing failed, status 4201

06/01/2016 20:21:42 - Critical bpbrm (pid=210579) from client server.domain.com: FTL - snapshot creation failed, status 4201

06/01/2016 20:21:42 - Warning bpbrm (pid=210579) from client server.domain.com: WRN - ALL_LOCAL_DRIVES is not frozen
06/01/2016 20:21:42 - Info bpfis (pid=1436) done. status: 4201

06/01/2016 20:21:42 - end Hyper-V: Create Snapshot; elapsed time 0:00:30
06/01/2016 20:21:42 - Info bpfis (pid=1436) done. status: 4201: Incorrect snapshot method configuration or snapshot method not compatible for protecting backup selection entries.
06/01/2016 20:21:42 - end writing
Operation Status: 4201

06/01/2016 20:21:42 - begin Hyper-V: Stop On Error
Operation Status: 0
06/01/2016 20:21:42 - end Hyper-V: Stop On Error; elapsed time 0:00:00
06/01/2016 20:21:42 - begin Hyper-V: Delete Snapshot
06/01/2016 20:21:43 - started process bpbrm (pid=210652)
06/01/2016 20:21:46 - Info bpbrm (pid=210652) Starting delete snapshot processing
06/01/2016 20:21:47 - Info bpfis (pid=7308) Backup started
06/01/2016 20:21:47 - Warning bpbrm (pid=210652) from client server.domain.com: cannot open C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.server.domain.com_1464808871.1.0
06/01/2016 20:21:48 - Info bpfis (pid=7308) done. status: 4207

06/01/2016 20:21:48 - end Hyper-V: Delete Snapshot; elapsed time 0:00:06
06/01/2016 20:21:48 - Info bpfis (pid=7308) done. status: 4207: Could not fetch snapshot metadata or state files
06/01/2016 20:21:48 - end writing
Operation Status: 4207

06/01/2016 20:21:48 - begin Hyper-V: End Notify Script
06/01/2016 20:21:48 - Info RUNCMD (pid=9132) started
06/01/2016 20:21:49 - Info RUNCMD (pid=9132) exiting with status: 0
Operation Status: 0
06/01/2016 20:21:49 - end Hyper-V: End Notify Script; elapsed time 0:00:01
Operation Status: 4201

Incorrect snapshot method configuration or snapshot method not compatible for protecting backup selection entries  (4201)
 

[lalajee]

06/02/2016 06:59:25 - Info nbjm (pid=5244) starting backup job (jobid=2625500) for client Server.domain.com, policy po_name, schedule Daily
06/02/2016 06:59:25 - Info nbjm (pid=5244) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=2625500, request id:{DFEE9E64-DB3F-4737-AF11-4E7F3E9364B3})
06/02/2016 06:59:25 - requesting resource dedupe_Server
06/02/2016 06:59:25 - requesting resource master_Server.NBU_CLIENT.MAXJOBS.Server.domain.com
06/02/2016 06:59:25 - requesting resource master_Server.NBU_POLICY.MAXJOBS.po_name
06/02/2016 06:59:25 - awaiting resource dedupe_Server. Maximum job count has been reached for the storage unit.
06/02/2016 07:06:43 - granted resource  master_Server.NBU_CLIENT.MAXJOBS.Server.domain.com
06/02/2016 07:06:43 - granted resource  master_Server.NBU_POLICY.MAXJOBS.po_name
06/02/2016 07:06:43 - granted resource  MediaID=@aaabM;DiskVolume=PureDiskVolume;DiskPool=dedupe_Server;Path=PureDiskVolume;StorageServer=Server.domain.com;MediaServer=Server.domain.com
06/02/2016 07:06:43 - granted resource  dedupe_Server
06/02/2016 07:06:44 - estimated 288602523 kbytes needed
06/02/2016 07:06:44 - begin Parent Job
06/02/2016 07:06:44 - begin Hyper-V: Start Notify Script
06/02/2016 07:06:44 - Info RUNCMD (pid=4680) started
06/02/2016 07:06:44 - Info RUNCMD (pid=4680) exiting with status: 0
Operation Status: 0
06/02/2016 07:06:44 - end Hyper-V: Start Notify Script; elapsed time 0:00:00
06/02/2016 07:06:44 - begin Hyper-V: Step By Condition
Operation Status: 0
06/02/2016 07:06:44 - end Hyper-V: Step By Condition; elapsed time 0:00:00
Operation Status: 0
06/02/2016 07:06:44 - end Parent Job; elapsed time 0:00:00
06/02/2016 07:06:44 - begin Hyper-V: Create Snapshot
06/02/2016 07:06:45 - started process bpbrm (pid=147169)
06/02/2016 07:07:21 - Error bpbrm (pid=147169) Nameuse [0], VM [Server.domain.com] not found on any node. Is either powered off or does not exist.
06/02/2016 07:07:22 - Info bpbkar (pid=0) done. status: 48: client hostname could not be found
06/02/2016 07:07:22 - end writing
Operation Status: 48

06/02/2016 07:07:22 - end Hyper-V: Create Snapshot; elapsed time 0:00:38
06/02/2016 07:07:22 - begin Hyper-V: Stop On Error
Operation Status: 0
06/02/2016 07:07:22 - end Hyper-V: Stop On Error; elapsed time 0:00:00
06/02/2016 07:07:22 - begin Hyper-V: End Notify Script
06/02/2016 07:07:22 - Info RUNCMD (pid=8396) started
06/02/2016 07:07:22 - Info RUNCMD (pid=8396) exiting with status: 0
Operation Status: 0
06/02/2016 07:07:22 - end Hyper-V: End Notify Script; elapsed time 0:00:00
Operation Status: 48

client hostname could not be found  (48)
 

[lalajee]

Our storage is netapp

[lalajee · Accepted solution]

This was fix by changing the settings in policy.

Go to Hyper-V tab ->  click on Advance button.

Change the provider Type: Software

Thats it.

This is only if you have server 2012 r2 in failover cluster