Skip to main content

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 the Customer Care Web App is 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 over to DR DC.
1. Check the check box indicating that you understand the risks of a failover.
2. Make sure that you select Planned Migration.
3. Click Next and then Finish

Monitor the plan while it runs.

Once the plan is complete, it is important that we reprotect the Customer Care Web App as soon as possible.
1. Click the Reprotect button
Make sure to click the checkbox to confirm you understand what will be occurring during the operation before clicking Next. As with the previous Reprotect operation, this may take up to 20 minutes while the protected VMs are replicated back to DR DC

After the plan completes, verify that SRM is now protecting Production DC using resources in Albuquerque.
1. Click on the Summary tab
2. Ensure that Production DC is listed as the Protected site and DR DCas the Recovery Site.
That's it! You've failed a critical application over from one site to another to avoid a disaster, failed it back and used reprotect to make sure that it was protected from disaster regardless of the site in which it was running. 

Popular posts from this blog

HP CSA Implementation

I know the above picture is little confusing but don’t worry I break it down and explain in detail. By the time I am done explaining you all will be happy. HARDWARE AND SOFTWARE REQUIREMENTS 1.VMware vSphere infrastructure / Microsoft Hyper V: For the sake of Simplicity we will use VMware vSphere. We Need vSphere 4.0 /5/5.5 and above and vCenter 4.0 and above ready and installed. This is the first step. 2.We need Software medias for HP Cloud Service Automation, 2.00, HP Server Automation, 9.02, HP Operations Orchestration (OO)9.00.04, HP Universal CMDB 9.00.02, HP Software Site Scope, 11.01,HP Insight Software6.2 Update 1 3.DNS, DHCP and NTP systems are already installed and configured. NTP information should be part of VM templates 4.SQL Server 2005 or Microsoft® SQL Server 2008 or Microsoft® SQL Server 2012 , Oracle 11g, both 32-bit and 64-bit versions may be used for CSA database.
5.We will install  HP Cloud Service Automation, 2.00, HP Server Automation, 9.02, HP Operations Orchestra…

Data Center Migration

Note: This blog is written with the help of my friend Rajanikanth
Data Center Migrations / Data Center Consolidations
Data Center Consolidations, Migrations are complex projects which impact entire orgnization they support. They usually dont happen daily but once in a decade or two. It is imperative to plan carefully, leverage technology improvements, virtualization, optimizations.
The single most important factor for any migration project is to have high caliber, high performing, experienced technical team in place. You are migrating business applications from one data center to another and there is no scope for failure or broken application during migration. So testing startegy should be in place for enterprise business applications to be migrated.
Typical DCC and Migrations business objectives
Business Drivers
·Improve utilization of IT assets ·DC space & power peaked out - business growth impacted ·Improve service levels and responsiveness to new applications ·Reduce support complexi…

Openstack- Its importance in Cloud. The HP Helion Boost

Every enterprise expects few things from cloud computing, mainly:

· Auto scaling: The workload should increase and decrease as needed by the IT environment.

· Automatic repair: If there is any fault or crash of the application or the server, it automatically fix it

· Fault tolerant: The application or underlying technology is intelligent enough to make itself fault torrent

· Integrated lifecycle: It should have integrated lifecycle

· Unified management: Its easy to manage all different aspects of technology

· Less cost

· Speed


Its year 2014. till now only 5% to 7% enterprises are using cloud computing. Such a small number. Its a huge opportunity and a vast majority for anyone who is interested in providing cloud computing services.
Current IT environment is very complex. You just cant solve all your problems with cloud computing.
There are legacy systems, databases, data processors, different hardware and software. You name it , there are so many technology available in just o…