There are a lot of different products in the replication and recovery space today. The two big players in this arena are Zerto and VMware Site Recovery Mananager. VMware SRM is the incumbant in this space as it has been around for a long time.
VMware SRM requires its own database. This database is used to store data such as recovery plan and inventory information. In this deployment we will utilize the embedded Postgress DB included with the install. This will minimize the dependencies between SRM and a stand alone SQL server.
We will be installing SRM in a Two-Site topology with one vCenter Server instance per PSC.
A few house keeping items to keep in mind before we start with the installation.
- Use the FQDN whenever possible rather than IP Addresses. Using the FQDN rather than the IP addresses allows you to change the vSphere infrastrucutre if needed.
- You must have the SSO username and password during the installation for each PSC
- Ensure the clocks are sync’d for the PSC, vCenter and SRM servers.
- Download the SRM installation software from VMware
- Double click the SRM installer
- Follow the installer prompts to accept the EULA and verifiy you have satisfied the install prereqs.
- Chose where to install SRM – Click Next
- Enter the information about the PSC at the site where you are installing SRM
- If prompted, verify the PSC certificate and Accept it
- Select the vCenter server instance that you want to register SRM and click next.
- If prompted, verify the vCenter certificate and Accept it
- Enter information with which to register the SRM extension with vCenter server, and click Next
- Local Site Name – A name for this SRM site – this will appear in the SRM interface.
- Administrator Email – Email address of the SRM administrator(s).
- Local Host – You can enter the IP or FQDN. As mentioned above, I highly recommend using the FQDN.
- Select the default SRM plug-in identifier. Since we will have a standard configuration with one protected site and one recovery site – click next
- Select a certificate type, click next
- If using “Automatically generate certificate” click next and type in values for your organization and oranization unit. Click next
- Select whether to user the embedded database or a cutom database, click next.
- Provide the SRM database configuration and click next
- Data Source Name – This option is only visable if using the embedded database. This can be named anything – I prefer to name it to the site SRM is protecting
- Database Username – Enter a username for the database user account for the embedded DB.
- Database Password – Enter a password for the database
- Database Port – The default port is 5678- leave this at default unless there is a business reason to change it.
- Select the user account under which to run the SRM Server service – Click next.
- Select the Local System Account to run the SRM server service under the Local System Account.
- Click Install
- When finished, click Finish
- Repeat these steps at the other site.
Pair SRM Sites
- Connect to the vSphere Web Client on one of the sites, and Select Site Recovery > Sites
- Right Click a site and select Pair Site
- Enter the address of the PSC for the Recovery Site and click Next
- Select the vCenter server with which SRM server is registered on the remote site – provide the vCenter SSO username and password, click Finish
- If prompted, verify each of the certs from the local PSC and vCenter.
As with all VMware products, SRM requires a license key to operate.
- Connect to the vSphere Web-Client on which SRM is installed
- On the vSphere Web Client Home tab, click Licensing
- Click on the plus sign on the License Tab
- Enter the SRM license key in the License keys text box and click next
- Update the license name. I typically name the license key for the product and the site.
- Click on Assets tab and click Assign License
- Select the license from the list and available licenses and click OK
- Repeat steps to assign the SRM license keys to all vCenter instances.
Let me know if you have any questions about the install.