EMC Celerra and VMware SRM Failback

Posted: February 5, 2009 in Celerra, Site Recovery Manager, VMware

As you might have read from a couple of my other posts, I recently configured replication between our 2x NS20’s and configured VMware SRM to protect a test lun with a clone of a Linux VM I have setup in production.

After the initial configuration I played with the “Test” button over and over, I was like a kid with a flash new toy. Once the novelty wore off I decided that i was going to need to perform a proper fail over where the replicated lun at the recovery site B would now be considered production, then make some changes to the data and then fail back to site A and hope it all works as it should.

Here are the steps required

  1. Reverse the replication direction in the storage layer to be from Site B to Site A
  2. Clean up the shadow virtual machines and protection groups on Site A
  3. Clean up the Recovery Plans configured on Site B
  4. Configure the protection group(s) on Site B
  5. Configure the Recovery Plans on Site A
  6. Test recovery from Site B to Site A
  7. Perform the recovery from Site B to Site A

The steps above are pretty straight forward and if you were the one who setup SRM in the first place you will have no problems. What I wanted to add here in this post was what you actually need to do for step 1 for the EMC Celerra fail back.

1.   Log into Celerra Manager at Site A

2.   Select the replication option from the left side panel

3.   Note the status of the replication “Failed Over” Select start, then select discard changes since last copy and then OK.

And thats it, move onto step 2  (Clean up the shadow virtual machines )

Advertisements

Leave a Reply

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

WordPress.com Logo

You are commenting using your WordPress.com 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 )

Google+ photo

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

Connecting to %s