{"id":61613,"date":"2024-06-14T09:00:47","date_gmt":"2024-06-14T07:00:47","guid":{"rendered":"https:\/\/nolabnoparty.com\/?p=61613"},"modified":"2024-06-24T10:51:30","modified_gmt":"2024-06-24T08:51:30","slug":"veeam-recovery-orchestrator-v7-recovery-locations-pt-3","status":"publish","type":"post","link":"https:\/\/nolabnoparty.com\/en\/veeam-recovery-orchestrator-v7-recovery-locations-pt-3\/","title":{"rendered":"Veeam Recovery Orchestrator v7: Recovery Locations - pt.3"},"content":{"rendered":"<p><img decoding=\"async\" class=\"aligncenter wp-image-61729 size-full\" title=\"veeam-recovery-orchestrator-v7-recovery-locations-pt-3-01\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2024\/06\/veeam-recovery-orchestrator-v7-recovery-locations-pt-3-01.jpg\" alt=\"veeam-recovery-orchestrator-v7-recovery-locations-pt-3-01\" width=\"602\" height=\"202\" \/><\/p>\n<p>Veeam Recovery Orchestrator (VRO) uses Recovery Locations to <strong>create resource groups used as target locations<\/strong> when orchestrating recovery.<\/p>\n<p>There are <strong>three Recovering Locations supported<\/strong> by VRO:<!--more--><\/p>\n<ul>\n<li>VMware Recovery<\/li>\n<li>Storage Recovery<\/li>\n<li>Microsoft Azure Recovery<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<h2>Blog Series<\/h2>\n<p><a href=\"https:\/\/nolabnoparty.com\/en\/veeam-recovery-orchestrator-v7-installation-pt-1\/\">Veeam Recovery Orchestrator v7 installation - pt. 1<\/a><br \/>\n<a href=\"https:\/\/nolabnoparty.com\/en\/veeam-recovery-orchestrator-v7-tags-pt-2\/\">Veeam Recovery Orchestrator v7 Tags - pt.2<\/a><br \/>\nVeeam Recovery Orchestrator v7 Recovery Locations - pt.3<br \/>\n<a href=\"https:\/\/nolabnoparty.com\/en\/veeam-recovery-orchestrator-v7-recovery-plans-replica-pt-4\/\">Veeam Recovery Orchestrator v7 Recovery Plans replica - pt.4<\/a><br \/>\n<a href=\"https:\/\/nolabnoparty.com\/en\/veeam-recovery-orchestrator-v7-recovery-plans-agent-pt-5\/\">Veeam Recovery Orchestrator v7 Recovery Plans agent - pt.5<\/a><br \/>\n<a href=\"https:\/\/nolabnoparty.com\/en\/veeam-recovery-orchestrator-v7-recovery-plans-backup-pt-6\/\">Veeam Recovery Orchestrator v7 Recovery Plans backup - pt.6<\/a><br \/>\n<a href=\"https:\/\/nolabnoparty.com\/en\/veeam-recovery-orchestrator-v7-datalabs-pt-7\/\">Veeam Recovery Orchestrator v7 DataLabs - pt.7<\/a><\/p>\n<p>&nbsp;<\/p>\n<h2>Create Recovery Locations<\/h2>\n<p>Login to <a href=\"https:\/\/www.veeam.com\/disaster-recovery-orchestrator.html\" target=\"_blank\" rel=\"noopener\">Veeam Recovery Orchestrator<\/a> console and go to <strong>Administration<\/strong> area.<\/p>\n<p>Access the <strong>Recovery Locations<\/strong> section and click <strong>Add<\/strong> to add a Location.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-large wp-image-61731\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2024\/06\/veeam-recovery-orchestrator-v7-recovery-locations-pt-3-02-600x316.jpg\" alt=\"\" width=\"600\" height=\"316\" title=\"\"><\/p>\n<p>&nbsp;<\/p>\n<h4>Recover from backup<\/h4>\n<p>Select <strong>VMware<\/strong> and click <strong>Next<\/strong>.<\/p>\n<h4><img decoding=\"async\" class=\"aligncenter size-large wp-image-61733\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2024\/06\/veeam-recovery-orchestrator-v7-recovery-locations-pt-3-03-600x471.jpg\" alt=\"\" width=\"600\" height=\"471\" title=\"\"><\/h4>\n<p>Type a <strong>Name<\/strong> for the location and optionally a <strong>Description<\/strong>. Click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-large wp-image-61735\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2024\/06\/veeam-recovery-orchestrator-v7-recovery-locations-pt-3-04-600x471.jpg\" alt=\"\" width=\"600\" height=\"471\" title=\"\"><\/p>\n<p>In the <strong>Recovery Options<\/strong> select <strong>Recover VM backups<\/strong> to recover the VMs from backups. Click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-large wp-image-61737\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2024\/06\/veeam-recovery-orchestrator-v7-recovery-locations-pt-3-05-600x471.jpg\" alt=\"\" width=\"600\" height=\"471\" title=\"\"><\/p>\n<p>Select the <strong>Compute Group<\/strong> to use identified by the tag assigned to the Hosts in the vCenter Server (DR Site) then click <strong>Add<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-large wp-image-61739\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2024\/06\/veeam-recovery-orchestrator-v7-recovery-locations-pt-3-06-600x471.jpg\" alt=\"\" width=\"600\" height=\"471\" title=\"\"><\/p>\n<p>The selected resource has been assigned to the <strong>Compute Groups<\/strong>. Click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-large wp-image-61741\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2024\/06\/veeam-recovery-orchestrator-v7-recovery-locations-pt-3-07-600x471.jpg\" alt=\"\" width=\"600\" height=\"471\" title=\"\"><\/p>\n<p>Do the same with <strong>Storage Resources<\/strong> and click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-large wp-image-61743\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2024\/06\/veeam-recovery-orchestrator-v7-recovery-locations-pt-3-08-600x471.jpg\" alt=\"\" width=\"600\" height=\"471\" title=\"\"><\/p>\n<p>Select <strong>Use backup copies<\/strong> in the <strong>Storage Options<\/strong> to take benefit of backup copies when recovering VMs. Backup Copies work only if created and used by the same Veeam VBR. Click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-large wp-image-61745\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2024\/06\/veeam-recovery-orchestrator-v7-recovery-locations-pt-3-09-600x471.jpg\" alt=\"\" width=\"600\" height=\"471\" title=\"\"><\/p>\n<p>In <strong>VM Networks<\/strong> section click <strong>Add<\/strong> to define a new network mapping. Specify <strong>both Source and Target vSphere network<\/strong> and click <strong>Save<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-large wp-image-61747\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2024\/06\/veeam-recovery-orchestrator-v7-recovery-locations-pt-3-10-600x471.jpg\" alt=\"\" width=\"600\" height=\"471\" title=\"\"><\/p>\n<p>In <strong>Re-IP Rules<\/strong>\u00a0section click <strong>Add<\/strong> to define a new IP remapping. Specify <strong>IP Address<\/strong> and <strong>Subnet Mask<\/strong> of <strong>Source and Target VM<\/strong> as well as <strong>Default gateway<\/strong> and <strong>DNS server<\/strong>. Click <strong>Add<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-large wp-image-61749\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2024\/06\/veeam-recovery-orchestrator-v7-recovery-locations-pt-3-11-600x471.jpg\" alt=\"\" width=\"600\" height=\"471\" title=\"\"><\/p>\n<p>Select <strong>Enforce data sovereignty<\/strong> option if required and click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-large wp-image-61751\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2024\/06\/veeam-recovery-orchestrator-v7-recovery-locations-pt-3-12-600x471.jpg\" alt=\"\" width=\"600\" height=\"471\" title=\"\"><\/p>\n<p>Click <strong>Finish<\/strong> to save the configuration.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-large wp-image-61753\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2024\/06\/veeam-recovery-orchestrator-v7-recovery-locations-pt-3-13-600x471.jpg\" alt=\"\" width=\"600\" height=\"471\" title=\"\"><\/p>\n<p>The created <strong>VMs Backup Recovery<\/strong> location.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-large wp-image-61755\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2024\/06\/veeam-recovery-orchestrator-v7-recovery-locations-pt-3-14-600x269.jpg\" alt=\"\" width=\"600\" height=\"269\" title=\"\"><\/p>\n<p>&nbsp;<\/p>\n<h4>Instant VM Recovery<\/h4>\n<p>Follow the <strong>same procedure<\/strong> as done in previous steps.<\/p>\n<p>Type a <strong>Name<\/strong> for the location and optionally a <strong>Description<\/strong>. Click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-large wp-image-61757\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2024\/06\/veeam-recovery-orchestrator-v7-recovery-locations-pt-3-15-600x471.jpg\" alt=\"\" width=\"600\" height=\"471\" title=\"\"><\/p>\n<p>In the <strong>Recovery Options<\/strong> select <strong>Recover VM backups<\/strong> and <strong>Enable Instant VM Recovery<\/strong>. Click <strong>Next<\/strong> and configure the remaining settings.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-large wp-image-61759\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2024\/06\/veeam-recovery-orchestrator-v7-recovery-locations-pt-3-16-600x471.jpg\" alt=\"\" width=\"600\" height=\"471\" title=\"\"><\/p>\n<p>The created <strong>VMs Instant Recovery<\/strong> location.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-large wp-image-61761\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2024\/06\/veeam-recovery-orchestrator-v7-recovery-locations-pt-3-17-600x265.jpg\" alt=\"\" width=\"600\" height=\"265\" title=\"\"><\/p>\n<p>&nbsp;<\/p>\n<h4>Agent Backup Recovery<\/h4>\n<p>Again, follow the <strong>same above procedure<\/strong> to add a new location.<\/p>\n<p>Type a <strong>Name<\/strong> for the location and optionally a <strong>Description<\/strong>. Click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-large wp-image-61763\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2024\/06\/veeam-recovery-orchestrator-v7-recovery-locations-pt-3-18-600x471.jpg\" alt=\"\" width=\"600\" height=\"471\" title=\"\"><\/p>\n<p>In the <strong>Recovery Options<\/strong> select <strong>Recover agent backups<\/strong> to recover the VMs from <a href=\"https:\/\/nolabnoparty.com\/en\/veeam-failed-to-acquire-agent-managed-by-error\/\">Veeam Agent<\/a> backups. Click <strong>Next<\/strong>\u00a0and configure the remaining steps.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-large wp-image-61765\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2024\/06\/veeam-recovery-orchestrator-v7-recovery-locations-pt-3-19-600x471.jpg\" alt=\"\" width=\"600\" height=\"471\" title=\"\"><\/p>\n<p>Configure the correct <strong>Agent Networks<\/strong> and click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-large wp-image-61767\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2024\/06\/veeam-recovery-orchestrator-v7-recovery-locations-pt-3-20-600x471.jpg\" alt=\"\" width=\"600\" height=\"471\" title=\"\"><\/p>\n<p>The created <strong>Agent Instant Recovery<\/strong> location.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-large wp-image-61769\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2024\/06\/veeam-recovery-orchestrator-v7-recovery-locations-pt-3-21-600x267.jpg\" alt=\"\" width=\"600\" height=\"267\" title=\"\"><\/p>\n<p>Once the Recovery Locations have been created, next step is the <strong>creation of Recovery Plans<\/strong>\u00a0covered in <a href=\"https:\/\/nolabnoparty.com\/en\/veeam-recovery-orchestrator-v7-recovery-plans-replica-pt-4\/\">part 4<\/a>.<\/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>Veeam Recovery Orchestrator (VRO) uses Recovery Locations to create resource groups used as target locations when orchestrating recovery. There are three Recovering Locations supported by VRO:<\/p>\n","protected":false},"author":3,"featured_media":61729,"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,933],"tags":[2842,2841,2840],"class_list":["post-61613","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-backup-en","category-veeam-en","tag-disaster","tag-recovery-locations","tag-recovery-orchestrator","has_thumb"],"_links":{"self":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/61613","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=61613"}],"version-history":[{"count":0,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/61613\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media\/61729"}],"wp:attachment":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media?parent=61613"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/categories?post=61613"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/tags?post=61613"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}