{"id":58444,"date":"2023-08-31T09:00:44","date_gmt":"2023-08-31T07:00:44","guid":{"rendered":"https:\/\/nolabnoparty.com\/?p=58444"},"modified":"2023-09-05T10:05:40","modified_gmt":"2023-09-05T08:05:40","slug":"nakivo-site-recovery-vms-re-protect-pt-2","status":"publish","type":"post","link":"https:\/\/nolabnoparty.com\/en\/nakivo-site-recovery-vms-re-protect-pt-2\/","title":{"rendered":"Nakivo Site Recovery: VMs Re-protect - pt.2"},"content":{"rendered":"

\"nakivo-site-recovery-vms-re-protect-01\"<\/p>\n

Once the Nakivo Site Recovery Job has been configured, failed over VMs should be protected to avoid a single point of failure<\/strong> scenario.<\/p>\n

In case of a disaster in the Primary site, VMs are failed over to the DR site to quickly restore services and data accessibility. Because source VMs are offline<\/strong> due to Primary Site failure, VMs running in the DR Site are not protected and they are the only working copies available.<\/p>\n

If something bad occurs at the DR Site, you don't have any weapon available to quickly restore the affected VMs<\/strong>.<\/p>\n

\"nakivo-site-recovery-vms-re-protect-02\"<\/p>\n

For this reason VMs running at the DR Site should be replicated in a temporary safe site<\/strong> until the Primary Site has been fixed. Nakivo Site Recovery<\/a>\u00a0provides the capability to\u00a0configure automated replication<\/strong>\u00a0when a VM failover process is completed.<\/p>\n

\"nakivo-site-recovery-vms-re-protect-03\"<\/p>\n

 <\/p>\n

Blog series<\/h2>\n

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

 <\/p>\n

Configure VMs Re-Protect in Nakivo Site Recovery<\/h2>\n

Create a new Replication Job for the replicated VMs and configure the replica from the DR Site to a temporary site<\/strong>. This allows to replicate the failed over VMs to a temporary site<\/strong> until the Primary Site has been fixed.<\/p>\n

\"nakivo-site-recovery-vms-re-protect-04\"<\/p>\n

From the Jobs<\/strong> section, select the Site Recovery Job previously created and click Edit<\/strong>.<\/p>\n

\"nakivo-site-recovery-vms-re-protect-05\"<\/p>\n

Select Run Jobs<\/strong> from the Actions<\/strong> list.<\/p>\n

\"nakivo-site-recovery-vms-re-protect-06\"<\/p>\n

Select the Replication Job created to re-protect the DR replicas from the job list (in the example Replication DR Re-protect<\/em>) and specify the Action options<\/strong> parameters. Click Save<\/strong>.<\/p>\n

\"nakivo-site-recovery-vms-re-protect-07\"<\/p>\n

To give the replica some time to boot<\/strong> before starting the Replication Job, select Wait<\/strong> from the Actions<\/strong> job list.<\/p>\n

\"nakivo-site-recovery-vms-re-protect-08\"<\/p>\n

Specify the desired Time to wait<\/strong> (for example 5 minutes) and Action options<\/strong> then click Save<\/strong>.<\/p>\n

\"nakivo-site-recovery-vms-re-protect-09\"<\/p>\n

To run boot and Replication Job operations with the correct sequence<\/strong>, select Wait<\/strong> action and click Move up<\/strong> to move the Wait action before the Replication Job.<\/p>\n

\"nakivo-site-recovery-vms-re-protect-10\"<\/p>\n

When the actions are arranged with the correct sequence, click Save<\/strong>. The Re-protection procedure has been completed.<\/p>\n

\"nakivo-site-recovery-vms-re-protect-11\"<\/p>\n

 <\/p>\n

Run the Failover with Re-protect<\/h2>\n

To verify if the configuration works as expected, we need to run the just configured Site Recovery Job.<\/p>\n

From Nakivo Backup & Replication<\/a> Jobs<\/strong> section, select the Site Recovery Job previously created and click Run > Run site recovery job<\/strong>.<\/p>\n

\"nakivo-site-recovery-vms-re-protect-12\"<\/p>\n

Select Planned Failover<\/strong> and click Run<\/strong>. The failover operation is triggered for the selected VMs with an automatic re-protection<\/strong> of the VM replicas.<\/p>\n

\"nakivo-site-recovery-vms-re-protect-13\"<\/p>\n

The Job performs the failover of replicated VMs<\/strong> to the DR Site.<\/p>\n

\"nakivo-site-recovery-vms-re-protect-14\"<\/p>\n

After completing the failover operation source VMs in the Primary Site are powered off<\/strong> and the corresponding VM replicas are now running in the DR Site. Bear in mind that running VM replicas are now the only copies available<\/strong> in the infrastructure.<\/p>\n

\"nakivo-site-recovery-vms-re-protect-15\"<\/p>\n

Completed the failover action, the Re-protect replica is triggered<\/strong> against the failed over VMs.<\/p>\n

\"nakivo-site-recovery-vms-re-protect-16\"<\/p>\n

Now all configured VM replicas are running in the DR Site in a failover state and as soon as the Primary Site is restored<\/strong>, failed over VMs should be moved back<\/strong> from the DR Site.<\/p>\n

Part 3<\/a> will cover the Failback procedure<\/strong> to move VMs back retaining changes occurred while running at DR site.<\/p>\n

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

Once the Nakivo Site Recovery Job has been configured, failed over VMs should be protected to avoid a single point of failure scenario. In case of a disaster in the Primary site, VMs are failed over to the DR site to quickly restore services and data accessibility. Because source VMs are offline due to Primary Site failure, VMs running in the DR Site are not protected and they are the only working copies available.<\/p>\n","protected":false},"author":3,"featured_media":58889,"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":[579,935,936,1903],"class_list":["post-58444","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-backup-en","category-nakivo-en","tag-backup-en","tag-disaster-recovery-en","tag-restore-en","tag-site-recovery","has_thumb"],"_links":{"self":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/58444","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=58444"}],"version-history":[{"count":0,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/58444\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media\/58889"}],"wp:attachment":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media?parent=58444"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/categories?post=58444"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/tags?post=58444"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}