Tag Archives: BC

vCenter Site Recovery Manager (SRM) 5.X – Part 2

Installation Repair

Altering authentication information to SRM database or vCenter server system will immediately prevent SRM to function correctly.

For example, you change the Administrator password for the vCenter server, SRM will no longer able to communicate with vCenter server. Whenever Authentication information changes after SRM installed, use Installation Repair wizard to update SRM with new credentials.

You can use Installation Repair Wizard to change the User and the Password for vCenter Server Administrator, the certification method for Authentication and the SRM database information.

One important thing to remember about using the Repair feature is that it over-write the existing installation of SRM. Therefore if you have applied patches to SRM and used Repair Wizard to change the User and the Password for vCenter Server Administrator, the certification method for Authentication and the SRM database information, You have to reapply all the patches.

Let’s start The Repair Process :-

1. Double click .EXE file to start Repair Wizard..

si12. Installer will detect that SRM is installed on the server so either we can Repair or Remove from this system. Choose Repair and click Next..

SRMPT2-23. If you were using Storage-Array Replication but now want to use vSphere         Replication Select Install vSphere Replication and click Next..

si84. Change the User or the Password information for vCenter Server and click Next..

SRMPT2-35. Change Certificate source if needed and click Next..

SRMPT2-46. Change Database Configuration Information if needed and Click Next..

SRMPT2-57. Follow the windows and click Finish to complete the Installation Repair.


Site Pairing Process

Once SRM is installed on both the sites, the next step is to pair the sites together. The pairing process establishes a connection between the vCenter Servers at the protected and recovery sites, which makes the SRM instances at both the sites aware of its counterpart at the other site (protected site/recovery site). Without the sites being paired, we can’t proceed further with the configuration of the DR setup.

This is how the sites are paired:

1) Connect to either vCenter Server using vSphere Client –> Home –> Solutions and Applications –> And Click Site Recovery. (Site Pairing can be done either from Protected Site or from Recovery Site vCenter Server).

SitePair-12) Click on Sites in the left pane.

3) Right-click on the local site listed, and click on Configure Connection to bring up the configure connection wizard.

SitePair-24)  In the Configure Connection wizard, supply the FQDN of the remote vCenter Server and click Next to continue. Accept any subsequent certificate warnings.

SitePair-35) Enter administrator credentials, and click Next. Accept any subsequent certificate warnings

SitePair-46) This will begin the pairing process, which will establish a connection with the remote vCenter Server and SRM, and also establish reciprocity. Click Finish to complete and exit the wizard.


7) Once you exit the wizard, you will be prompted again for the administrator credentials of the remote vCenter Server. Enter the credentials and click on OK. Ignore any subsequent certificate warnings.


8) You should see both the sites listed under the Sites pane now:

SitePair-9Note:- Pairing is done only from one of the sites. This is because the pairing process establishes reciprocity by configuring the connection in the reverse direction as well. However, when you open the site recovery solution at the remote vCenter Server, you will be prompted to enter the administrator credentials of the other site.


Installing Storage Replication Adapters (SRA) or vSphere Replication (VR) (Depends on your setup what are you going to use in your environment)

Once you have the SRM instances installed and paired, the next step is to install the Storage Replication Adapters. SRAs are coded and provided by the storage vendors. VMware certifies the SRAs and posts them as compatible with the SRM. Downloading SRA The certified versions of SRA can be downloaded directly from VMware’s website. Keep in mind that most vendors publish the updated versions of SRA at their website before it is certified by VMware. Since SRA is a vendor-supported component, you can choose to install the latest version available from the vendor.

This is how you can download an SRA:

1. Go to VMware’s website at www.vmware.com.

2.Navigate to the vCenter Site Recovery Manager option in Downloads under the Product Downloads category. (https://my.vmware.com/web/vmware/info/slug/infrastructure_operations_management/vmware_vcenter_site_recovery_manager/5_5)

3.Once you are at the download page for vCenter SRM, click on the Go to Downloads hyperlink listed against SRA.


4. At the Download Storage Replication Adapters for VMware vCenter Site Recovery Manager page, you will see a list of all the certified SRAs. Click on the Download Now button corresponding to the needed SRA.

SRA2 ==========================================================

Installing SRA

The SRA component has to be installed on both the SRM servers at both sites. In most cases, the SRA installation is pretty simple and straightforward, but this can be different from vendor to vendor. You need to refer to the vendor documentation for the installation procedure.

1) Once Download specific SRA from VMware Web site run .EXE file to start installation. (For Installation Demo – I am using Dell Compellent_StorageCenterSRA)

SRA32) Click on Next at the Welcome screen..


