VM protection that is the part of multiple consistency group

[RanjnaAggarwal]

if a vm is using multiple consistency group, can it be protected with srm?

[vbrowncoat]

What kind of VM are you referring to? If MSCS, this is supported by SRM (see: Site Recovery Manager 6.1 Documentation Center)

[RanjnaAggarwal]

Thanks Sir for reply. Any VM that is the Part of more than one consistency group.

[vbrowncoat]

How is a VM part of more than one consistency group? If it using LUN sharing see the link I sent you about MSCS prior.

[NikRaychev]

Hi,

If you are referring to a VM that has disks spanning on more that one consistency group than all consistency groups that VM spans will be grouped in a datastore grouped and when creating an ABR protection group you will protect that datastore group meaning all consistency groups the VM in question spans.

HTH,

Nik

[RanjnaAggarwal]

What if VM is migrated from datastore to another datastore, Will the protection group be updated automatically?

[NikRaychev]

If the new datastore is within the same datastore group meaning already protected in the PG then the protection group will stay in OK state. If the new datastore is not in the PG then the protection group will go into Not Configured state and you will have to edit the group and go through the edit protection group wizard in order to add the new datastore in the datastore group. It will be already added so you will just have to complete edit protection group wizard.

Nik

[RanjnaAggarwal]

This is really pain for someone ......let's assume storage vmotion is happening as storage drs is configured......as per my views datastore groups should be calculated based on the VM placement and it should be updated automatically in protection groups.

[NikRaychev]

I hear you. But automatic reconfiguration of ABR protection groups is not implemented.

Nik

[vbrowncoat]

SRM 6.0 and higher support using storage DRS & storage vMotion both for storage at the protected and recovery sites. Storage DRS has intelligence built into it so that it won't move a VM to storage that would result in the VM becoming unprotected (is not part of the same consistency group).

As was previously mentioned, if you are using array based replication and you manually storage vMotion a VM out of the consistency group it will break the protection for that VM. If you manually move it within the consistency group there will be no impact to protection.

If you are using vSphere Replication then storage vMotion doesn't have an impact on SRM protection regardless