In a typical vSphere Replication installation, the local site provides business-critical data center services. The remote site is an alternative facility to which you can migrate these services.
The local site can be any site where vCenter Server supports a critical business need. The remote site can be in another location, or in the same facility to establish redundancy. The remote site is usually located in a facility that is unlikely to be affected by environmental, infrastructure, or other disturbances that might affect the local site.
vSphere Replication has the following requirements for the vSphere® environments at each site:
- Each site must have at least one data center.
- The remote site must have hardware, network, and storage resources that can support the same virtual machines and workloads as the local site.
- The sites must be connected by a reliable IP network.
- The remote site must have access to networks (public and private) comparable to the ones on the local site, although not necessarily the same range of network addresses.
Connecting Local and Remote Sites
Before you replicate virtual machines between two sites, you must connect the sites. When connecting sites, users at both sites must have the privilege assigned.
When you connect sites that are part of the same vCenter Single Sign-On domain, you must select the remote site only, without providing authentication details, because you are already logged in.
When you connect sites that belong to different vCenter Single Sign-On domains, the vSphere Replication Management Server must register with the Platform Services Controller on the remote site. You must provide authentication details for the remote site, including IP or FQDN of the server where Platform Services Controller runs, and user credentials. See Local and Remote Sites.
After connecting the sites, you can monitor the connectivity state between them in the Site Recovery user interface.