SRA54) Installation Setup will start the software installation..

SRA65) Click Finish to complete installation.

SRA76) You Need to install SRA on SRM server If you are not installing on SRM server it will give configuration error after finishing the installation.

SRA8Once the installation is complete, follow this procedure to discover the installed SRA component:

1. Connect to the protected/recovery site of vCenter Server using  vSphere Client.

2. Navigate Home –> Solutions and Applications –> And Site Recovery.

3. Click on Array Managers in the left pane and navigate to the SRAs tab. click on Rescan SRAs to discover the installed SRA.

SRA94. Repeat the procedure at the recovery site as well to discover the SRA.


Adding an Array Manager

Once SRA installed and discovered at both the sites, we need to add an array manager at both the sites. An array manager is required to discover the replicated LUNs and perform other storage operations initiated by SRM.

This is how you add an array manager:

1. Connect to the protected/recovery site of vCenter Server using  vSphere Client.

2. Navigate Home –> Solutions and Applications –> And Site Recovery.

3) Click on Array Managers in the left pane, select the site, and click on Add Array Manager to bring up the Add Array Manager wizard, as shown in the following screenshot:

SRA104) Follow the windows and supply a Display Name for the array manager and an SRA Type. The SRA type value field will be prepopulated with the SRA that is already installed. Click on Next to continue.

5) Follow the windows and provide vendor specific Storage Array details and Click Next.

6) Repeat the same procedure on the recovery site as well.

7) Once done, the Array Managers for both the sites should be listed, as shown in the below screenshot


Enabling an Array Pair

An array pair shows the replication relationship between two arrays. Once Array Manager has been added to both Protected and Recovery Sites we need to enable an array pair. For the array manager to detect an array pair, there should be a replication schedule already created between the arrays. Refer to the vendor documentation to understand what a replication schedule means for the vendor’s array and the procedure to create it.

This is how you enable an array pair:

1. Make sure that there is a replication schedule enabled between the two arrays.

2. Navigate to the vCenter Server’s inventory home page and click on Site Recovery.

3. Click on Array Managers in the left pane.

4. Select an added Array Manager (local or remote), and click on Refresh to discover an array pair.


5. If the Refresh action discovers an array pair, the array pair will be listed.  The Refresh action has to be done at both of the sites.

6.  Array pairs discovered are not enabled by default. To enable an array pair, select an array pair and click on Enable. This operation has to done at only one of the sites.

EAP27. When an array pair is enabled, it tries to discover the devices (LUNs) for which a replication schedule is enabled at the array. Keep in mind that not all devices with a replication schedule are displayed as a device for the array pair; only the ones that are presented to a host at the protected site are displayed. To view the detected and filtered replication-enabled devices with the array manager selected, navigate to the Devices tab and click on Refresh, as shown in the following screenshot:



Continue to vCenter Site Recovery Manager (SRM) 5.X – Part 3

Click here to go to vCenter Site Recovery Manager (SRM) 5.X – Part 1

 Click here to go to vCenter Site Recovery Manager (SRM) 5.X – Part 2

 Click here to go to vCenter Site Recovery Manager (SRM) 5.X – Part 3

  Click here to go to vCenter Site Recovery Manager (SRM) 5.X – Part 4

  Click here to go to vCenter Site Recovery Manager (SRM) 5.X – Part 5

  Click here to go to vCenter Site Recovery Manager (SRM) 5.X – Part 6

  Click here to go to vCenter Site Recovery Manager (SRM) 5.X – Part 7

Note :- I have used pictures in this post from SRM book written by Abhilash GB and would like to Thank you him for this 🙂

vCenter Site Recovery Manager (SRM) 5.X – Part 1


With today’s IT infrastructures, be it virtual or physical, disaster recovery has importance. Any business should be able to continue operating with reduced downtime for its sustainability amongst the competition. Two of the major factors used to service are High Availability and Recoverability.

Recoverability is the guarantee that the service offered and its data are protected against failures, and High Availability is the guarantee that the service offered would remain operational and the failures are handled in a way that the user of the service would not even know that there was a failure. There are many ways in which businesses plan and implement disaster recovery.

When we talk about High Availability and Recoverability these two factors are important to discuss – Recovery Point Objective (RPO) and Recovery Time Objective (RTO).

What are RPO and RTO?

RPO defines the amount of data an organization can afford to lose when measured against time. RTO defines the amount of downtime the organization can afford for its services before it becomes operational again.

Both RPO and RTO are defined by time. For example, an organization can have an RPO set to 4 hours and RTO set to 1 hour. This means, it can afford to lose up to 4 hours of data, but it can only afford a service downtime up to 1 hour.

