{"id":38546,"date":"2019-09-03T09:00:28","date_gmt":"2019-09-03T07:00:28","guid":{"rendered":"https:\/\/nolabnoparty.com\/?p=38546"},"modified":"2023-04-12T10:54:25","modified_gmt":"2023-04-12T08:54:25","slug":"vsphere-replication-8-x-deployment-pt-1","status":"publish","type":"post","link":"https:\/\/nolabnoparty.com\/en\/vsphere-replication-8-x-deployment-pt-1\/","title":{"rendered":"vSphere Replication 8.x: deployment - pt.1"},"content":{"rendered":"<p><img decoding=\"async\" class=\"aligncenter wp-image-39694 size-full\" title=\"vmware-vsphere-replication-deployment-01\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-deployment-01.jpg\" alt=\"vmware-vsphere-replication-deployment-01\" width=\"602\" height=\"202\" \/><\/p>\n<p>VMware vSphere Replication 8.x is the VMware solution for <strong>replicating production VMs<\/strong> in order to implement a <a href=\"https:\/\/nolabnoparty.com\/en\/vmware-vcenter-high-availability-setup-pt-1\/\">DR site or a migration strategy<\/a> to avoid services disruption.<\/p>\n<p>vSphere Replication can perform replication of virtual machines in the vSphere environment from production site to <strong>another site or to the same site<\/strong>. It is a component deployed as appliance and it is included in the vSphere solution with no need to purchase <strong>any additional license<\/strong>.<!--more--><\/p>\n<p>&nbsp;<\/p>\n<h2>Blog series<\/h2>\n<p>vSphere Replication 8.x deployment - pt.1<br \/>\n<a href=\"https:\/\/nolabnoparty.com\/en\/vsphere-replication-8-x-failover-pt-2\/\">vSphere Replication 8.x failover - pt.2<\/a><br \/>\n<a href=\"https:\/\/nolabnoparty.com\/en\/vsphere-replication-8-x-traffic-isolation-pt-3\/\">vSphere Replication 8.x traffic isolation - pt.3<\/a><br \/>\n<a href=\"https:\/\/nolabnoparty.com\/en\/vsphere-replication-8-x-seeding-pt-4\/\">vSphere Replication 8.x seeding - pt.4<\/a><\/p>\n<p>&nbsp;<\/p>\n<h2>vSphere Replication 8.x<\/h2>\n<p>vSphere Replication is a free product completely integrated with <a href=\"https:\/\/nolabnoparty.com\/en\/vcenter-server-6-7-converge-tool-embed-external-psc-into-vcsa\/\">vCenter Server<\/a> and allows the replication of virtual machines protecting such VMs from <strong>production site failure<\/strong>.<\/p>\n<p>With this solution you can replicate VMs from the following sites:<\/p>\n<ul>\n<li>From production site to another site (DR site).<\/li>\n<li>In the same site from one cluster to a different cluster.<\/li>\n<\/ul>\n<p>The last one is a typical use case when you need to <strong>migrate VMs from an old infrastructure<\/strong> to a new one.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39696 size-full\" title=\"vmware-vsphere-replication-deployment-02\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-deployment-02.jpg\" alt=\"vmware-vsphere-replication-deployment-02\" width=\"580\" height=\"320\" \/><\/p>\n<p>&nbsp;<\/p>\n<h4>vSphere Replication 8.2<\/h4>\n<p>Although the procedure described in this article refers to version 8.1.2, the newest vSphere Replication 8.2 has been released providing some new features:<\/p>\n<ul>\n<li>Support for VMware vSphere 6.7 Update 2.<\/li>\n<li><strong>Support for VM encryption<\/strong> - using vSphere 6.7 U1 or later encrypted virtual machines can be replicated.<\/li>\n<li><strong>Enable network encryption<\/strong> - using VMware vSphere 6.0 or later transferred replication data can be encrypted.<\/li>\n<li><strong>Enhancements to the Site Recovery UI<\/strong> - target datastores can be monitored in the Site Recovery UI replication details.<\/li>\n<li><strong>vRealize Operations Management Pack<\/strong> - RPO violations and a better visibility of the vSphere Replication status are additional info provided with new version 8.2.<\/li>\n<li><strong>vRealize Orchestrator Plug-In for vSphere Replication 8.2<\/strong>.<\/li>\n<\/ul>\n<p>vSphere Replication 8.2 supports the following versions:<\/p>\n<ul>\n<li>vCenter - 6.0 Update 3 or later<\/li>\n<li>ESXi - 6.0 Udate 3 or later<\/li>\n<li>vSAN - 6.5\u00a0or later<\/li>\n<\/ul>\n<p>Although version 8.1.2 has been used during the deployment, the installation and configuration <strong>procedures are the same<\/strong> also for version 8.2.<\/p>\n<p>&nbsp;<\/p>\n<h2>Deploy vSphere Replication 8.x in vSphere 6.7<\/h2>\n<p>To deploy vSphere Replication, you need to <a href=\"https:\/\/my.vmware.com\/en\/web\/vmware\/info\/slug\/datacenter_cloud_infrastructure\/vmware_vsphere\/6_7\" target=\"_blank\" rel=\"noopener noreferrer\">download the ISO file<\/a> from VMware website.<\/p>\n<p>From vSphere Client, right click the inventory object where to deploy the appliance and select <strong>Deploy OVF Template<\/strong> option.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39698 size-large\" title=\"vmware-vsphere-replication-deployment-03\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-deployment-03-600x469.jpg\" alt=\"vmware-vsphere-replication-deployment-03\" width=\"600\" height=\"469\" \/><\/p>\n<p>Click <strong>Browse<\/strong> to select the installation files then click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39700 size-large\" title=\"vmware-vsphere-replication-deployment-04\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-deployment-04-600x495.jpg\" alt=\"vmware-vsphere-replication-deployment-04\" width=\"600\" height=\"495\" \/><\/p>\n<p>These are the correct files to use for deployment.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39702 size-large\" title=\"vmware-vsphere-replication-deployment-05\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-deployment-05-600x361.jpg\" alt=\"vmware-vsphere-replication-deployment-05\" width=\"600\" height=\"361\" \/><\/p>\n<p>Specify the <strong>Virtual machine name<\/strong> and the location then click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39704 size-large\" title=\"vmware-vsphere-replication-deployment-06\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-deployment-06-600x495.jpg\" alt=\"vmware-vsphere-replication-deployment-06\" width=\"600\" height=\"495\" \/><\/p>\n<p>Select the <strong>compute resource<\/strong> to use and click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39706 size-large\" title=\"vmware-vsphere-replication-deployment-07\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-deployment-07-600x495.jpg\" alt=\"vmware-vsphere-replication-deployment-07\" width=\"600\" height=\"495\" \/><\/p>\n<p>Click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39708 size-large\" title=\"vmware-vsphere-replication-deployment-08\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-deployment-08-600x495.jpg\" alt=\"vmware-vsphere-replication-deployment-08\" width=\"600\" height=\"495\" \/><\/p>\n<p>Accept the EULA and click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39710 size-large\" title=\"vmware-vsphere-replication-deployment-09\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-deployment-09-600x495.jpg\" alt=\"vmware-vsphere-replication-deployment-09\" width=\"600\" height=\"495\" \/><\/p>\n<p>Specify the required number of vCPUs to use (2 or 4) and click <strong>Next<\/strong>. Depending on the number of VMs to replicate, vSphere Replication can be deployed in two ways:<\/p>\n<ul>\n<li>2 vCPU, 8 Gb RAM<\/li>\n<li>4 vCPU, 16Gb RAM<\/li>\n<\/ul>\n<p>Keep in mind that during the replication process, CPU and RAM of the <strong>source host are consumed<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39712 size-large\" title=\"vmware-vsphere-replication-deployment-10\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-deployment-10-600x495.jpg\" alt=\"vmware-vsphere-replication-deployment-10\" width=\"600\" height=\"495\" \/><\/p>\n<p>Select the <strong>virtual disk format<\/strong> and the <strong>datastore<\/strong> to use. Click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39714 size-large\" title=\"vmware-vsphere-replication-deployment-11\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-deployment-11-600x495.jpg\" alt=\"vmware-vsphere-replication-deployment-11\" width=\"600\" height=\"495\" \/><\/p>\n<p>Select the <strong>Destination Network<\/strong> (by default vSphere Replication uses the management network for its traffic) and click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39716 size-large\" title=\"vmware-vsphere-replication-deployment-12\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-deployment-12-600x495.jpg\" alt=\"vmware-vsphere-replication-deployment-12\" width=\"600\" height=\"495\" \/><\/p>\n<p>Specify the appliance's parameters by entering <strong>Password<\/strong>, <strong>NTP Servers<\/strong> and <strong>Hostname<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39718 size-large\" title=\"vmware-vsphere-replication-deployment-13\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-deployment-13-600x495.jpg\" alt=\"vmware-vsphere-replication-deployment-13\" width=\"600\" height=\"495\" \/><\/p>\n<p>Specify the <strong>Network Properties<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39720 size-full\" title=\"vmware-vsphere-replication-deployment-14\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-deployment-14.jpg\" alt=\"vmware-vsphere-replication-deployment-14\" width=\"560\" height=\"593\" \/><\/p>\n<p>Last two options to specify are the <strong>Management Network IP Address<\/strong> of the appliance and the <strong>Management Network Netmask<\/strong>. Click <strong>Next<\/strong> to continue.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39722 size-large\" title=\"vmware-vsphere-replication-deployment-15\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-deployment-15-600x495.jpg\" alt=\"vmware-vsphere-replication-deployment-15\" width=\"600\" height=\"495\" \/><\/p>\n<p>Specify the <strong>vService bindings<\/strong> then click <strong>Next<\/strong>. Previous versions required to <strong>specify this parameter through the flex<\/strong> version of vSphere Web Client but now this issue has been fixed.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39724 size-large\" title=\"vmware-vsphere-replication-deployment-16\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-deployment-16-600x495.jpg\" alt=\"vmware-vsphere-replication-deployment-16\" width=\"600\" height=\"495\" \/><\/p>\n<p>Click <strong>Finish<\/strong> to proceed with appliance deployment.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39726 size-large\" title=\"vmware-vsphere-replication-deployment-17\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-deployment-17-600x495.jpg\" alt=\"vmware-vsphere-replication-deployment-17\" width=\"600\" height=\"495\" \/><\/p>\n<p>&nbsp;<\/p>\n<h2>Link the vSphere Replication to the vCenter<\/h2>\n<p>Once the appliance has been deployed successfully, right click the vSphere Replication appliance and select <strong>Power &gt; Power On<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39736 size-large\" title=\"vmware-vsphere-replication-deployment-18\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-deployment-18-600x434.jpg\" alt=\"vmware-vsphere-replication-deployment-18\" width=\"600\" height=\"434\" \/><\/p>\n<p>Access the appliance's console to <strong>check the IP address<\/strong> to use to connect.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39738 size-large\" title=\"vmware-vsphere-replication-deployment-19\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-deployment-19-600x445.jpg\" alt=\"vmware-vsphere-replication-deployment-19\" width=\"600\" height=\"445\" \/><\/p>\n<p>While attempting to connect the appliance management console via browser you may receive an error. You just need to <strong>wait a little bit<\/strong> to allow services to properly start, then try again.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39740 size-full\" title=\"vmware-vsphere-replication-deployment-20\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-deployment-20.jpg\" alt=\"vmware-vsphere-replication-deployment-20\" width=\"240\" height=\"144\" \/><\/p>\n<p>Enter <strong>root <\/strong>as <strong>User name<\/strong> and the <strong>Password<\/strong> specified during the configuration of the installer. Click <strong>Login<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39742 size-large\" title=\"vmware-vsphere-replication-deployment-21\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-deployment-21-600x173.jpg\" alt=\"vmware-vsphere-replication-deployment-21\" width=\"600\" height=\"173\" \/><\/p>\n<p>Specify the <strong>LookupService Address<\/strong> by entering the vCSA address for a PSC embedded topology or the PSC address if an external PSC topology is used instead. Make sure to enter the correct <strong>SSO Administrator<\/strong> and <strong>Password<\/strong> then click on <strong>Save and Restart Service<\/strong> button.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39744 size-large\" title=\"vmware-vsphere-replication-deployment-22\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-deployment-22-600x649.jpg\" alt=\"vmware-vsphere-replication-deployment-22\" width=\"600\" height=\"649\" \/><\/p>\n<p>Accept the SSL self-signed certificate by clicking <strong>Accept<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39746 size-large\" title=\"vmware-vsphere-replication-deployment-23\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-deployment-23-600x328.jpg\" alt=\"vmware-vsphere-replication-deployment-23\" width=\"600\" height=\"328\" \/><\/p>\n<p>If a wrong PSC, SSO Administrator or Password has been entered, you may receive a similar error. Just <strong>double check entered parameters<\/strong> and try again.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39748 size-large\" title=\"vmware-vsphere-replication-deployment-24\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-deployment-24-600x318.jpg\" alt=\"vmware-vsphere-replication-deployment-24\" width=\"600\" height=\"318\" \/><\/p>\n<p>The green message confirms the appliance is now connected to the vCSA\/PSC and the <strong>Service Status<\/strong> area reports services are running.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39750 size-large\" title=\"vmware-vsphere-replication-deployment-25\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-deployment-25-600x531.jpg\" alt=\"vmware-vsphere-replication-deployment-25\" width=\"600\" height=\"531\" \/><\/p>\n<p>&nbsp;<\/p>\n<h2>Configure vSphere Replication<\/h2>\n<p>From the vSphere Client click <strong>Menu &gt; Site Recovery<\/strong> to access the appliance configuration.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39752 size-large\" title=\"vmware-vsphere-replication-deployment-26\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-deployment-26-600x463.jpg\" alt=\"vmware-vsphere-replication-deployment-26\" width=\"600\" height=\"463\" \/><\/p>\n<p>In the <strong>Site Recovery<\/strong> area, click <strong>OPEN Site Recovery<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39754 size-large\" title=\"vmware-vsphere-replication-deployment-27\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-deployment-27-600x279.jpg\" alt=\"vmware-vsphere-replication-deployment-27\" width=\"600\" height=\"279\" \/><\/p>\n<p>Click <strong>View Details<\/strong>. Notice that this configuration uses a <strong>single vCenter topology<\/strong> and replications occur within the same vCenter.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39766 size-large\" title=\"vmware-vsphere-replication-deployment-28\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-deployment-28-600x382.jpg\" alt=\"vmware-vsphere-replication-deployment-28\" width=\"600\" height=\"382\" \/><\/p>\n<p>In the <strong>Summary<\/strong> tab you can check the connected vCenter Server.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39768 size-large\" title=\"vmware-vsphere-replication-deployment-29\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-deployment-29-600x283.jpg\" alt=\"vmware-vsphere-replication-deployment-29\" width=\"600\" height=\"283\" \/><\/p>\n<p>In the <strong>Replication Servers<\/strong> tab you can see the replication servers in use.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39772 size-large\" title=\"vmware-vsphere-replication-deployment-30\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-deployment-30-600x283.jpg\" alt=\"vmware-vsphere-replication-deployment-30\" width=\"600\" height=\"283\" \/><\/p>\n<p>&nbsp;<\/p>\n<h2>Configure a replication job<\/h2>\n<p>To configure a replication job, select one or more VMs then right click the selection and choose <strong>All Site Recovery actions &gt; Configure Replication<\/strong> option.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39774 size-large\" title=\"vmware-vsphere-replication-deployment-31\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-deployment-31-600x485.jpg\" alt=\"vmware-vsphere-replication-deployment-31\" width=\"600\" height=\"485\" \/><\/p>\n<p>Click <strong>Yes<\/strong> to open the replication wizard for the selected VMs.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39776 size-full\" title=\"vmware-vsphere-replication-deployment-32\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-deployment-32.jpg\" alt=\"vmware-vsphere-replication-deployment-32\" width=\"576\" height=\"206\" \/><\/p>\n<p>Click <strong>Next<\/strong> to proceed with replica configuration.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39778 size-large\" title=\"vmware-vsphere-replication-deployment-33\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-deployment-33-600x346.jpg\" alt=\"vmware-vsphere-replication-deployment-33\" width=\"600\" height=\"346\" \/><\/p>\n<p>Select the <strong>Target Site<\/strong> (the configured vCenter in this example) and the replication server to use (Auto-assign or Manual) if multiple replication servers are deployed. Click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39780 size-large\" title=\"vmware-vsphere-replication-deployment-34\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-deployment-34-600x346.jpg\" alt=\"vmware-vsphere-replication-deployment-34\" width=\"600\" height=\"346\" \/><\/p>\n<p>Specify the <strong>Disk format<\/strong> and the <strong>Target datastore<\/strong>. Additional options available in this configuration page allow to <strong>assign different datastores<\/strong> to the VM's disks and to specify if the <strong>replica should use seeds<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39782 size-large\" title=\"vmware-vsphere-replication-deployment-35\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-deployment-35-600x346.jpg\" alt=\"vmware-vsphere-replication-deployment-35\" width=\"600\" height=\"346\" \/><\/p>\n<p>By default VM's disks are <strong>located to same datastore<\/strong> but VMDK disks can also be <strong>assigned to different datastores<\/strong>. Click on <strong>Change<\/strong> link to <strong>specify a different datastore<\/strong> for a specific Hard disk.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39784 size-large\" title=\"vmware-vsphere-replication-deployment-36\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-deployment-36-600x346.jpg\" alt=\"vmware-vsphere-replication-deployment-36\" width=\"600\" height=\"346\" \/><\/p>\n<p>Select the datastore to use for the selected Hard disk then click <strong>OK<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39786 size-large\" title=\"vmware-vsphere-replication-deployment-37\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-deployment-37-600x348.jpg\" alt=\"vmware-vsphere-replication-deployment-37\" width=\"600\" height=\"348\" \/><\/p>\n<p>Specify the <strong>required RPO<\/strong> for the replica as well as the retention to adopt by flagging the <strong>Enable point in time instances<\/strong>. To optimize replica consistency and network performance, <strong>Enable guest OS quiescing<\/strong> and <strong>Enable network compression for VR data<\/strong> options to provide additional capabilities to the replica. Click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39788 size-large\" title=\"vmware-vsphere-replication-deployment-38\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-deployment-38-600x346.jpg\" alt=\"vmware-vsphere-replication-deployment-38\" width=\"600\" height=\"346\" \/><\/p>\n<p>Click <strong>Finish<\/strong> to save the configuration.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39790 size-large\" title=\"vmware-vsphere-replication-deployment-39\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-deployment-39-600x346.jpg\" alt=\"vmware-vsphere-replication-deployment-39\" width=\"600\" height=\"346\" \/><\/p>\n<p>To execute the replication job, it is mandatory the <strong>virtual machine is powered on<\/strong> otherwise the replication wizard will display a warning.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39792 size-large\" title=\"vmware-vsphere-replication-deployment-40\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-deployment-40-600x346.jpg\" alt=\"vmware-vsphere-replication-deployment-40\" width=\"600\" height=\"346\" \/><\/p>\n<p>Click <strong>Replications<\/strong> to check the replication status of selected virtual machines.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39794 size-large\" title=\"vmware-vsphere-replication-deployment-41\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-deployment-41-600x273.jpg\" alt=\"vmware-vsphere-replication-deployment-41\" width=\"600\" height=\"273\" \/><\/p>\n<p>Depending on the <strong>VM size and available bandwidth<\/strong>, after some minutes the replication is completed successfully.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39796 size-large\" title=\"vmware-vsphere-replication-deployment-42\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-deployment-42-600x233.jpg\" alt=\"vmware-vsphere-replication-deployment-42\" width=\"600\" height=\"233\" \/><\/p>\n<p>The replicated VMs are now ready to be fired up in case of need.\u00a0<a href=\"https:\/\/nolabnoparty.com\/en\/vsphere-replication-8-x-failover-pt-2\/\">Part 2<\/a> will explain how to perform a failover to <strong>quickly restore services<\/strong> provided if the source VM fails for any reason.<\/p>\n<p><img decoding=\"async\" title=\"signature\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/images\/firma.jpg\" alt=\"signature\" \/><\/p>\n","protected":false},"excerpt":{"rendered":"<p>VMware vSphere Replication 8.x is the VMware solution for replicating production VMs in order to implement a DR site or a migration strategy to avoid services disruption. vSphere Replication can perform replication of virtual machines in the vSphere environment from production site to another site or to the same site. It is a component deployed as appliance and it is included in the vSphere solution with no need to purchase any additional license.<\/p>\n","protected":false},"author":3,"featured_media":39694,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"rop_custom_images_group":[],"rop_custom_messages_group":[],"rop_publish_now":"initial","rop_publish_now_accounts":{"linkedin_93tdZWzMZc_93tdZWzMZc":"","facebook_2879994398731222_17841400390232720":"","twitter_113568041_113568041":"","mastodon_115463926174894442_115463926174894442":""},"rop_publish_now_history":[],"rop_publish_now_status":"pending","footnotes":""},"categories":[2138,2642],"tags":[2012,582,700],"class_list":["post-38546","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-backup-en","category-vsphere-replication-en","tag-deployment-en","tag-replication-en","tag-vsphere-en","has_thumb"],"_links":{"self":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/38546","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/comments?post=38546"}],"version-history":[{"count":0,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/38546\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media\/39694"}],"wp:attachment":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media?parent=38546"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/categories?post=38546"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/tags?post=38546"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}