Sanovi DRM for VMware SRM. Technical Brief

Transcription

1 Sanovi DRM for VMware SRM Technical Brief

2 Contents Executive Summary Benefits of Sanovi DRM for SRM DR Lifecycle Non-Intrusive Test Switchover and Switch back Failover Report and Analytics Pre-requisite Installation & Configuration Summary Disclaimers The information contained in this document is the proprietary and exclusive property of Sanovi Technologies except as otherwise indicated. No part of this document, in whole or in part, may be reproduced, stored or transmitted, or used without the prior written permission of Sanovi Technologies. Privacy Information This document may contain information of a sensitive nature. This information should be circulated to the intended audience. 2 of

3 Executive Summary Sanovi Disaster Recovery Management (DRM) software provides comprehensive and reliable disaster recovery management for enterprises and service providers. With its support for VMware Site Recovery Manager (SRM), Sanovi DRM enables users to manage the complete lifecycle of DR from the single console. It provides visibility to DR SLAs, ensures SRM on the DR site recovers predictably and with little or no manual intervention and provides comprehensive DR reports. Sanovi DRM helps users meet their recovery metrics reliably and predictably. Introduction Businesses are faced with an ever-increasing need to recover critical applications within set recovery goals. This can be a complex issue if not handled carefully, because replication of data to the DR/secondary site in itself does not ensure that the application will recover and come up with all the required inter-dependencies. This document provides the details of how Sanovi DRM provides a comprehensive best practice approach for disaster recovery management by integrating with VMware SRM. Benefits of Sanovi DRM for SRM There are several features and benefits that Sanovi DRM offers in SRM environments. Some of them are: DR Monitor Ø Real time monitoring of replication data lag for all replicators Ø Automated alerts on DR SLA deviation Ø Application level monitoring Ø Storage replication monitoring is possible using single pane of DRM console. Storage replication status is always required to be monitored through storage or replicator console Ø SLA can be tracked using RTO & RPO monitoring using DRM console. Recovery & DR Drills Ø Pre-flight checks to ensure DR Drill and Recovery success Ø Application startup/checks using built-in Recovery Action Library(RAL) Ø Trackable DR Drill calendar for each application Ø Fully automated switchover/switchback drill with incremental reverse sync Ø Trigger SRM Recovery Plans Ø In mix & match environment where vsphere replication has got limitation like automated fallback of VM's can be achieved through customized scripts in DRM Ø Since discovery of the VM's happens at vcenter level in DRM, vcloud director environment can also be supported which is not possible using SRM Ø DRM provides capability that supports not just bringing up the VM at DR site but makes sure application integrity is also maintained. Ø Support for other hypervisors and physical infrastructure for DR DR Reports Ø End-to-end reporting including SLA /deviations for Audit/Compliance purpose Ø RTO/RPO reports can be fetched at individual VM level cause DRM concentrates more on application defined continuity where in SRM RTO is mainly depends on Datacenter of

4 DR Lifecycle Every DR solution has a lifecycle that it operates around. The phases of the DR Lifecycle are: r DR Monitor: In this phase, the health of the replication and DR SLA metrics are continuously monitored and alerts are raised on failures and deviation of SLAs. r Non-Intrusive Test: This allows testing the DR environment without causing any production downtime. Servers and applications are brought up in a sandbox environment on the DR site and tests are run on the sandbox environment without impacting the production. r Switchover/Switchback: This allows the testing of the DR environment in a live scenario where the application is run live and from the DR site. As a part of the Switchover, DR site takes over the role of production and primary site takes of the role of DR. The underlying replication is reversed so that the data from the DR site it synced back to the primary site. This enables the users to test their DR environment using live data and production loads. Once the testing is complete, the roles of the sites are reversed back and the application is run live from the primary site and the DR site goes back to its original role of DR. The underlying replication is reversed back so the synchronization of data resumes on the forward direction. r Failover: When the primary site or the application is down on the primary, the application is recovered on the DR site and takes over the role of running the application live. All the users and business transactions will be handled from the application running on the DR site. Non-Intrusive test Non-intrusive test workflows from DRM will invoke the SRM recovery plan to bring the application on a sandbox environment for testing the DR without impacting the production. The typical DR test operation steps for non-intrusive test are given below. The workflow can be customized by adding/modifying/removing steps that are specific to the environment. 1 Connect to vcenter from power CLI 2 Connect to SRM and Load Extended Data Set Recovery Plan to execute Verify SRM Plan state is ready, if not ready, throw error, if State is ready Set Recovery Plan execution Mode Start Executing test Plan Verify SRM Plan Execution Status 8 Guest Customization for DB layer DB configuration changes required, Bringing up the DB using RALs 9 Guest Customization for App Layer APP configuration changes to brings the application using RALs 10 Execute the Application test procedures to validate the environment of

