Site Recovery Manager (SRM)

Proof of Concept (POC) Guide

Always watch for the most current version of this document. It will be updated as often as the users of it make suggestions!

Table of Contents Table of Contents ................................................................................................................ 2   Team Details ....................................................................................................................... 3   Customers’ Business Drivers & Success Criteria ............................................................... 4   Application Environment .................................................................................................... 4   Recovery Order ............................................................................................................... 4   Site Naming ........................................................................................................................ 5   Proof of Concept Configuration Information ..................................................................... 5   Networking ..................................................................................................................... 5   Virtual Infrastructure Information .................................................................................. 5   Storage Array Information .............................................................................................. 6   Customer Success Criteria .................................................................................................. 6   Pre-Engagement Preparation .............................................................................................. 7   Storage ............................................................................................................................ 7   Application...................................................................................................................... 7   Pre-Engagement Checklist .............................................................................................. 7   POC Tasks .......................................................................................................................... 9   POC Architecture Diagram ....................................................................................... 10   Results of this PofC from the point of view of the customer! .................................. 11   Next Steps – for the customer and local SE .............................................................. 11   After Action Report .................................................................................................. 11   Appendix ........................................................................................................................... 12   PofC Outline ................................................................................................................. 12   Whiteboard Education .................................................................................................. 12   Background info............................................................................................................ 13   Comments / Suggestions ............................................................................................... 13  

Page 2 of 13

Team Details VMware Account Team Region Account Manager Systems Engineer/Consultant SSSE / SME Client Company Name Location Storage Vendor Company Name & Contact Partner Name & Contact Client Executive Sponsor Name Title Group POC Details Customer Project Lead Phone Number Email Address Start Date

Page 3 of 13

Customers’ Business Drivers & Success Criteria Business Overview: •

What are the key business drivers and compelling reasons for this Proofof-Concept (POC)?

•

What is the Required RPO/RTO for a production implementation?

•

Has the customer performed a Business Impact Analysis (BIA)?

•

Has the customer ranked applications in terms of importance and/or RPO/RTO requirements?

Note: please delete this text, including this note with the business overview information.

Application Environment List Applications to be protected during the Proof-of-Concept (POC) along with their components: Example: •

Application CRM: 6 virtual servers total, 2 for iis, 2 for weblogix, 2 for Oracle

Fill in the Following Table Detailing Application Components: Component

VM Name

VM OS

VM – No CPUs

VMAmt Mem

VM- Amt Storage (GB)

IP addr Prod NW

(GB)

IP addr DR NW

ESX Server

Important Note: This PofC is about proving SRM can do what is needed and that is through education. It is strongly recommended that you do no more than 10 VM’s due to the complexity that might entail and of course subtract from the learning and success of the PofC.

Recovery Order Provide Recovery Order of All Application Components: Example: 1. Oracle Database 2. iiS 3. weblogix

Page 4 of 13

Site Naming What is the Protected Site name _____________________________ What is the Recovery Site name _____________________________ Proof of Concept Configuration Information

Networking Fill in the Following Table Detailing Networking Components: Component

Production Site IP

DR Site IP

Subnet Gateway DNS

Virtual Infrastructure Information Fill in the Following Table Detailing VMware Infrastructure: Component

Fully Qualified Host Name

IP address

Server Model or VM

Number of CPUs

Amount of Memory

ESX Server in Production Site ESX Server in DR Site Virtual Center Server in Production Site Virtual Center Server in DR Site Oracle or SQL Database in Production Site

Page 5 of 13

Oracle or SQL Database in DR Site

Storage Array Information Fill in the Following Table Detailing Storage Array and Replication: Production Site

DR Site

N/A

4 GB max

LUNs required for replication Shadow VM LUN

Storage Array Array Firmware Replication Type Available Snapshot Type Available Array Manager Software version

Storage Management Hostname and/or IP Addr)

Note: extra space will be required on the recovery side for snapshots, flashcopys, remote copys, flexclones, etc. The amount of extra space will vary among the storage vendors.

Customer Success Criteria Proof-of-Concept (POC) Success Criteria as Defined by Client: Examples: 1. Show Application Restarts at DR Site 2. Test Application Functionality at DR Site

Page 6 of 13

Pre-Engagement Preparation

Storage To be completed by the VMware SE and Storage Vendor representatives: 1. Get commitment from the storage vendor to help with POC and attend the second day of POC. 2. Get a copy of storage vendor’s Storage documentation and current code revision.

Replication

Agent

(SRA)

