{"id":61601,"date":"2024-06-12T09:00:05","date_gmt":"2024-06-12T07:00:05","guid":{"rendered":"https:\/\/nolabnoparty.com\/?p=61601"},"modified":"2024-06-24T10:50:24","modified_gmt":"2024-06-24T08:50:24","slug":"veeam-recovery-orchestrator-v7-tags-pt-2","status":"publish","type":"post","link":"https:\/\/nolabnoparty.com\/en\/veeam-recovery-orchestrator-v7-tags-pt-2\/","title":{"rendered":"Veeam Recovery Orchestrator v7: Tags - pt.2"},"content":{"rendered":"<p><img decoding=\"async\" class=\"aligncenter wp-image-61706 size-full\" title=\"veeam-recovery-orchestrator-v7-tags-pt-2-01\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2024\/06\/veeam-recovery-orchestrator-v7-tags-pt-2-01.jpg\" alt=\"veeam-recovery-orchestrator-v7-tags-pt-2-01\" width=\"602\" height=\"202\" \/><\/p>\n<p>Veeam Recovery Orchestrator (VRO) requires the creation of <strong>vSphere Tags<\/strong> to <strong>tag the VMware objects<\/strong> at the DR Site used to orchestrate DR events.<\/p>\n<p>These Tags are <strong>assigned to the resources such as Host and Datastore<\/strong> VRO will use to run VMs at DR Site when the failover operation is triggered.<!--more--><\/p>\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 \/>\nVeeam Recovery Orchestrator v7 Tags - pt.2<br \/>\n<a href=\"https:\/\/nolabnoparty.com\/en\/veeam-recovery-orchestrator-v7-recovery-locations-pt-3\/\">Veeam Recovery Orchestrator v7 Recovery Locations - pt.3<\/a><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 VMware vSphere Tags<\/h2>\n<p>Login to the <strong>VMware vSphere infrastructure<\/strong> at DR Site to create the required tags.<\/p>\n<p>From the vSphere Client, select <strong>Settings &gt; Tags &amp; Custom Attributes<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-full wp-image-61708\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2024\/06\/veeam-recovery-orchestrator-v7-tags-pt-2-02.jpg\" alt=\"\" width=\"561\" height=\"555\" title=\"\"><\/p>\n<p>Assign a <strong>Category Name<\/strong> (e.g. <em>Resources DR Site<\/em>) and select the <strong>Associable Object Types<\/strong>. <strong>Host<\/strong> and <strong>Datastore<\/strong> are the objects used by VRO. Click <strong>Create<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-large wp-image-61710\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2024\/06\/veeam-recovery-orchestrator-v7-tags-pt-2-03-600x435.jpg\" alt=\"\" width=\"600\" height=\"435\" title=\"\"><\/p>\n<p>The created category.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-large wp-image-61712\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2024\/06\/veeam-recovery-orchestrator-v7-tags-pt-2-04-600x371.jpg\" alt=\"\" width=\"600\" height=\"371\" title=\"\"><\/p>\n<p>Now create a Tag to identify <strong>Hosts<\/strong>. Assign a <strong>Name<\/strong> (e.g. <em>Host DR<\/em>) and select the <strong>Category<\/strong> previously created (e.g. <em>Resources DR Site<\/em>). Click <strong>Create<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-full wp-image-61714\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2024\/06\/veeam-recovery-orchestrator-v7-tags-pt-2-05.jpg\" alt=\"\" width=\"576\" height=\"399\" title=\"\"><\/p>\n<p>Create a Tag also to identify <strong>Datastores<\/strong>. Assign a <strong>Name<\/strong> (e.g. <em>Datastore DR<\/em>) and select the <strong>Category<\/strong> previously created (e.g. <em>Resources DR Site<\/em>). As a result two tags are available to identify Hosts and Datastores available at DR Site.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-large wp-image-61716\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2024\/06\/veeam-recovery-orchestrator-v7-tags-pt-2-06-600x379.jpg\" alt=\"\" width=\"600\" height=\"379\" title=\"\"><\/p>\n<p>&nbsp;<\/p>\n<h4>Assign Tag to Hosts<\/h4>\n<p>In the vSphere Client, select the Host configured in the DR infrastructure and in the <strong>Tags<\/strong> section assign the correct tag to the host.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-large wp-image-61718\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2024\/06\/veeam-recovery-orchestrator-v7-tags-pt-2-07-600x317.jpg\" alt=\"\" width=\"600\" height=\"317\" title=\"\"><\/p>\n<p>&nbsp;<\/p>\n<h4>Assign Tag to Datastores<\/h4>\n<p>Select the Datastore to use with VRO configured in the DR infrastructure. In the <strong>Tags<\/strong> section assign the created tag to the datastore.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-large wp-image-61720\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2024\/06\/veeam-recovery-orchestrator-v7-tags-pt-2-08-600x454.jpg\" alt=\"\" width=\"600\" height=\"454\" title=\"\"><\/p>\n<p>&nbsp;<\/p>\n<h2>Collect data details with Veeam ONE<\/h2>\n<p>Once the vSphere objects have been tagged, VRO needs to <strong>collect also the components details<\/strong> used to create Recovery Locations and Recovery Plans.<\/p>\n<p>In the virtual machine where Veeam Recovery Orchestrator was installed, open the Veeam ONE console and go to <strong>Configuration<\/strong> area. In the <strong>Data Collection<\/strong> section, click the <strong>Start<\/strong> button to collect the components defined in Veeam Recovery Orchestrator (vCenter Server and <a href=\"https:\/\/nolabnoparty.com\/en\/veeam-plugin-for-microsoft-sql\/\">Veeam Backup &amp; Replication<\/a> Servers).<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-large wp-image-61722\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2024\/06\/veeam-recovery-orchestrator-v7-tags-pt-2-09-600x302.jpg\" alt=\"\" width=\"600\" height=\"302\" title=\"\"><\/p>\n<p>System scans the environment to collect data.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-large wp-image-61724\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2024\/06\/veeam-recovery-orchestrator-v7-tags-pt-2-10-600x279.jpg\" alt=\"\" width=\"600\" height=\"279\" title=\"\"><\/p>\n<p>After a few seconds the data collection process completes and the <strong>Status<\/strong> is reported as <strong>Success<\/strong>. Under <strong>Details<\/strong> you can see the collected data.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-large wp-image-61726\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2024\/06\/veeam-recovery-orchestrator-v7-tags-pt-2-11-600x454.jpg\" alt=\"\" width=\"600\" height=\"454\" title=\"\"><\/p>\n<p><a href=\"https:\/\/www.veeam.com\/disaster-recovery-orchestrator.html?ad=menu-products-vdp\" target=\"_blank\" rel=\"noopener\">Veeam Recovery Orchestrator<\/a> is now ready to be configured with Recovery Locations and Recovery Plans.<\/p>\n<p><a href=\"https:\/\/nolabnoparty.com\/en\/veeam-recovery-orchestrator-v7-recovery-locations-pt-3\/\">Part 3<\/a> will cover the <strong>creation of Recovery Locations<\/strong> used to run workloads during a failover operation.<\/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) requires the creation of vSphere Tags to tag the VMware objects at the DR Site used to orchestrate DR events. These Tags are assigned to the resources such as Host and Datastore VRO will use to run VMs at DR Site when the failover operation is triggered.<\/p>\n","protected":false},"author":3,"featured_media":61706,"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":[935,2839,1708],"class_list":["post-61601","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-backup-en","category-veeam-en","tag-disaster-recovery-en","tag-orchestrator","tag-tags","has_thumb"],"_links":{"self":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/61601","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=61601"}],"version-history":[{"count":0,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/61601\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media\/61706"}],"wp:attachment":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media?parent=61601"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/categories?post=61601"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/tags?post=61601"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}