{"id":58600,"date":"2023-09-05T09:00:28","date_gmt":"2023-09-05T07:00:28","guid":{"rendered":"https:\/\/nolabnoparty.com\/?p=58600"},"modified":"2023-09-04T14:03:09","modified_gmt":"2023-09-04T12:03:09","slug":"nakivo-site-recovery-failback-pt-3","status":"publish","type":"post","link":"https:\/\/nolabnoparty.com\/en\/nakivo-site-recovery-failback-pt-3\/","title":{"rendered":"Nakivo Site Recovery: Failback - pt.3"},"content":{"rendered":"

\"nakivo-site-recovery-failback-01\"<\/p>\n

When the Primary Site has been fixed, Nakivo Site Recovery must be configured to perform the failback operation to move back running VMs<\/strong> from the DR site to preserve changed data.<\/p>\n

When the production site fails, the failover to a VM replica action is triggered<\/strong> to quickly restore services and data accessibility. Because VMs are now running in the DR site, any changes to the VMs are stored in the DR datastore<\/strong> not accessible from the source VMs.<\/p>\n

When the primary site has been fixed, VMs running in the DR Site must be brought back to the production site<\/strong> restoring the data changed during the failover time. VM replicas must then be re-synchronized using the failback<\/strong> process.<\/p>\n

\"nakivo-site-recovery-failback-02\"<\/p>\n

 <\/p>\n

Blog series<\/h2>\n

Nakivo Site Recovery: Job creation - pt.1<\/a>
\nNakivo Site Recovery: VMs Re-protect - pt.2<\/a>
\nNakivo Site Recovery: Failback - pt.3<\/p>\n

 <\/p>\n

Configure Failback in Nakivo Site Recovery<\/h2>\n

The Failback operation can be performed in production mode or in test mode<\/strong>.<\/p>\n

Before performing the Failback action, you need a configured Site Recovery Job with a Failover action included<\/strong>. VM replicas must be in failover state<\/strong>.<\/p>\n

\"nakivo-site-recovery-failback-03\"<\/p>\n

From Nakivo's dashboard\u00a0access the\u00a0Jobs<\/strong>\u00a0area, click the\u00a0+ icon<\/strong>\u00a0then select\u00a0Site recovery job<\/strong>\u00a0under\u00a0Site Recovery Job<\/strong>.<\/p>\n

\"nakivo-site-recovery-failback-04\"<\/p>\n

Select Failback VMware VMs<\/strong> (if the VMware platform is in use) action and click Next<\/strong>.<\/p>\n

\"nakivo-site-recovery-failback-05\"<\/p>\n

Select the VM replicas in failover state you want to failback<\/strong> then click Next<\/strong>.<\/p>\n

\"nakivo-site-recovery-failback-06\"<\/p>\n

Select the Failback location<\/strong> where VMs should be restored (Original location<\/strong> or New location<\/strong>) and click Next<\/strong>.<\/p>\n

\"nakivo-site-recovery-failback-07\"<\/p>\n

In the Options<\/strong> tab, enable the\u00a0Power off replica VMs<\/strong> option if the failback action is performed to the production site. Click Save<\/strong>.<\/p>\n

\"nakivo-site-recovery-failback-08\"<\/p>\n

When the Failback configuration has been completed, click Next<\/strong>.<\/p>\n

\"nakivo-site-recovery-failback-09\"<\/p>\n

If the VLANs between DR an Production sites are different, thick the Enable network mapping<\/strong> checkbox and assign the correct VLAN by clicking the Create new mapping<\/strong> link. Click Next<\/strong>\u00a0when done.<\/p>\n

\"nakivo-site-recovery-failback-10\"<\/p>\n

When the required network has been configured, click Next<\/strong>.<\/p>\n

\"nakivo-site-recovery-failback-11\"<\/p>\n

If the subnets between DR and Production sites are different, thick the Enable Re-IP<\/strong> checkbox and assign the correct subnet by clicking the Create new rule<\/strong> link.<\/p>\n

\"nakivo-site-recovery-failback-12\"<\/p>\n

Configure the New Re-IP Rule<\/strong> and click Save<\/strong>.<\/p>\n

\"nakivo-site-recovery-failback-13\"<\/p>\n

When the required rules have been assigned, click Next<\/strong>.<\/p>\n

\"nakivo-site-recovery-failback-14\"<\/p>\n

When prompted specify the correct credentials for the selected VMs then click X<\/strong> to exit. Click Next<\/strong> to continue.<\/p>\n

\"nakivo-site-recovery-failback-15\"<\/p>\n

Configure the Test Schedule<\/strong> options. This step is recommended to ensure that VM replicas can be recovered successfully and the RTO is met<\/strong>. Click Next<\/strong>.<\/p>\n

\"nakivo-site-recovery-failback-16\"<\/p>\n

Specify the Job name<\/strong> and click Finish<\/strong>.<\/p>\n

\"nakivo-site-recovery-failback-17\"<\/p>\n

 <\/p>\n

Run the Failback<\/h2>\n

Select the just configured Site Recovery Job and click Run<\/strong>\u00a0> Run site recovery job<\/strong>.<\/p>\n

\"nakivo-site-recovery-failback-18\"<\/p>\n

Click Run<\/strong>.<\/p>\n

\"nakivo-site-recovery-failback-19\"<\/p>\n

The failback operation is being executed.<\/p>\n

\"nakivo-site-recovery-failback-20\"<\/p>\n

After a few minutes the VMs failed back to production site successfully.<\/p>\n

\"nakivo-site-recovery-failback-21\"<\/p>\n

The failed back VMs in the Primary Site.<\/p>\n

\"nakivo-site-recovery-failback-22\"<\/p>\n

Failback operation can also be run in Test Mode<\/strong> (replicas are connected to an isolated network<\/strong>) to ensure that everything can be restored successfully.<\/p>\n

Nakivo Site Recovery is part of Nakivo Backup & Replication<\/a> and the product can be downloaded as 15-day trial<\/a>.<\/p>\n

\"signature\"<\/p>\n","protected":false},"excerpt":{"rendered":"

When the Primary Site has been fixed, Nakivo Site Recovery must be configured to perform the failback operation to move back running VMs from the DR site to preserve changed data. When the production site fails, the failover to a VM replica action is triggered to quickly restore services and data accessibility. Because VMs are now running in the DR site, any changes to the VMs are stored in the DR datastore not accessible from the source VMs.<\/p>\n","protected":false},"author":3,"featured_media":58924,"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,1697],"tags":[935,2119,1957,582],"class_list":["post-58600","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-backup-en","category-nakivo-en","tag-disaster-recovery-en","tag-failback","tag-failover-en","tag-replication-en","has_thumb"],"_links":{"self":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/58600","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=58600"}],"version-history":[{"count":0,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/58600\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media\/58924"}],"wp:attachment":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media?parent=58600"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/categories?post=58600"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/tags?post=58600"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}