![\"vmware-vsphere-replication-failover-01\"](\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-failover-01.jpg\" "\\"vmware-vsphere-replication-failover-01\\"")
<\/p>\n<\/p>\n
When the Production Site fails, the failover procedure of replicated VMs at DR Site with vSphere Replication can be initiated to quickly restore network services<\/strong>.<\/p>\n The failover procedure is an action that is performed quite easily in VMware vSphere<\/a> Replication and you just need few steps to fire up replicated VMs.<\/p>\n <\/p>\n vSphere Replication 8.x deployment - pt.1<\/a> <\/p>\n To check the status of replicated VMs <\/strong>ready to be powered on in case of need, access the Site Recovery and <\/strong>go to Replications<\/strong> area.<\/p>\n If the production virtual machine fails for any reason, its replica at DR Site can be fired up to quickly restore services<\/strong> provided.<\/p>\n To perform a failover, access the Site Recovery Replication<\/strong> page and right click the VM to be powered on. Select Recover<\/strong> from available options. Keep in mind that data stored in the replicated VM are updated based on latest replication<\/strong> occurred.<\/p>\n Select the Recovery option<\/strong> to use:<\/p>\n You can also flag the Power on the virtual machine after recovery<\/strong> to power on VMs automatically. Click Next<\/strong>.<\/p>\n Specify the Folder<\/strong> for the VM at the Recovery Site then click Next<\/strong>.<\/p>\n Specify the Resource<\/strong> to use at Recovery Site then click Next<\/strong>.<\/p>\n Click Finish<\/strong> to power on the replica. Remember that network devices will be disconnected<\/strong> in the recovered VM to avoid possible conflicts with Production Site.<\/p>\n After a few seconds the selected VM is up and running in the specified DR Site with the Status<\/strong> reported as Recovered<\/strong>.<\/p>\n Looking at the vSphere Client you can see the recovered virtual machine<\/strong>.<\/p>\n To connect the recovered VM to the network, you need to connect the Network device<\/strong>. Right click the VM and select Edit Settings<\/strong>. Enable the Connect<\/strong> option for the VM's network adapter.<\/p>\n If the RPO policy has been configured, the recovered VM will have a certain number of snapshots available based on the RPO set<\/strong>. Selecting one of these snapshots you can revert the VM to a specific point in time<\/strong>.<\/p>\n To failback to production retaining changes<\/strong> occured in the VM, you need to configure a reverse replication<\/strong> from the DR Site to the Production Site.<\/p>\n If vSphere Replication<\/a> is configured with default network, the appliance uses the management network<\/strong> to transfer replication data with the result of consuming the production network and affecting application performance. To avoid this situation, replication traffic should be isolated using a dedicated network. Part 3<\/a>\u00a0will explain how to isolate the traffic to improve overall performance<\/strong> without using the management network to transfer the data.<\/p>\n When the Production Site fails, the failover procedure of replicated VMs at DR Site with vSphere Replication can be initiated to quickly restore network services. The failover procedure is an action that is performed quite easily in VMware vSphere Replication and you just need few steps to fire up replicated VMs.<\/p>\n","protected":false},"author":3,"featured_media":39799,"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":[2023,1957,582],"class_list":["post-39190","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-backup-en","category-vsphere-replication-en","tag-dr-site","tag-failover-en","tag-replication-en","has_thumb"],"_links":{"self":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/39190","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=39190"}],"version-history":[{"count":0,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/39190\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media\/39799"}],"wp:attachment":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media?parent=39190"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/categories?post=39190"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/tags?post=39190"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Blog series<\/h2>\n
\nvSphere Replication 8.x failover - pt.2
\nvSphere Replication 8.x traffic isolation - pt.3<\/a>
\nvSphere Replication 8.x seeding - pt.4<\/a><\/p>\nPerform failover<\/h2>\n
![\"vmware-vsphere-replication-failover-02\"](\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-failover-02-600x363.jpg\" "\\"vmware-vsphere-replication-failover-02\\"")
<\/p>\n![\"vmware-vsphere-replication-failover-03\"](\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-failover-03-600x412.jpg\" "\\"vmware-vsphere-replication-failover-03\\"")
<\/p>\n\n
![\"vmware-vsphere-replication-failover-04\"](\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-failover-04-600x384.jpg\" "\\"vmware-vsphere-replication-failover-04\\"")
<\/p>\n![\"vmware-vsphere-replication-failover-05\"](\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-failover-05-600x384.jpg\" "\\"vmware-vsphere-replication-failover-05\\"")
<\/p>\n![\"vmware-vsphere-replication-failover-06\"](\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-failover-06-600x384.jpg\" "\\"vmware-vsphere-replication-failover-06\\"")
<\/p>\n![\"vmware-vsphere-replication-failover-07\"](\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-failover-07-600x384.jpg\" "\\"vmware-vsphere-replication-failover-07\\"")
<\/p>\n![\"vmware-vsphere-replication-failover-08\"](\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-failover-08-600x270.jpg\" "\\"vmware-vsphere-replication-failover-08\\"")
<\/p>\n![\"vmware-vsphere-replication-failover-09\"](\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-failover-09-600x325.jpg\" "\\"vmware-vsphere-replication-failover-09\\"")
<\/p>\n![\"vmware-vsphere-replication-failover-10\"](\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-failover-10-600x460.jpg\" "\\"vmware-vsphere-replication-failover-10\\"")
<\/p>\n![\"vmware-vsphere-replication-failover-11\"](\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-failover-11-600x388.jpg\" "\\"vmware-vsphere-replication-failover-11\\"")
<\/p>\n![\"signature\"](\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/images\/firma.jpg\" "\\"signature\\"")
<\/p>\n","protected":false},"excerpt":{"rendered":"