3. Get a copy of the release notes for the current SRA and any future SRA that is available. Identify known issues section. 4. Determine and document the customer’s complete storage configuration to be used for the POC. This includes array, array firmware, array management software, replication and snapshot software, available storage, and any other management components. For example, if the customer is using EMC Clariion with ECC management software then the Solutions Enabler component is required for the POC if they are not using ECC, Solutions Enabler is not required. Each storage vendor is different on their requirements so document the environment and with the storage vendor go through the SRA document thoroughly to understand configuration requirements and components. 5. Make sure there is enough space in the array at the DR site to accommodate an array snapshot for testing the SRM Recovery Plan.

Application To be completed by the VMware SE and customer application and IT team representatives: 1. Determine and document application shutdown and startup order 2. Determine application authentication requirements and dependencies (i.e. AD, hard-coded IP addresses, hostnames etc.) 3. Determine application network dependencies 4. Determine application dependencies on physical components and plan for access to these components after failover 5. Plan for the application team to be available prior to SRM implementation to test application shutdown and startup in the POC environment (this baselines the application prior to SRM)

Pre-Engagement Checklist To be completed jointly with the client and the storage vendor in a pre-POC prep meeting, prior to the first day of the POC. NOTE1: The storage vendor should also attend the first day of the POC to help as the storage vendor’s Storage Replication Agent (SRA) is installed and verified. NOTE2: Check with the SRM Reference Guide to note any potential issues that may impact your PofC. Also, it is useful for background information that will help you sound more knowledgeable.

Page 7 of 13

Requirement Facilities – we will need a room with a projector and white board for the duration of the PofC. An internet connection will be required. One VMware ESX Server installed at both the Production and DR sites. Please include make\model and CPU and Memory capacity in details. Please ensure that the ESX host server hardware is certified and on our hardware compatibility list. The HCL is located at: http://www.vmware.com/resources/techresources/cat/119 The ability to install SRM on both the VC at the production site and the VC at the DR site needs to be confirmed. See the following for requirements for both VC and ESX: http://www.vmware.com/pdf/srm_compat_matrix_4_x.pdf One VMware Virtual Center Management Server 2.5 installed on either a virtual or physical Windows 2003 Server at both the Production and DR sites. The ability to access via ODBC either a SQL or Oracle database for SRM at both the Production and DR sites. Valid versions of these databases are listed here: http://www.vmware.com/pdf/srm_compat_matrix_4_x.pdf Create a database in either Oracle or SQL at both the Production and DR sites. Create an empty database, with similar naming structure as VC and VUM, and make the owner of it the same account as will be used in the ODBC connection. Obtain Valid VMware licenses to cover all components – These can either be purchased licenses or evaluation keys. SRM has a built in 60 license. TCP/IP connectivity and forward, reverse, short, long DNS resolution between VC, ESX, and SRM servers in each site. Create a list of Virtual Machine(s) to be protected by SRM along with their underlying storage. As discussed earlier in this document. Identify storage vendor and array replication and snapshot software to be used. Verify storage is supported: http://www.vmware.com/pdf/srm_storage_partners.pdf With customer, contact storage vendor and make sure the storage vendor follows their Storage Replication Agent (SRA) documentation to prepare for the POC. Read through the SRA documentation to note any information that pertains to the limits or capabilities of the SRA that will or may impact the PofC. Validate VM operating systems are supported: http://www.vmware.com/pdf/srm_compat_matrix_4_x.pdf

Yes/No

Validate VM operating systems requiring customization are supported:

http://www.vmware.com/pdf/srm_compat_matrix_4_x.pdf Customization requirements discussion and list Networking Requirements for DR failover - identified Non-replicated storage at DR site for shadow VMs. This storage needs only be 4 GB MAX.

Page 8 of 13

Details

