SRM and NetApp SRA

VMware vCenter Site Recovery Manager enhances your ability to build, manage and execute reliable disaster recovery plans for your virtual environment.   I like to refer to it as the gold standard of automated DR.  Below is a short description of the key capabilities available.

  • Planned Migration.  You can run a recovery plan under planned circumstances to migrate virtual machines from the protected site to the recovery site. You can also run a recovery plan under unplanned circumstances if the protected site suffers an unforeseen event that might result in data loss.
  • Automated Reprotection. Reprotection is a new extension to recovery plans for use only with array-based replication. Automated re-protect enables the environment at the recovery site to establish replication and protection of the environment back to the original protected site through a single click.
  • Automated Failback. Automated failback returns the entire environment to the originally protected primary site. This can only happen after re-protection has ensured that data replication and synchronization have been established to the original primary site. Failback will run the same workflow that was used to migrate the environment to the protected site, ensuring that the critical systems encapsulated by the recovery plan are returned to their original environment. Automated failback, like re-protection, is only available for use with array-based replication protected virtual machines.

Below is a 3 part series of videos demonstrating the test recovery, planned migration and re-protection workflows.

My Lab:

  • ESXi\vCenter\Site Recovery Manager 5.1
  • NetApp FAS\V-Series Storage Replication Adapter 2.1
  • 2 X NetApp Data ONTAP Edge VSAs

Part 1 – Test Recovery Workflow

Testing a recovery plan exercises nearly every aspect of a recovery plan.  In a NetApp environment, Running a test recovery does not disrupt replication or ongoing activities at either site.   The SRA creates an instantaneous zero capacity writable FlexClone and mounts it to the recovery site for testing.  You can run test recoveries as often as necessary. You can also cancel a recovery plan test at any time.

Part 2 – Recovery Workflow

During a planned migration SRM synchronizes the virtual machines on the recovery site with the virtual machines on the protected site, then stops replication. SRM attempts to replicate all virtual machines and gracefully shut down the protected machines. If errors occur during a planned migration, the plan stops so that you can resolve the errors and rerun the plan. You can reprotect the virtual machines after the recovery.

Part 3 – Reprotect Workflow

The Reprotect workflow uses the protection information that you established before a recovery to reverse the direction of the SnapMirror replication. You can complete the reprotect process only after a recovery finishes

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s