RTO only defines the amount of time a service can remain unavailable but doesn’t account for the data loss. But RPO defines how much data loss can be afforded.

srm2For example RPO is 4 hours, RTO is 2 hours and WRT is 30 minutes and disaster occurs at 10 am so we need to restore data by point of 6 am and recover the site by 12 pm. And then WRT starts for checking the servers integrity site must be fully functional by 12:30 pm. MTD in this case in 2:30 hours.

WRT (Work Recovery Time) – Determines the maximum tolerable amount of time that is needed to verify the system and/or data integrity. This could be, for example, checking the databases and logs, making sure applications or services are running and are available.

MTD (Maximum Tolerable Downtime) = RTO + WRT.

There are still so many companies following manual /Traditional way for BC/DR. To orchestrate this VMware has product called Site Recovery Manager.

Site Recovery Manager (SRM)

Site Recovery Manager (SRM) is an orchestration software that is used to automate disaster recovery testing and Failover. It can be configured to leverage either vSphere Replication or a supported array-based replication. SRM is a not a product that performs an automatic Failover, which means that there is no intelligence built into SRM that would detect a disaster/outage and Failover the VMs. The disaster recovery process should be manually initiated. Hence, it is not a high availability solution; it is purely a tool that orchestrates a Recovery Plan.

SRM requires both the protected and recovery sites to be managed by separate instances of the vCenter Server. It also requires an SRM instance at both the sites. SRM’s functionalities are currently only available via the vSphere Client and not the vSphere Web Client. Hence, an SRM plugin needs to be installed on the same machine where the vSphere Client is installed.

Refer to the following figure:

srm3Installing SRM on the protected and recovery sites:

vCenter SRM has to be installed at both the protected and recovery sites for the disaster recovery setup to work. The installation process is identical regardless of the site it is being installed on; the only difference is that at each site, you will be registering the SRM installation to the vCenter Server managing that site. SRM can either be installed on the same machine that has vCenter Server installed or on a different machine. The decision to choose either one of the installation models depends on how you want to size or separate the service-providing machines in your infrastructure. The most common deployment model is to have both vCenter and SRM on the same machine. The rationale behind this is that SRM will not work in a standalone mode; this means that if your vCenter Server goes down, there is no way you could access SRM. Like vCenter Server, SRM can be installed on a physical or virtual machine. Another factor that you must take into account is the installation of SRA. SRAs have to be installed on the same machine where you already have SRM installed. Some SRAs need a reboot after installation. So, it is important to read through the storage vendor’s documentation prior to proceeding to make a deployment choice for SRM. If the vCenter downtime is not feasible, then you will have to consider installing SRM on a separate machine.

Note:- SRA only required when you are using Array-based Replication to replicate from Protected Site to Recovery Site.


SRM Installation

1. Download SRM installer from VMware site and double click .EXE file to start installation process

si12. Click Run to start installation

si23. It will start SRM Installation process and Extract installation files.

si34. Click the Next button in the Welcome page.

si45. Click Next in the VMware Patents page.

si56. Select I agree in the License agreement and click Next..

si67. Change the Destination folder if required or click Next to install at default location ..

si78. If you want to use VR for VMs replication choose Install vSphere Replication, If want to use Array-based Replication choose Do Not install vSphere Replication and Click Next.

si89. Enter details of the vCenter Server to which this SRM will be registered to and Click Next.

si910. Make a selection of your choice and click on Next to continue. Here, I have chosen to let the installer generate a new certificate.  Use the second option if you already have a certificate file from your certificate authority. VMware recommends using CA-signed certificates for all its products.

si1011. Enter Organization name and Organization Unit and Click Next…

si1112. Enter Name of the Local Site and details and Click Next..

si1213. Choose Database and enter ODBC DSN details and click Next..

si1314. Click Install at Ready to install wizard to start the installation…

si1415. It will take few minutes to complete the installation

si1516. Click Finish to complete the Installation process.


When all these components are put together, a  paired site protected by SRM will look as below:-


Continue to Part – 2 for Installation repair , Site Pairing, and Installation of SRA.

Click here to go to vCenter Site Recovery Manager (SRM) 5.X – Part 1

 Click here to go to vCenter Site Recovery Manager (SRM) 5.X – Part 2

 Click here to go to vCenter Site Recovery Manager (SRM) 5.X – Part 3

 Click here to go to vCenter Site Recovery Manager (SRM) 5.X – Part 4

Note :- I have used few pictures in this post from SRM book written by Abhilash GB and would like to Thank him for this 🙂

Installing Storage Replication Adapters (SRA)