vmware site recovery manager integration with...

www.eaton.com/virtualization

VMware Site Recovery Manager integration with IPM Page | 1

VMware Site Recovery Manager Integration with IPM

http://www.eaton.com/virtualization



Contents

1 Introduction..................................................................................................................................... 4

1.1 VMware Site Recovery Manager........................................................................................... 4

1.2 Eaton’s Intelligent Power Manager ....................................................................................... 6

1.3 Benefits of VMware Site Recovery Manager integration with IPM ........................................ 7

2 Recovery plan in SRM ...................................................................................................................... 8

3 Integration of VMware Site Recovery Manager with IPM ............................................................... 10

3.1 Pre-requisites ..................................................................................................................... 10

3.2 Integration ......................................................................................................................... 10

4 Appendix A – SRM java script ......................................................................................................... 16




Table of Figures

No. Name of Figure

1.1 VMware Site Recovery Manager architecture

1.2 IPM web console.

2.1 A snapshot of sample recovery plan in SRM

3.1 Architecture of SRM and IPM integration

3.2 Setting a priority for VM in recovery plan

3.3 Configuring VM Recovery Properties in a recovery plan




1 Introduction

The purpose of this document is to guide IT administrator/user to make use of VMware site recovery manager with Eaton’s Intelligent Power Manager.

Acronyms

SRM VMware Site Recovery Manager

IPM Eaton’s Intelligent Power Manager

VM Virtual Machine

VR vSphere Replication

VRMS vSphere Replication Management Server

VRS vSphere Replication Server

VPS Virtual Power Source

1.1 VMware Site Recovery Manager

SRM provides disaster recovery protection for VMware virtualized environment .The protection can range from virtual machines residing on a single datastore to all the virtual machines in a datacenter. This protection is for the operating systems as well as the applications running on the VM.

SRM provides two types of recoveries.

Planned Migration Planned migration is the orderly shutting down of virtual machines at the protected site and starting up equivalent machines at recovery site. For planned migration to succeed, both sites must be up and fully functioning. Disaster Recovery Disaster recovery is similar to planned migration except it does not require that both sites be up. During a disaster recovery operation, failure of operations on the protected site is ignored.




SRM requires two sites, protected and recovery, and SRM server should be installed at each site. Also each site must be owned by its own vCenter Server. SRM performs a fully automated recovery of the protected site. See figure 1.1 for illustration.

Fig 1.1 VMware Site Recovery Manager Architecture.

SRM supports NFS, iSCSI storage and it uses two types of replication mechanism:

1. Array based replication (Storage-based)

• It needs identical high-end storage arrays across the sites. Here the storage subsystem manages VM replication.

• SRM automatically discovers datastores for array-based replication between the protected and recovery sites. SRM supports upto 1,000 VMs for Array based replication.




2. vSphere Replication Storage(host-based)

• It eliminates the need of identical high end storage arrays. Here ESXi manages VM replication.

• SRM supports upto 500 VMs for vSphere replication.

SRM coordinates the recovery process with the underlying replication mechanisms where the virtual machines at the protected site are shut down gracefully and the replicated virtual machines can be powered up at the recovery site. Recovery of protected virtual machines to the recovery site is guided by a recovery plan that specifies the order in which virtual machines are started up. In order to perform the recovery process, the virtual machine should be protected. For more information about protection groups, refer SRM admin guide http://www.VMware.com/pdf/srm_admin_5_0.pdf .

1.2 Eaton’s Intelligent Power Manager • IPM discovers and supervises Eaton UPSs, ePDUs and supervises non-Eaton branded power

devices connected to the network (either by means of a card or a proxy). • IPM will also provide local computer graceful shutdown to the system hosting IPM.

A snapshot of IPM web interface shown below.

Fig 1.2 IPM web console.


http://www.vmware.com/pdf/srm_admin_5_0.pdf



1.3 Benefits of VMware Site Recovery Manager integration with IPM

