VMware

This Question is Possibly Answered

1 "correct" answer available (10 pts) 2 "helpful" answers available (6 pts)
4 Replies Last post: Nov 10, 2009 9:20 AM by Smoggy  

Error Creating Protection Groups: "Virtual machine could not be created on recovery site: Resource pool, datastore and host specified for shadow virtual machine are not compatible with each other" posted: Jun 8, 2009 9:47 AM

Click to view kweller's profile Novice
kweller
5 posts since
Mar 28, 2005

Thanks in advance for the help. I'm seeing the following message for each VM when trying to create a protection group: "Virtual machine could not be created on recovery site: Resource pool,
datastore and host specified for shadow virtual machine are not
compatible with each other" I have checked my inventory mappings and everything seems to be fine.

Environment: VC 2.5 / ESX 3.5U3 / SRM 1.0.1-128004

Note: My ESX hosts boot from SAN so from time to time the MAC address or the FC WWNs on the protected or recovery site will change. Should this matter?

SRM log excerpt below:

2009-06-08 11:56:00.297 'com.vmware.vcDr.ReplicationGroup.AddVmTask-Task' 3336 verbose Task created
2009-06-08 11:56:00.297 'SimpleTaskManager' 3336 verbose Adding task com.vmware.vcDr.ReplicationGroup.AddVmTask-2
2009-06-08 11:56:00.297 'com.vmware.vcDr.ReplicationGroup.AddVmTask-Task' 3336 info State set to running
2009-06-08 11:56:00.297 'com.vmware.vcDr.ReplicationGroup.AddVmTask-Task' 3336 verbose Scheduling work item
2009-06-08 11:56:00.297 'com.vmware.vcDr.ReplicationGroup.AddVmTask-Task' 3336 verbose Task created
2009-06-08 11:56:00.297 'SimpleTaskManager' 3336 verbose Adding task com.vmware.vcDr.ReplicationGroup.AddVmTask-3
2009-06-08 11:56:00.297 'com.vmware.vcDr.ReplicationGroup.AddVmTask-Task' 3336 info State set to running
2009-06-08 11:56:00.297 'com.vmware.vcDr.ReplicationGroup.AddVmTask-Task' 3336 verbose Scheduling work item
2009-06-08 11:56:00.297 'com.vmware.vcDr.ReplicationGroup.AddVmTask-Task' 3336 verbose Task created
2009-06-08 11:56:00.297 'SimpleTaskManager' 3336 verbose Adding task com.vmware.vcDr.ReplicationGroup.AddVmTask-4
2009-06-08 11:56:00.297 'com.vmware.vcDr.ReplicationGroup.AddVmTask-Task' 3336 info State set to running
2009-06-08 11:56:00.297 'com.vmware.vcDr.ReplicationGroup.AddVmTask-Task' 3336 verbose Scheduling work item
2009-06-08 11:56:00.297 'com.vmware.vcDr.ReplicationGroup.AddVmTask-Task' 3432 info Running work method
2009-06-08 11:56:00.297 'com.vmware.vcDr.ReplicationGroup.AddVmTask-Task' 3432 info Work function yielded
2009-06-08 11:56:00.297 'com.vmware.vcDr.ReplicationGroup.AddVmTask-Task' 1064 info Running work method
2009-06-08 11:56:00.297 'com.vmware.vcDr.ReplicationGroup.AddVmTask-Task' 1064 info Work function yielded
2009-06-08 11:56:00.297 'com.vmware.vcDr.ReplicationGroup.AddVmTask-Task' 3288 info Running work method
2009-06-08 11:56:00.297 'com.vmware.vcDr.ReplicationGroup.AddVmTask-Task' 3288 info Work function yielded
2009-06-08 11:56:00.609 'PrimarySanProvider' 3448 trivia 'Retrieved 4 properties of 1 objects of type 'vim.VirtualMachine'' took 0.046 seconds
2009-06-08 11:56:00.625 'PrimarySanProvider' 3448 trivia 'Retrieved 1 properties of 1 objects of type 'vim.Datastore'' took 0.015 seconds
2009-06-08 11:56:00.625 'PrimarySanProvider' 3448 trivia VM 'vm-181' has no snapshots
2009-06-08 11:56:00.625 'PrimarySanProvider' 3448 trivia 'Retrieved 4 properties of 1 objects of type 'vim.VirtualMachine'' took 0 seconds
2009-06-08 11:56:00.625 'PrimarySanProvider' 3448 trivia 'Retrieved 1 properties of 1 objects of type 'vim.Datastore'' took 0 seconds
2009-06-08 11:56:00.625 'PrimarySanProvider' 3448 trivia VM 'vm-189' has no snapshots
2009-06-08 11:56:00.640 'PrimarySanProvider' 3448 trivia 'Retrieved 4 properties of 1 objects of type 'vim.VirtualMachine'' took 0.015 seconds
2009-06-08 11:56:00.640 'PrimarySanProvider' 3448 trivia 'Retrieved 1 properties of 1 objects of type 'vim.Datastore'' took 0 seconds
2009-06-08 11:56:00.640 'PrimarySanProvider' 3448 trivia VM 'vm-652' has no snapshots
2009-06-08 11:56:00.640 'Replication' 3448 verbose Protected VM 'vim.VirtualMachine:vm-181' device '4000' being mirrored
2009-06-08 11:56:00.640 'Replication' 3448 verbose Protected VM 'vim.VirtualMachine:vm-181' device '2000' being mirrored
2009-06-08 11:56:00.656 'Replication' 3448 verbose Protected VM 'vim.VirtualMachine:vm-189' device '4000' being mirrored
2009-06-08 11:56:00.656 'Replication' 3448 verbose Protected VM 'vim.VirtualMachine:vm-189' device '2000' being mirrored
2009-06-08 11:56:00.656 'Replication' 3448 verbose Protected VM 'vim.VirtualMachine:vm-652' device '4000' being mirrored
2009-06-08 11:56:00.656 'Replication' 3448 verbose Protected VM 'vim.VirtualMachine:vm-652' device '2000' being mirrored
2009-06-08 11:56:01.312 'com.vmware.vcDr.ReplicationGroup.AddVmTask-Task' 3480 verbose Progress is unchanged
2009-06-08 11:56:01.312 'com.vmware.vcDr.ReplicationGroup.AddVmTask-Task' 3480 verbose Progress is unchanged
2009-06-08 11:56:01.312 'com.vmware.vcDr.ReplicationGroup.AddVmTask-Task' 3480 verbose Progress advanced to 90
2009-06-08 11:56:01.312 'Replication' 3480 verbose Creation of shadow VM failed with error (dr.secondary.fault.WrongVmInventoryPlacement) {
1 dynamicType = <unset>,
1 resourcePool = 'vim.ResourcePool:resgroup-584',
1 datastore = 'vim.Datastore:datastore-625',
1 host = 'vim.HostSystem:host-585',
1 msg = "Resource pool, datastore and host specified for shadow virtual machine are not compatible with each other."
1 }
2009-06-08 11:56:01.312 'com.vmware.vcDr.ReplicationGroup.AddVmTask-Task' 3480 verbose Error set to (dr.primary.fault.RemoteAddVmFault) {
1 dynamicType = <unset>,
1 remoteFault = (dr.secondary.fault.WrongVmInventoryPlacement) {
1 dynamicType = <unset>,
1 resourcePool = 'vim.ResourcePool:resgroup-584',
1 datastore = 'vim.Datastore:datastore-625',
1 host = 'vim.HostSystem:host-585',
1 msg = "Resource pool, datastore and host specified for shadow virtual machine are not compatible with each other."
1 },
1 msg = ""
1 }
2009-06-08 11:56:01.312 'com.vmware.vcDr.ReplicationGroup.AddVmTask-Task' 3480 info State set to error
2009-06-08 11:56:01.312 'com.vmware.vcDr.ReplicationGroup.AddVmTask-Task' 3480 verbose Progress is unchanged
2009-06-08 11:56:01.312 'com.vmware.vcDr.ReplicationGroup.AddVmTask-Task' 3480 verbose Progress advanced to 90
2009-06-08 11:56:01.312 'Replication' 3480 verbose Creation of shadow VM failed with error (dr.secondary.fault.WrongVmInventoryPlacement) {
1 dynamicType = <unset>,
1 resourcePool = 'vim.ResourcePool:resgroup-584',
1 datastore = 'vim.Datastore:datastore-625',
1 host = 'vim.HostSystem:host-585',
1 msg = "Resource pool, datastore and host specified for shadow virtual machine are not compatible with each other."
1 }
2009-06-08 11:56:01.312 'com.vmware.vcDr.ReplicationGroup.AddVmTask-Task' 3480 verbose Error set to (dr.primary.fault.RemoteAddVmFault) {
1 dynamicType = <unset>,
1 remoteFault = (dr.secondary.fault.WrongVmInventoryPlacement) {
1 dynamicType = <unset>,
1 resourcePool = 'vim.ResourcePool:resgroup-584',
1 datastore = 'vim.Datastore:datastore-625',
1 host = 'vim.HostSystem:host-585',
1 msg = "Resource pool, datastore and host specified for shadow virtual machine are not compatible with each other."
1 },
1 msg = ""
1 }
2009-06-08 11:56:01.312 'com.vmware.vcDr.ReplicationGroup.AddVmTask-Task' 3480 info State set to error
2009-06-08 11:56:01.531 'com.vmware.vcDr.ReplicationGroup.AddVmTask-Task' 1064 verbose Progress advanced to 90
2009-06-08 11:56:01.531 'Replication' 1064 verbose Creation of shadow VM failed with error (dr.secondary.fault.WrongVmInventoryPlacement) {
1 dynamicType = <unset>,
1 resourcePool = 'vim.ResourcePool:resgroup-584',
1 datastore = 'vim.Datastore:datastore-625',
1 host = 'vim.HostSystem:host-585',
1 msg = "Resource pool, datastore and host specified for shadow virtual machine are not compatible with each other."
1 }
2009-06-08 11:56:01.531 'com.vmware.vcDr.ReplicationGroup.AddVmTask-Task' 1064 verbose Error set to (dr.primary.fault.RemoteAddVmFault) {
1 dynamicType = <unset>,
1 remoteFault = (dr.secondary.fault.WrongVmInventoryPlacement) {
1 dynamicType = <unset>,
1 resourcePool = 'vim.ResourcePool:resgroup-584',
1 datastore = 'vim.Datastore:datastore-625',
1 host = 'vim.HostSystem:host-585',
1 msg = "Resource pool, datastore and host specified for shadow virtual machine are not compatible with each other."
1 },
1 msg = ""
1 }
2009-06-08 11:56:01.531 'com.vmware.vcDr.ReplicationGroup.AddVmTask-Task' 1064 info State set to error

