VMware VC-SRM4-A - vCenter Site Recovery Manager Spécifications télécharger pdf (Page 34)

18. Execute an SRM recovery plan in the opposite direction as was done in the disaster recovery.

19. Verify the recovered environment and allow users to connect and continue normal business operations.

20. Reestablish primary-to-DR replication.

9.4 REESTABLISHING PRIMARY-TO-DR REPLICATION

Reestablishing normal operations requires the following processes:

1. Reversing the SnapMirror and SRM relationships again, to establish the original primary-to-DR site

replication and protection.

For more information, see the Resynchronizing SnapMirror section of the Data Protection Online

Backup and Recovery Guide for your version of Data ONTAP for instructions:

http://now.netapp.com/NOW/knowledge/docs/ontap/ontap_index.shtml.

2. Clean up all remaining unnecessary SnapMirror relationships using the SnapMirror release command

and by deleting Snapshot copies that were created for the temporary SnapMirror relationships as

necessary.

For more information, see the Releasing Partners from a SnapMirror Relationship section of the Data

Protection Online Backup and Recovery Guide for your version of Data ONTAP for instructions:

http://now.netapp.com/NOW/knowledge/docs/ontap/ontap_index.shtml.

3. Rebuild the original SRM protection groups and recovery plans.

Note: If the test button does not appear active after establishing protection for a virtual machine, verify

that there were no preexisting shadow virtual machine directories in the temporary datastore at the DR

site. If these directories exist, it might be necessary to delete and recreate the protection group for those

VMs. If these directories remain, they might prevent the ability to run a DR test or failover.

10 BEST PRACTICES

ENSURING THE QUICKEST STARTUP AT THE DR SITE

The ESX host used to start each VM in the recovery plan is the host on which the placeholder VM is

currently registered. To help make sure that multiple VMs can be started simultaneously you should spread

the placeholder VMs across ESX hosts before running the recovery plan. Make sure that in each step of the

recovery plan, for example high priority and normal priority, the VMs are separated onto different ESX hosts.

SRM will startup two VMs per ESX host while executing the recovery plan. For more information about SRM

VM startup performance see VMware vCenter Site Recovery Manager 4.0 Performance and Best Practices for

Performance at www.vmware.com/files/pdf/VMware-vCenter-SRM-WP-EN.pdf

NETAPP VOLUMES AND SRM PROTECTION GROUPS

Volume-based SnapMirror works by replicating Snapshot copies at the volume level. Because of this

NetApp volumes, or groups of volumes, work well as the basis for protection groups. If the data layout was

done according to the designs described in TR-3428, then NetApp volumes should map nicely to VMware

protection groups.

NETWORK FOR DR TESTING

Create a physical test bubble network by segregating a physical network or a VLAN to link the ESX test

bubble networks. A possible cost-free solution to consider is to use the physical infrastructure of the

VMotion® network at the DR site. VMware best practices recommend a separate VMotion network. If the DR

VMotion network is not utilized outside of DR activities or during DR testing and is already segregated from

the public network, then adding a test bubble network to the VMotion vSwitch can provide this infrastructure.

Make sure that this network is segregated using VLANs or VLAN tagging to isolate the IP addresses of the

DR virtual machines as they are recovered.

VIRTUAL MACHINE STARTUP DEPENDENCIES

In the protection group, set important infrastructure servers at high priority to make sure they are recovered

first. Also consider inserting a message step into the recovery plan after the step that recovers the high-

priority virtual machines. This will pause the execution of the recovery plan at this point. During a DR test or

true DR scenario verify the infrastructure services are available before other servers with dependencies are

recovered.

1 2 ... 29 30 31 32 33 34 35 36 37 38 39 ... 45 46

Commentaires sur ces manuels

Pas de commentaire

VMware VC-SRM4-A - vCenter Site Recovery Manager Spécifications Page 34

Commentaires sur ces manuels

Produits connexes et manuels pour Logiciel VMware VC-SRM4-A - vCenter Site Recovery Manager