1. Starts recovery process on several different events: IPM will initiate the execution of recovery plan upon several different events.

2. Less down time for end users: Virtual machines will be down only for the amount of time required to transfer of latest snapshot and will restart once transfer is complete. The unprotected VMs will continue to run on the primary site.

3. Customization for end users: User can customize the script included in the package as per his / her needs. E.g. user may want to configure SRM with IPM for low battery and protection loss features, then user is able to make such customizations. It will allow user to make the best alignment of his/her needs with this integration.

4. Unattended execution of recovery plan before server crash: SRM with IPM provides recovery even before the entire site crashes. With the use of SRM feature, user will have the backup ready even before the crash, which keeps user secured all the time.




2 Recovery plan in SRM

After SRM is configured at the protected and recovery sites, user can create and test a recovery plan without affecting services at either site. User can also perform planned migrations or disaster recoveries by running a recovery plan, and, if necessary, reverse the role of two sites by performing a reprotect. See below screenshot which shows a recovery plan ‘TestPlan’ having recovery steps to execute after it is triggered.

Fig 2.1 A snapshot of sample recovery plan in SRM.




• When a recovery plan is executed, all virtual machines in the recovery plan are replicated to the recovery site. The corresponding protected site virtual machines are shut down.

• If this is a planned migration, an attempt is made to replicate all virtual machines and gracefully shut down the protected machines. If errors occur during a planned migration, the plan pauses so that users can resolve errors.

• If this is a disaster recovery, an attempt is made to shut down any virtual machines. If they cannot be shutdown, the copies at the recovery site are still brought up. If errors occur during a disaster recovery, the recovery plan still continues to execute.

• For more information about how to create, edit a recovery plan, refer admin guide of SRM http://www.VMware.com/pdf/srm_admin_5_0.pdf .





3 Integration of VMware Site Recovery Manager with IPM

In real time scenarios, there may be n number of UPSs powering the servers and its VMs and there may be a huge amount data flowing or getting used by the users. But when there is any anomaly with the UPS, it is necessary to protect this valuable data from data loss. For this intention, the SRM integration with IPM has been made. IPM is the power management software which notifies the user in case of any UPS and power anomalies and SRM is used to trigger the disaster recovery upon such anomalies.

3.1 Pre-requisites • SRM is configured at protected as well as recovery site. • It is recommended that Latest version of IPM is installed at the recovery site. To know more

about IPM,refer its user manual on http://pqsoftware.eaton.com/explore/eng/network/net_sol.htm • Windows Powershell version 2.0 should be installed on the host on which IPM is installed. • VMware vSphere PowerCLI installed on the machine. • User should have a basic knowledge of SRM and its configuration and IPM. • If user wants to use VPS features of IPM ,to know more about VPS, refer chapter 8 (redundancy)

of IPM user manual on http://pqsoftware.eaton.com/explore/eng/network/net_sol.htm • User should have atleast one recovery plan created in order to perform the disaster recovery. • In ideal situation, both the sites must be powered by 2 different UPSs.

3.2 Integration • Download and extract EatonSRMPackage from

http://pqsoftware.eaton.com/explore/eng/network/net_sol.htm • Copy the PSVMSrm module and place it in a root folder of IPM. e.g. C:\Program

Files\Eaton\IntelligentPowerManager. For more information about this module, refer http://archive.msdn.microsoft.com/PSVMSrm

• Copy remaining .ps1 files and place in the root folder of IPM. e.g. C:\Program Files\Eaton\IntelligentPowerManager

• Copy the SRM.js script and place it in the “C:\Program Files\Eaton\IntelligentPowerManager\configs\scripts”.

• Customize the java script as per the requirement. Restart the IPM service. • Now the SRM is integrated with IPM. The figure below illustrates the architecture of SRM and

IPM integration.


http://pqsoftware.eaton.com/explore/eng/network/net_sol.htm



http://archive.msdn.microsoft.com/PSVMSrm



Fig 3.1 Architecture of SRM and IPM integration.

