VMware Site Recovery Manager 5 Lab Setup
The following Diagram illustrates the setup required for the following VMware Site Recovery Manager 5 tutorial series. This series guides you through how to setup VMware Site Recovery Manger 5 with Netapp as the underlying storage subsystem.
If you are using a different SAN vendor, the steps will be almost identical, so you are still able to following these tutorials.
VMware Site Recovery Manager 5 – Primary and Secondary Sites
The Site Recovery Manager Primary Site consists of a Domain Controller, VMware vCenter 5 Server, VMware ESXi 5 Host, a Netapp SAN and 2 Virtual Machines entitled Windows 2008 Web 1 and Windows 2008 Web 2.
The Site Recovery Manager Secondary Site consists of a Domain Controller, VMware vCenter 5 Server, VMware ESXi 5 Host, a Netapp SAN and 2 Virtual Machines entitled Windows 2008 Web 1 and Windows 2008 Web 2.
VMware Site Recovery Manager 5 – Active Directory
The Active Directory domain controllers are Windows 2008 R2 Servers. The Active Directory Domain is called vmlab.local
VMware Site Recovery Manager 5 – VMware vSphere
The VMware vSphere setup is running VMware vCenter 5 with it’s database on Microsoft SQL 2008 R2 Express. Both installed on the same Server. Each VMware host is running ESXi 5 consisting of 3 network adapter. 1. VM Network and Management, 2. vMotion, 3. NFS Storage.
VMware Site Recovery Manager 5 – Netapp Storage
The Netapp Storage utilizes 2 network connections – 1. Management, 2. NFS Storage. At the Site Recovery Manager 5 Primary Site the SAN has a hostname of san1. There is a volume called Vmware_Primary and within this volume a qtree called qtree_vmware_datastore. The 2 Netapp SANs have Snapmirror enabled.The qtree at the primary site is synchronized, asynchronously at 15min intervals to the Secondary Sites’ SAN called san2.
VMware Site Recovery Manager 5 – Lab Diagram
All the tutorials included on this site are performed in a lab environment to simulate a real world production scenario. As everything is done to provide the most accurate steps to date, we take no responsibility if you implement any of these steps in a production environment.