Re: Error Creating Protection Groups: "Virtual machine could not be created on recovery site: Resource pool, datastore and host specified for shadow virtual machine are not compatible with each other"

2. Nov 6, 2009 5:53 AM in response to: kweller
Click to view BjornJohansson's profile Enthusiast
BjornJohansson
56 posts since
Sep 22, 2005

Hello,

Check that all ESX hosts has the same patch levels, check version in VI Client.

/Björn

Re: Error Creating Protection Groups: "Virtual machine could not be created on recovery site: Resource pool, datastore and host specified for shadow virtual machine are not compatible with each other"

3. Nov 6, 2009 7:22 AM in response to: kweller
Click to view lmilev's profile Novice
lmilev
3 posts since
Jul 1, 2008

Hello,

Have you checked the logs on the remote site for more details?

On the recovery site - Could it be that the datastore used to keep the .vmx files for the vms of a protection group is not visible by hosts which are recommended by Inventory Mappings?

Thank you,

Lyuben

Re: Error Creating Protection Groups: "Virtual machine could not be created on recovery site: Resource pool, datastore and host specified for shadow virtual machine are not compatible with each other"

4. Nov 10, 2009 9:20 AM in response to: kweller
Click to view Smoggy's profile Hot Shot
Smoggy
187 posts since
Nov 9, 2005
check that ALL hosts at the recovery site can see the placeholder VM datastore. If any one of them cannot access it then you will see this error.

i have also seen this error caused when customers have for some reason installed one SRM server at the protected site on to say an AD server (not really bes practice) and then the recovery site SRM server onto an AD member server. They have then configured site pairing using a local rather than domain account so verify you've been consistent with the accounts used during your setup otherwise it will cause this issue.

hope that helps,
Lee

Actions

VMware Developer

SDKs, APIs, Videos, Learn and much more in the Developer community.

Learn More

Developer Sample Code

Increase your developer productivity with VMware API sample code.

Learn More

VMworld Sessions & Labs

Online access to the latest VMworld Sessions & Labs and online services.

Learn more

Purchase PSO Credits Online

Purchase credits to redeem training and consulting services online.

Buy Now

Community Hardware Software

View reported configurations or report your own.

Learn More

VMware vSphere

Come witness the next giant leap in virtualization.

Register Today

Communities