Pairing VMware vCenter Site Recovery Manager with virtual SAN
- 1. Luke Huckaba, vExpert Virtualization Architect @ThepHuck Pairing VMware® vCenter™ Site Recovery Manager™ with Virtual SAN
- 2. • This presentation outlines general information regarding our services and is for informational purposes only; all statements and information are provided “AS IS” and are presented WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. OUR PRODUCT/SERVICES OFFERINGS ARE SUBJECT TO CHANGE WITHOUT NOTICE. • Rackspace is either a registered service marks or service marks of Rackspace US, Inc. in the United States and other countries. • Third-party trademarks and tradenames appearing in this document are the property of their respective owners. Such third-party trademarks have been printed in caps or initial caps and are used for referential purposes only. We do not intend our use or display of other companies’ tradenames, trademarks, or service marks to imply a relationship with, or endorsement or sponsorship of us by, these other companies. Legal 2 Pairing vCenter Site Recovery Manager with Virtual SAN WWW.RACKSPACE.COM
- 3. • Setup – VSAN – vCenter & SRM – Installation Speed Bumps • vSphere Replication – Upgrading – Limitations – Storage Policies • SRM Configuration – Protection Groups – Recovery Plans • Live Demo! – Let’s hope it doesn’t crash! Agenda 3 Pairing vCenter Site Recovery Manager with Virtual SAN WWW.RACKSPACE.COM
- 4. Pairing vCenter Site Recovery Manager with Virtual SAN Setup 4www.rackspace.com
- 5. • VSAN Setup – Check VSAN HCL for RAID controller: http://www.vmware.com/resources/compatibility/search.php?deviceCategory=vsan – 3-node minimum – 4-node Best Practice minimum – Disk Group configuration • Minimum 1 flash device (SSD, PCIe, etc) and 1 magnetic disk per group for hybrid • Minimum 1 flash write buffer device and 1 flash storage disk for all-flash (vSphere 6.0 only) • 2 disk groups per host is recommended, 5 is maximum • 2 10Gbps network adapters dedicated to VSAN traffic • Requires IGMP snooping multicast, separate multicast addresses per VSAN cluster Setup Pairing vCenter Site Recovery Manager with Virtual SAN
- 6. • VSAN Setup – Sizing • Raw capacity: Hosts x Capacity disks per host used for vSAN (or disk size X total N of capacity disks) – 1 host = 3x 1000GB magnetic disks for vSAN; 4 hosts X 3 X 1000GB = 12,000GB raw capacity • Failures To Tolerate: N+1 copies of data and 2N+1 hosts are needed – FTT1 data = two copies; FTT2 = three; FTT3 = four – FTT1 hosts = three; FTT2 = five; FTT3 = seven – Default is FTT1 • Usable Capacity is directly dependent on FTT • vSwap file is created twice regardless of FTT – vSwap file: 2 X vRAM • Example: VM1 with 8GB of RAM 64GB VMDK and 128GB VMDK – FTT1 = (2 X 8) + ((64 + 128)X2) = 16 + 192 X 2 = 16 + 384 = 400GB – FTT2 = (2 X 8) + ((64 + 128)X3) = 16 + 192 X 3 = 16 + 576 = 592GB – FTT3 = (2 X 8) + ((64 + 128)X4) = 16 + 192 X 4 = 16 + 768 = 784GB • Sizing Chart: https://vsantco.vmware.com Setup Pairing vCenter Site Recovery Manager with Virtual SAN
- 7. • vCenter & SRM – Windows or Appliance? • SRM & VUM require Windows OS – What’s new in SRM 5.8 • Web Client plug-in • Auto-configure resource mappings for recovery back to protected site – vSphere Replication should be installed prior to installing SRM • SRM 5.8 installer will not prompt you to install vSphere Replication Setup Pairing vCenter Site Recovery Manager with Virtual SAN
- 8. • Installation Speed Bumps – VUM is Windows application • requires 32-bit DSN if using external database – SRM is Windows application • requires 64-bit DSN if using external database – SRM database password considerations • No longer breaks when ending with an exclamation point! • Still cannot have quotes in password, but the installer warns if it detects a “ – SRM installation cannot handle space in path • Default: C:Program FilesVMwareSite Recovery Manager • Changed to: D:Program FilesVMwareSite Recovery Manager • Installer fails saying Cannot find “D:Program” Setup Pairing vCenter Site Recovery Manager with Virtual SAN
- 9. Pairing vCenter Site Recovery Manager with Virtual SAN vSphere Replication 9www.rackspace.com
- 10. vSphere Replication Pairing vCenter Site Recovery Manager with Virtual SAN
- 11. • Upgrading – If on 5.1, must upgrade to 5.5 or 5.6 before upgrading to 5.8 – Can upgrade from 5.5 directly to 5.8 – Power off appliance in vCenter, then power on (not reboot via VAMI) • An HA event clears the OVF environment • Power On in vCenter builds /opt/vmware/etc/vami/ovfEnv.xml vSphere Replication Pairing vCenter Site Recovery Manager with Virtual SAN
- 12. • Limitations – 1 vSphere Replication Appliance (VRA) per vCenter • Hosts Virtual Appliance Management Interface (VAMI) • vSphere Replication Management Server • Serves as initial vSphere Replication Server (VRS) – 9 additional VRSs to spread out the load – 500 VMs per VRA – 100 VMs per VRS vSphere Replication 12 Pairing vCenter Site Recovery Manager with Virtual SAN www.rackspace.com
- 13. • Storage Policies – vSphere Replication lists available storage polices at target/recovery site – vSphere Replication will allow non-compliant storage policies – SRM won’t create placeholder vSphere Replication 13 Pairing vCenter Site Recovery Manager with Virtual SAN www.rackspace.com
- 14. Pairing vCenter Site Recovery Manager with Virtual SAN SRM Configuration 14www.rackspace.com
- 15. Pairing vCenter Site Recovery Manager with Virtual SAN • Same rules still apply – VM can be a member of only one Protection Group – Protection Group can contain one or more VMs – Protection Group can be a member of multiple Recovery Plans – Can have multiple Recovery Plans consisting of different Protection Groups – Can have multiple Recovery Plans with different network mappings – Boot Priority is an attribute of the VM and follows the VM across Protection Groups • Set boot priority based on Protection Group – Example: Tier 1 Protection Group VMs all set to boot priority 1; Tier 2 VMs set to boot priority 2, etc – Multiple boot priorities extends recovery time SRM Configuration 15www.rackspace.com
- 16. Pairing vCenter Site Recovery Manager with Virtual SAN • IP Customizations have changed in 5.8 – Define at network mapping • Specify Network Prefix to change – Will change subnet, leaves host number the same • Specify gateway • DNS servers • DNS search suffixes • Primary & secondary WINS server – Manually configure each VM – Dr-ip-customizer.exe still exists SRM Configuration 16www.rackspace.com
- 17. Pairing vCenter Site Recovery Manager with Virtual SAN Live Demo! 17www.rackspace.com
- 18. THANK YOU RACKSPACE® | 1 FANATICAL PLACE, CITY OF WINDCREST | SAN ANTONIO, TX 78218 US SALES: 1-800-961-2888 | US SUPPORT: 1-800-961-4454 | WWW.RACKSPACE.COM © RACKSPACE LTD. | RACKSPACE® AND FANATICAL SUPPORT® ARE SERVICE MARKS OF RACKSPACE US, INC. REGISTERED IN THE UNITED S TATES AND OTHER COUNTRIES. | WWW.RACKSPACE.COM
Editor's Notes
- #6: vSAN HCL is separate from standard VMware HCL For multiple VSAN clusters, they *MUST* have different multicast addresses
- #8: SRM 5.8 no longer includes vSphere Replication, it must be installed separately. It is recommended/preferred to install prior to installing SRM.
- #12: Before upgrading vSphere Replication, be sure to power cycle the VRA via vCenter. The *POWER ON* function MUST be done through vCenter to build the ovfEnv.xml
- #14: vSphere Replication lists the vsanDatastore as compatible with FTT=2, despite it only having four nodes. vSphere Replication will complete and replicate the VM, but SRM will fail when trying to create the placeholder.