<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic vSphere Replication with Site Recovery Manager in VMware vSphere™ Discussions</title>
    <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/vSphere-Replication-with-Site-Recovery-Manager/m-p/2745484#M35145</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, &lt;/P&gt;&lt;P&gt;I'm new to using SRM with vSphere Replication.&amp;nbsp; In the past I've always had storage array replication.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Versions:&lt;/P&gt;&lt;P&gt;SRM 8.1.0 (Build 8738384)&lt;/P&gt;&lt;P&gt;vSphere Replication 8.1.0 (Build 8744176)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So on to my question.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the past when I've done it with Storage array replication, once I fail over I just reprotect and it only has to start replicating changes back to the source instead of having to re-seed the entire VMFS volume/LUN.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've noticed that once I reprotect a VM after failover it will start a reverse replication and it has to replicate the entire VM again the other way!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there no way to make it keep the original VM files on the source and just replicate changes back when reversing?&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does that make sense?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With the way I'm seeing vsphere replication work, it would take a long time to replicate all the VMs back.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 06 Jul 2018 19:18:37 GMT</pubDate>
    <dc:creator>JodyWongGunvorU</dc:creator>
    <dc:date>2018-07-06T19:18:37Z</dc:date>
    <item>
      <title>vSphere Replication with Site Recovery Manager</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/vSphere-Replication-with-Site-Recovery-Manager/m-p/2745484#M35145</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, &lt;/P&gt;&lt;P&gt;I'm new to using SRM with vSphere Replication.&amp;nbsp; In the past I've always had storage array replication.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Versions:&lt;/P&gt;&lt;P&gt;SRM 8.1.0 (Build 8738384)&lt;/P&gt;&lt;P&gt;vSphere Replication 8.1.0 (Build 8744176)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So on to my question.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the past when I've done it with Storage array replication, once I fail over I just reprotect and it only has to start replicating changes back to the source instead of having to re-seed the entire VMFS volume/LUN.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've noticed that once I reprotect a VM after failover it will start a reverse replication and it has to replicate the entire VM again the other way!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there no way to make it keep the original VM files on the source and just replicate changes back when reversing?&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does that make sense?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With the way I'm seeing vsphere replication work, it would take a long time to replicate all the VMs back.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 06 Jul 2018 19:18:37 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/vSphere-Replication-with-Site-Recovery-Manager/m-p/2745484#M35145</guid>
      <dc:creator>JodyWongGunvorU</dc:creator>
      <dc:date>2018-07-06T19:18:37Z</dc:date>
    </item>
    <item>
      <title>Re: vSphere Replication with Site Recovery Manager</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/vSphere-Replication-with-Site-Recovery-Manager/m-p/2745485#M35146</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Actually it only replicate back the changed blocks at DR site, but a task with Full Synchronization appear due the fact it is making the checksum of the disks, see:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.vmware.com/en/Site-Recovery-Manager/8.1/com.vmware.srm.admin.doc/GUID-1DE0E76D-1BA7-44D8-AEA2-5B2218E219B1.html" title="https://docs.vmware.com/en/Site-Recovery-Manager/8.1/com.vmware.srm.admin.doc/GUID-1DE0E76D-1BA7-44D8-AEA2-5B2218E219B1.html"&gt;How Site Recovery Manager Reprotects Virtual Machines with vSphere Replication&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;&lt;SPAN style="color: #212529; font-family: Metropolis, 'Avenir Next', 'Helvetica Neue', Arial, sans-serif; background-color: #fafafa;"&gt;When performing reprotection with &lt;/SPAN&gt;&lt;SPAN class="ph productname" style="color: #212529; font-family: Metropolis, 'Avenir Next', 'Helvetica Neue', Arial, sans-serif; background-color: #fafafa;"&gt;vSphere Replication&lt;/SPAN&gt;&lt;SPAN style="color: #212529; font-family: Metropolis, 'Avenir Next', 'Helvetica Neue', Arial, sans-serif; background-color: #fafafa;"&gt;, &lt;/SPAN&gt;&lt;SPAN class="ph productname" style="color: #212529; font-family: Metropolis, 'Avenir Next', 'Helvetica Neue', Arial, sans-serif; background-color: #fafafa;"&gt;Site Recovery Manager&lt;/SPAN&gt;&lt;SPAN style="color: #212529; font-family: Metropolis, 'Avenir Next', 'Helvetica Neue', Arial, sans-serif; background-color: #fafafa;"&gt; uses the original VMDK files as initial copies during synchronization. The full synchronization that appears in the recovery steps mostly performs checksums, and only a small amount of data is transferred through the network.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 07 Jul 2018 23:38:30 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/vSphere-Replication-with-Site-Recovery-Manager/m-p/2745485#M35146</guid>
      <dc:creator>rcporto</dc:creator>
      <dc:date>2018-07-07T23:38:30Z</dc:date>
    </item>
    <item>
      <title>Re: vSphere Replication with Site Recovery Manager</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/vSphere-Replication-with-Site-Recovery-Manager/m-p/2745486#M35147</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hmm, is there some way for me to verify that?&amp;nbsp; It looks like it does a full sync back.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Jul 2018 17:33:10 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/vSphere-Replication-with-Site-Recovery-Manager/m-p/2745486#M35147</guid>
      <dc:creator>JodyWongGunvorU</dc:creator>
      <dc:date>2018-07-09T17:33:10Z</dc:date>
    </item>
    <item>
      <title>Re: vSphere Replication with Site Recovery Manager</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/vSphere-Replication-with-Site-Recovery-Manager/m-p/2745487#M35148</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;So I just did a reprotect of a 50GB windows VM.&amp;nbsp; The amount of data needed to transfer constantly changes as the sync operation percentage goes up.&amp;nbsp; Is this normal?&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="reprotect.JPG"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/2725i1773A249B525FBF9/image-size/large?v=v2&amp;amp;px=999" role="button" title="reprotect.JPG" alt="reprotect.JPG" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="reprotect2.JPG"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/2727i243C058F27B5BCBF/image-size/large?v=v2&amp;amp;px=999" role="button" title="reprotect2.JPG" alt="reprotect2.JPG" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Jul 2018 16:41:48 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/vSphere-Replication-with-Site-Recovery-Manager/m-p/2745487#M35148</guid>
      <dc:creator>JodyWongGunvorU</dc:creator>
      <dc:date>2018-07-11T16:41:48Z</dc:date>
    </item>
    <item>
      <title>Re: vSphere Replication with Site Recovery Manager</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/vSphere-Replication-with-Site-Recovery-Manager/m-p/2745488#M35149</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, because note that the checksum is in progress yet, so, while the checksum do not finish, maybe the amount of data to transfer will increase. But, at the end, only the different data will be transferred... the amount of time to the checksum finish will depends of your storage performance.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 12 Jul 2018 20:16:36 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/vSphere-Replication-with-Site-Recovery-Manager/m-p/2745488#M35149</guid>
      <dc:creator>rcporto</dc:creator>
      <dc:date>2018-07-12T20:16:36Z</dc:date>
    </item>
  </channel>
</rss>

