Skip to main content

Posts

Showing posts from February, 2015

Site recovery manager and vsphere replication features

Overview of New Features in SRM and vSphere Replication vCenter Site Recovery Manager 5.5 and vSphere Replication 5.5 include a number of significant improvements and exciting new features

New features in vCenter Site Recovery Manager 5.5 include:
•New support for StorageDRS and Storage vMotion
•Full integration with vSphere 5.5  - Support for Multiple Recovery Points
New features in vSphere Replication include:
•New User Interface
•Flexible Replication Topologies
•Support for Multiple Point-in-Time Recovery Points
•Support for vSphere Distributed Storage

•Major Performance Improvements

What's New in vSphere Replication: Support for New Replication Topologies vSphere Replication is a feature of the vSphere platform. It copies a virtual machine to another location, within or between clusters, and makes that copy available for restoration through the VMware® vCenter Server™ Web-based user interface. vSphere Replication continues to protect the virtual machine on an ongoing basis. It replicates t…

USE VMware SITE RECOVERY MANAGER TO TEST DISASTER RECOVERY -Optimize the Disaster Recovery Plan

We have already done failover from prod to DR in my previous blog
USE VMware SITE RECOVERY MANAGER TO TEST DISASTER RECOVERY -1

Now we will Optimize the Disaster Recovery Plan
We will use the reporting features of Site Recovery Manager to view the test results and see if we can identify a problem and then reconfigure the recovery plan to address any issues
Review the dr test report for errors


If you've left the Recovery Plan page, navigate back and open the Customer Care Web App recovery plan. 1. Click on"History" 2. The report at the top of the list will be the cleanup operation we previously ran. Make sure you select the report for the Test instead, which should be the second item in the history. Click on"Export Report"
1. Leave the file format as "Web Page" and click"Generate Report."
The report for our DR test has been saved to the desktop. Minimize the open web browser and find the icon on the desktop for the saved report. Double click to open. …

USE VMware SITE RECOVERY MANAGER TO TEST DISASTER RECOVERY -2

This is a second part of BCDR using VMware SRM. The earlier blog USE VMware SITE RECOVERY MANAGER TO TEST DISASTER RECOVERY -1 contained failoing over to DR. In this blog we will failback

Now, we will fail the application BACK to Production DC, restoring it to the original location. Applications protected with SRM can be migrated back and forth as often as necessary for everything from disaster recovery/avoidance to simply avoiding downtime due to planned maintenance outages

Connect to production dc site

1. Open the vSphere Web Client for the Production DC vCenter.  From the home tab navigate to the Site Recovery plugin. We'll be running the planned failback from the Production DC site vCenter

Initiate recovery plan for planned migration'
Navigate to Recovery Plans. 1.Make sure that theCustomer Care Web Appis highlighted
2. Click the red button to recover the recovery plan. Start the disaster avoidance procedure We will use the same process that we followed when we originally failed ove…

USE VMware SITE RECOVERY MANAGER TO TEST DISASTER RECOVERY -1

Scenario:

In working with the business, IT has determined that they will protect the application with the following policy in mind.
•All workloads in Production DC will be protected and recovered using resources in the DR DC
•All workloads in DR DC will be protected and recovered using resources in the Production DC
•vSphere Replication will be used to protect all workloads to save cost since a recovery point objective of 15 minutes is acceptable for all Customer  data.

ENSURE VMS ARE BEING REPLICATED SUCCESSFULLY

We need to review the status.
1.Click on vSphere Replication in the left pane
2.Click on vc-01b.corp.local to select the local vCenter
3.Click on Monitor

VIEW VSPHERE REPLICATION STATUS

1.Make sure you have Outgoing Replications selected
2.View the status of outgoing VM replications. All should have "OK" as their status and have vc-01a.corp.local as their target. The status for some VMs may show an RPO violation instead of "OK". This is because of the way the Hands-…