5 Switchover and Switchback Switchover and Switchback workflows from DRM will invoke the SRM roleswtich plan along with pre and post actions to complete the application level switchover or switchback. The typical DR operation steps for Switchover/Switchback including the SRM actions are given below and the same can be customized by adding/modifying/removing steps that are specific to the environment. 1 Gracefully shutdown the App 2 Gracefully shutdown the DB Connect to vcenter from power CLI Connect to SRM and Load Extended Data Set Recovery Plan to execute Verify SRM Plan state is ready, if not ready, throw error, if State is ready Set Recovery Plan execution Mode 8 Start Executing role switch Plan 9 Verify SRM Plan Execution Status 10 Guest Customization for DB layer DB configuration changes required, Bringing up the DB using RALs 11 Guest Customization for App Layer APP configuration changes to brings the application using RALs 12 Switch the network to get the client connect to the new site Failover Failover workflow from DRM will invoke the SRM recovery plan to bring the application live on the DR environment. The typical DR operation steps for Failover including the SRM actions are given below and the same can be customized by adding/modifying/removing steps that are specific to the environment. 1 Connect to vcenter from power CLI 2 Connect to SRM and Load Extended Data Set Recovery Plan to execute Verify SRM Plan state is ready, if not ready, send an alert. if State is ready Set Recovery Plan execution Mode Start Executing failover Plan Verify SRM Plan Execution Status. If not successful, send an alert. 8 Guest Customization for DB layer DB configuration changes required, Bringing up the DB using RALs 9 Guest Customization for App Layer APP configuration changes to brings the application using RALs 10 Switch the network to get the client connect to the new site of

6 Reports & Analytics Sanovi DRM provides built in reports to do the analysis and improve the recovery objectives of the applications. Some of the reports available are RTO Report, Drill Report and Test Report. In addition, the advanced reports module of Sanovi DRM allows the customization as well as creating new reports based on the users compliance needs. Pre-requisites q VMware vsphere PowerCLI. R2 and above on a Windows server q SRM API should be installed on SRM Server. q SRM plugin needs to be installed on the vsphere client (powercli and vsphere client should be on the same machine) Credentials to connect to vcenter and SRM to manage plans Installation & Configuration The following agents must be installed on Primary and DR Power CLI machines q Windows OS Agent Note: Refer Installation Guide for more details on Agent Installation & configuration. of

7 Summary Sanovi DRM for SRM provides a DR solution that includes central monitoring, automation and DR Reports. The Sanovi solution provides business benefits by increasing operational efficiency and application uptime. DRM s flexible and user friendly approach allows to extend the solution by integrating the application specific intelligence during automation or testing based on the needs. About Sanovi Gartner Cool Vendor Sanovi Technologies, provides Cloud Migration, Business Continuity and IT recovery solutions using its innovative Application Defined Continuity (ADC) technology for workloads across physical, virtual and cloud infrastructures. Sanovi has over 0 customers, including fortune 00 companies, service providers and multi-billion dollar enterprises across vertical industries. Gartner's 201 Hype Cycle report on BCP/DR calls out Sanovi's software as the recovery management solution for heterogeneous platforms. Sanovi is a Red Herring Global 100 award 201 winner. Sanovi's offerings include enterprise DRM and cloud continuity software products. For more on Sanovi solutions, please visit BUW00-USEN-00 of