{"id":38544,"date":"2019-09-12T09:00:38","date_gmt":"2019-09-12T07:00:38","guid":{"rendered":"https:\/\/nolabnoparty.com\/?p=38544"},"modified":"2023-04-12T10:53:30","modified_gmt":"2023-04-12T08:53:30","slug":"vsphere-replication-8-x-seeding-pt-4","status":"publish","type":"post","link":"https:\/\/nolabnoparty.com\/en\/vsphere-replication-8-x-seeding-pt-4\/","title":{"rendered":"vSphere Replication 8.x: seeding - pt.4"},"content":{"rendered":"<p><img decoding=\"async\" class=\"aligncenter wp-image-39642 size-full\" title=\"vmware-vsphere-replication-seeding-01\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-seeding-01.jpg\" alt=\"vmware-vsphere-replication-seeding-01\" width=\"602\" height=\"202\" \/><\/p>\n<p>To reduce the network traffic generated by the initial synchronization, vSphere Replication provides the seeding capability to limit the data to transfer.<\/p>\n<p>This option allows to quickly perform the initial replication without transferring the entire virtual machine to the target datastore. This allows to <strong>reduce the required time<\/strong> to complete the task and <strong>limit the data to transfer<\/strong> especially if the <strong>network is busy<\/strong> or if the available <strong>bandwidth is poor<\/strong>.<!--more--><\/p>\n<p>&nbsp;<\/p>\n<h2>Blog series<\/h2>\n<p><a href=\"https:\/\/nolabnoparty.com\/en\/vsphere-replication-8-x-deployment-pt-1\/\">vSphere Replication 8.x deployment - pt.1<\/a><br \/>\n<a href=\"https:\/\/nolabnoparty.com\/en\/vsphere-replication-8-x-failover-pt-2\/\">vSphere Replication 8.x failover - pt.2<\/a><br \/>\n<a href=\"https:\/\/nolabnoparty.com\/en\/vsphere-replication-8-x-traffic-isolation-pt-3\/\">vSphere Replication 8.x traffic isolation - pt.3<\/a><br \/>\nvSphere Replication 8.x seeding - pt.4<\/p>\n<p>&nbsp;<\/p>\n<h2>How vSphere Replication seeding works<\/h2>\n<p>To <strong>reduce the initial replication data transferred<\/strong> over the network, virtual disk files of VMs to replicate can be copied in the target datastore and <strong>used as replication seeds<\/strong> when the replication job is configured.<\/p>\n<p>During the replication procedure, <a href=\"https:\/\/www.vmware.com\/latam\/products\/vsphere\/replication.html\" target=\"_blank\" rel=\"noopener noreferrer\">vSphere Replication<\/a> <strong>compares differences<\/strong> occurred on the source and target site replicating only the <strong>changed blocks<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39644 size-full\" title=\"vmware-vsphere-replication-seeding-02\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-seeding-02.jpg\" alt=\"vmware-vsphere-replication-seeding-02\" width=\"566\" height=\"180\" \/><\/p>\n<p>When the replication job is configured a <strong>target datastore must be specified<\/strong> to store the replicated VM. When the target datastore has been selected, the system checks if a <strong>disk with the same filename<\/strong> already exists in the datastore. If the same filename is found, you have the option to <strong>use the existing disk file as a seed<\/strong> for the replication. If this option is selected, a new page is available in the wizard where seeds for each disk of the VM can be specified. The result you can obtain is the reduction of the network traffic since only <strong>changed blocks will be replicated<\/strong>.<\/p>\n<p>If you don't want to use the seed option, replica files are <strong>placed in a new directory with a unique name<\/strong>.<\/p>\n<p>&nbsp;<\/p>\n<h2>Configure vSphere Replication seeding<\/h2>\n<p>The seeding process is composed by three main steps:<\/p>\n<ul>\n<li>Download source VMDK files<\/li>\n<li>Upload VMDK files to target site<\/li>\n<li>Configure the replication job<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<h4>Download source VMDK files<\/h4>\n<p>Access the datastore where the source virtual machine is stored and <strong>locate the VM folder<\/strong>. Select the correct folder and click <strong>Download<\/strong> from the available options to download the <a href=\"https:\/\/nolabnoparty.com\/en\/vsphere-vms-encryption-encrypt-virtual-machines-pt-3\/\">VMDK files<\/a> on the local computer. To download these files, the source virtual machine must be <strong>powered off<\/strong>\u00a0first.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39646 size-large\" title=\"vmware-vsphere-replication-seeding-03\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-seeding-03-600x312.jpg\" alt=\"vmware-vsphere-replication-seeding-03\" width=\"600\" height=\"312\" \/><\/p>\n<p>Click <strong>Download<\/strong> to confirm.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39648 size-full\" title=\"vmware-vsphere-replication-seeding-04\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-seeding-04.jpg\" alt=\"vmware-vsphere-replication-seeding-04\" width=\"516\" height=\"250\" \/><\/p>\n<p>A <strong>ZIP file<\/strong> containing the source VMDK files is created in the chosen location.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39650 size-full\" title=\"vmware-vsphere-replication-seeding-05\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-seeding-05.jpg\" alt=\"vmware-vsphere-replication-seeding-05\" width=\"546\" height=\"252\" \/><\/p>\n<p>&nbsp;<\/p>\n<h4>Upload VMDK files to target Site<\/h4>\n<p>In the target Site, access the <strong>Storage<\/strong> area and select the datastore where the VM files should be copied. Click <strong>Datastore browser<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39652 size-large\" title=\"vmware-vsphere-replication-seeding-06\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-seeding-06-600x289.jpg\" alt=\"vmware-vsphere-replication-seeding-06\" width=\"600\" height=\"289\" \/><\/p>\n<p>When the target datastore has been selected, click <strong>Create directory<\/strong>. Enter a <strong>Directory name<\/strong> and click on <strong>Create directory<\/strong>\u00a0button.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39654 size-large\" title=\"vmware-vsphere-replication-seeding-07\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-seeding-07-600x321.jpg\" alt=\"vmware-vsphere-replication-seeding-07\" width=\"600\" height=\"321\" \/><\/p>\n<p>Click <strong>Upload<\/strong> to copy the VM files to the just created new directory. A the end of the <a href=\"https:\/\/nolabnoparty.com\/en\/vsphere-error-when-uploading-files-to-datastores\/\">upload process<\/a>, all source VM files are stored in the selected datastore.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39656 size-large\" title=\"vmware-vsphere-replication-seeding-08\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-seeding-08-600x321.jpg\" alt=\"vmware-vsphere-replication-seeding-08\" width=\"600\" height=\"321\" \/><\/p>\n<p>&nbsp;<\/p>\n<h4>Configure the replication job<\/h4>\n<p>Once the VM files have been copied to the target datastore, in vSphere Client right click the VM to replicate and select <strong>All Site Recovery actions &gt; Configure Replication<\/strong>. The <strong>Configure Replication<\/strong> wizard is displayed showing the <strong>VM validation<\/strong> status that indicates if the selected VM can be configured for replication. Click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39658 size-large\" title=\"vmware-vsphere-replication-seeding-09\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-seeding-09-600x346.jpg\" alt=\"vmware-vsphere-replication-seeding-09\" width=\"600\" height=\"346\" \/><\/p>\n<p>Specify the <strong>Target Site<\/strong> and the <strong>vSphere Replication server<\/strong> then click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39660 size-large\" title=\"vmware-vsphere-replication-seeding-10\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-seeding-10-600x346.jpg\" alt=\"vmware-vsphere-replication-seeding-10\" width=\"600\" height=\"346\" \/><\/p>\n<p>Specify the <strong>Target datastore<\/strong> to use and enable the <strong>Select seeds<\/strong> option. Click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39662 size-large\" title=\"vmware-vsphere-replication-seeding-11\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-seeding-11-600x346.jpg\" alt=\"vmware-vsphere-replication-seeding-11\" width=\"600\" height=\"346\" \/><\/p>\n<p>In the <strong>Select seed<\/strong> section, click the <strong>Seed<\/strong> drop-down menu and select <strong>Browse<\/strong> to locate the source VMDK files.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39664 size-large\" title=\"vmware-vsphere-replication-seeding-12\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-seeding-12-600x346.jpg\" alt=\"vmware-vsphere-replication-seeding-12\" width=\"600\" height=\"346\" \/><\/p>\n<p>Access the <strong>folder containing the source VM files<\/strong> previously copied and select the corrisponding hard disk (VMDK file) you want to seed. Note the reported source VMDK file size is 16 GB.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39666 size-large\" title=\"vmware-vsphere-replication-seeding-13\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-seeding-13-600x350.jpg\" alt=\"vmware-vsphere-replication-seeding-13\" width=\"600\" height=\"350\" \/><\/p>\n<p>Once the appropriated hard disk has been selected, enable <strong>The selected seeds are correct<\/strong> option to confirm that the selection is correct.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39668 size-large\" title=\"vmware-vsphere-replication-seeding-14\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-seeding-14-600x346.jpg\" alt=\"vmware-vsphere-replication-seeding-14\" width=\"600\" height=\"346\" \/><\/p>\n<p><strong>The selected seeds are correct<\/strong> option is mandatory to continue the configuration. If not checked, an <strong>error message<\/strong> is displayed.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39670 size-large\" title=\"vmware-vsphere-replication-seeding-15\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-seeding-15-600x241.jpg\" alt=\"vmware-vsphere-replication-seeding-15\" width=\"600\" height=\"241\" \/><\/p>\n<p>Specify the <strong>RPO<\/strong> for the replica then click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39672 size-large\" title=\"vmware-vsphere-replication-seeding-16\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-seeding-16-600x346.jpg\" alt=\"vmware-vsphere-replication-seeding-16\" width=\"600\" height=\"346\" \/><\/p>\n<p>Review the selected settings then click <strong>Finish<\/strong> to save the configuration and start the replica.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39674 size-large\" title=\"vmware-vsphere-replication-seeding-17\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-seeding-17-600x346.jpg\" alt=\"vmware-vsphere-replication-seeding-17\" width=\"600\" height=\"346\" \/><\/p>\n<p>The initial synchronization is being performed.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39676 size-large\" title=\"vmware-vsphere-replication-seeding-18\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-seeding-18-600x317.jpg\" alt=\"vmware-vsphere-replication-seeding-18\" width=\"600\" height=\"317\" \/><\/p>\n<p>When the replication has been completed successfully, you can notice the <strong>transferred data are only few MB<\/strong> instead of the full size of the VM (the source VMDK file is 16 GB). It means the replication seed worked as expected <strong>transferring only the changes<\/strong> occurred in the virtual machine from the initial copy.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-39678 size-large\" title=\"vmware-vsphere-replication-seeding-19\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2019\/08\/vmware-vsphere-replication-seeding-19-600x239.jpg\" alt=\"vmware-vsphere-replication-seeding-19\" width=\"600\" height=\"239\" \/><\/p>\n<p>Using the replication seeds, the used bandwidth and the time required are <strong>very limited<\/strong> providing the big benefits of keeping the network performance unaltered and saving time.<\/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>To reduce the network traffic generated by the initial synchronization, vSphere Replication provides the seeding capability to limit the data to transfer. This option allows to quickly perform the initial replication without transferring the entire virtual machine to the target datastore. This allows to reduce the required time to complete the task and limit the data to transfer especially if the network is busy or if the available bandwidth is poor.<\/p>\n","protected":false},"author":3,"featured_media":39642,"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":[582,2011,700],"class_list":["post-38544","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-backup-en","category-vsphere-replication-en","tag-replication-en","tag-seeding","tag-vsphere-en","has_thumb"],"_links":{"self":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/38544","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=38544"}],"version-history":[{"count":0,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/38544\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media\/39642"}],"wp:attachment":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media?parent=38544"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/categories?post=38544"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/tags?post=38544"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}