POC Tasks It is important to understand that this is not just a PofC to sell SRM, but to further a relationship with the customer. In fact sometimes it is a start to a relationship. In the three days of this PofC you will have a lot of time to impress the customer with our products, our company, and you. Take advantage of it. Bring in lunch and do product roadmaps, or tips and tricks, or demonstrate other products. I often will give demos of other things like View or vSphere. Even a demo of vSEL is very effective. When installing software explain the significance and sometimes how it used to be before SRM. Use examples where possible from the customer world. Use the SRM Reference Guide for background knowledge and learning before you start! Task Completed Comments (Y/N) or MM\DD\YY Issues POC Kick Off Meeting Review key business drivers and priorities and document them in section above. “Why is the client looking at SRM?” This can often be part of the Education section below. This can be done as part of understanding current methods of DR. Provide cursory overview of underlying Virtual Infrastructure framework, including centralized management and high availability. Learn their naming, organization so your examples will make more sense. Education – this should take roughly half of a day, and sometimes (often) longer. It can / should be done on a whiteboard. Find hints and suggestions in Appendix. Whiteboard proposed POC architecture and document. Include in POC Architecture section below. Address any client concerns and\or questions. Often this is the end of day 1. Site Recovery Manager (SRM) Installation Install Site Recovery Manager (SRM) server at both sites. Sometimes day 1 ends here. Install SRM Plug-in where required Install storage vendor SRA at both the production and DR sites Configuration of SRM Compare Site Pairings Configure Array Managers Inventory Mappings

Page 9 of 13

Create Protection Group(s) SRM Recovery Plans Create Recovery Plan(s) Note: test small, failover small or big. This is more effective for the testing and availability of resources. Test Recovery Plan - simple Test A Recovery Plan(s). Do no IP customization. Make sure things work. This is a test of SRM / SRA communication. Troubleshoot as necessary Capture SRM Test Recovery Plan Report. Generally day 2 will end here. Test Recovery Plan - enhanced First teach customization in detail! Use tool to do customization Adjust RP to use VLAN Validate Successful VMs running at DR site with proper IP Capture SRM Run/Execute Recovery Plan Report Teach how to do Test Plan. This should take between 2 and 3 hours. Find more info on this and an outline in the SRM Reference Guide. Do Availability roadmap. Normally the end of day 3 here. Ideas for lunch would include roadmaps, and product demos. Even talking about best practices. The outline above should take roughly 3 days when it goes smooth.

POC Architecture Diagram

Page 10 of 13

Results of this PofC from the point of view of the customer! Happy and willing to buy for example. Or happy with SRM but they need something else to buy.

Next Steps – for the customer and local SE Pricing information to be provided to customer.

After Action Report How can this guide, and the SRM Reference guide but easier to use? Did you learn anything we need to bring back to the storage partner? Did you get any comments or learn anything that needs to be shared with our engineers or product management? Please record here any comments or suggestions you have to make things better. Than email this complete report to [email protected]. This is important so we can improve this document, reference guide, and SRM!

Page 11 of 13

Appendix

PofC Outline Day 1 • Tour • Whiteboard (see below) • Maybe, install SRM, but not configure Suggest lunch activity – VMware overview roadmap Day 2 • Install? • Configure • Simple Test Suggested lunch activity – View demo, or vSel demo Day 3 • Ehanced test, • More simple test • IP customization • Catch up Suggested lunch activity – CARS roadmap

Whiteboard Education Much of this can be found in the SRM Reference Guide. • • •

• • • •

•

What is SRM and what is it not? Usage scenarios – data center moves, test dev stocking, also talk about 1 to 1 Licensing – draw it out! And talk about how to manage it during an event meaning the licenses are needed for the failback but are in fact on the original protected side. SRA – only use trusted ones, what they are for, support BIA / Run books – they are key and why they are important! Design and scalability Naming, in LUN / Storage, but also resource pools / folders, for troubleshooting, but also for the purpose of understanding if something is protected or not. Or in a recovery place or not. Mention this again when doing the array manager stuff. Resource pools with low shares better than sleeping – which is an option in the recovery plan. Make sure they understand. Page 12 of 13

•

• •

Updates – how to do patching (4 weeks after a patch is received, watch forums, talk to local SE’s, make sure it is good.) Than when ready get it done quick as SRM needs exact builds on each side! Support – start with us but we will not help much with SRA but will usually provide a log snippet to use with the SRA vendor. Always submit logs. Simple test vs. enhanced testing. Meaning simple uses test bubble and enhanced uses VLAN.

Background info Make sure to use the SRM Reference Guide to help you with this process. Many things mentioned briefly in this document are in detailed in the Reference Guide. Scalability, design, test plans and much more including caveats about SRA’s. You should have installed SRM a few times, hopefully with the help of a SME or SSSE, and have attended the SRM Troubleshooting lab at vSummit. If neither of these are true contact the local SME for a ride along and you will be good the following time on your own. The local SME can also arrange for the SSSE to attend.

Comments / Suggestions Please forward any comments or suggestions to Jeff Junter, BC/DR SSSE, at [email protected] . This is document version VMware_SRM_POCGuide_f.docx . Thanks!

Page 13 of 13