Different scenarios considered for UPSs are as follows

UPS Power Failure :

• The protected site is getting powered by a UPS. This UPS is continuously monitored by IPM. If the protected site experiences a power failure, then IPM triggers the execution of user-created recovery plan. The recovery plan can be customized as per the user needs. e.g. User can customize a recovery plan as follows:

1. User can set the priority for VMs as per the criticality. See the figure 3.2 for illustration. e.g In case of any UPS anomalies, user can set the priority 1 for those VMs which are critical. So the VMs with high priority will be handled first.




Fig 3.2 Setting a priority for VM in recovery plan.

2. User can perform different actions for VMs as per their priority. E.g. User can set graceful shutdown feature for high priority VMs and power off for low priority VMs. See below snapshot for illustration.




Fig 3.3 Configuring VM Recovery Properties in a recovery plan.

• After a recovery plan is executed, all virtual machines in the recovery plan are replicated to the recovery site and the corresponding protected site virtual machines are shut down.

• If both sites are up and functioning then recovery plans gets executed in ‘Planned Migration’ mode. In case of planned migration mode, if any error occurs, then the recovery plan pauses so that user can resolve errors.

• In case of real time scenarios e.g. Protected site is down due to UPS down, then recovery plan gets executed in ‘Disaster Recovery’ mode. In this case, failure of operations on the protected site is ignored and it attempts to shut down all VMs at the protected site. If they cannot be shutdown, the replicas of VMs at the recovery site are still brought up.

Low Battery Alarm:

If the UPS powering protected site experiences a low battery warning alarm – i.e. if battery capacity is lower than the battery capacity limit defined in NMC, IPM initiates the execution of recovery plan to perform the disaster recovery.




Internal failure, fan failure Alarm:

If there is any internal failure or fan failure in UPS, then IPM initiates the execution of recovery plan to perform the disaster recovery.

Over Temperature Alarm:

If internal temperature of UPS is high, then IPM initiates the execution of recovery plan to perform the disaster recovery.

Loss of Redundancy and Protection Loss for VPS:

If one of the UPSs experience a communication loss, power fail, or low battery then it is a loss of redundant UPS. In this case IPM initiates the execution of recovery plan to perform the disaster recovery. When all the UPS nodes in VPS experience power fail, any internal failure, or communication loss, then it is protection loss. In this case IPM initiates the execution of recovery plan to perform the disaster recovery.

For more information about how to customize a recovery plan, refer admin guide of SRM http://www.VMware.com/pdf/srm_admin_5_0.pdf .





References

• Eaton and virtualization Please visit http://www.eaton.com/virtualization

• Intelligent Power Manager (Eaton Power Supervisor) Please visit http://pqsoftware.eaton.com for more information about download and installation of IPM.

• VMware Sire Recovery Manager Visit http://www.VMware.com/products/site-recovery-manager for more information about SRM and its benefits.

• SRM configuration and vSphere replication storage. Visit http://www.VMware.com/pdf/srm_admin_5_0.pdf for more information about SRM configurations.

Copyrights

Eaton and Eaton Corporation are trade names, trademarks, and/or service marks of Eaton Corporation or its subsidiaries and affiliates. VMware is a registered trademark of VMware, Inc. in the United States and/or other countries. All other company or product names are used for informational purposes only and may be trademarks are property of their respective owners.



http://pqsoftware.eaton.com/

http://www.vmware.com/products/site-recovery-manager




4 Appendix A – SRM java script




Note: During configuration of above JavaScript if username contains \ replace it with \\.

The parameters used in the script are as follows:

• RecoveryServer – Hostname of the SRM server at recovery site. • Username – Username of SRN server • Password – Password of SRM server • statusUPS1 – IP address of node in IPM. • RecoveryPlanName – Name of Recovery Plan • Waittime – time in minutes to wait to execute recovery plan. • statusVPS1 – Name of VPS node in IPM.


vmware site recovery manager integration with...

Documents