<?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 Deployed vSphere Replication however seem to be getting the attached unhelpful error :( in Site Recovery Manager Discussions</title>
    <link>https://communities.vmware.com/t5/Site-Recovery-Manager/Deployed-vSphere-Replication-however-seem-to-be-getting-the/m-p/484522#M2084</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have a a vSphere 6 environment with SRM and vSphere replication 6.0 appliances configured.&amp;nbsp; I have followed the instruction to the mark to the best of my knowledge.&amp;nbsp; I have configured the Replication appliances with additional separate NICs dedicated to replication alone.&amp;nbsp; These separate NICs are on their own dedicated VLAN and subnet and both appliances can ping each others replication NICs (across sites).&amp;nbsp; I have been assured there are absolutely no firewalls in the way or ports blocked.&amp;nbsp; Despite this I am encountering the following problem after configuring a VM for replication on the target site ....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;VM appears to be replicating with progress bar for the initial sync however eventually I get the below error at the recovery site (despite seeing a 100% progress bar completing)...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TestVM Configuration error: Replication "TestVM" on the source site has been force-stopped&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After further examination of the datastore contents at the recovery site, I see the VM directory and stub files however the actual file sizes are 2-3KB where as the "Provisioned Size" is correct 27GB any idea's ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;TABLE cellpadding="0" cellspacing="0" style="font-family: Arial, Tahoma, Helvetica, sans-serif;"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD align="left" style="font-size: 12px;"&gt;&lt;TABLE cellpadding="0" cellspacing="0"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD align="left"&gt;&lt;P class="vami-page-label" style="font-size: 16px; color: #001100; font-weight: bold; padding-top: 5px; padding-bottom: 5px;"&gt;System Information&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD align="left" style="font-size: 12px;"&gt;&lt;TABLE cellpadding="0" cellspacing="0"&gt;&lt;TBODY&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD align="left" style="font-size: 12px;"&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD align="left" height="100%" style="font-size: 12px;" width="100%"&gt;&lt;TABLE cellpadding="0" cellspacing="0"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD align="left" height="100%" width="100%"&gt;&lt;TABLE cellpadding="0" cellspacing="0"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD align="left" width="100%"&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD align="left" height="100%" width="100%"&gt;&lt;P&gt;&lt;/P&gt;&lt;DIV class="vami-page-content"&gt;&lt;TABLE cellpadding="0" cellspacing="0" style="padding-bottom: 1px;"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD align="left"&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;Vendor:&lt;/TD&gt;&lt;TD class="vami-bold" style="font-weight: bold;"&gt;VMware, Inc.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;Appliance Name:&lt;/TD&gt;&lt;TD class="vami-bold" style="font-weight: bold;"&gt;vSphere Replication Appliance&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;Appliance Version:&lt;/TD&gt;&lt;TD class="vami-bold" style="font-weight: bold;"&gt;6.1.1.14190 Build 4595498&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 02 Aug 2017 08:21:44 GMT</pubDate>
    <dc:creator>lukeglazebrook</dc:creator>
    <dc:date>2017-08-02T08:21:44Z</dc:date>
    <item>
      <title>Deployed vSphere Replication however seem to be getting the attached unhelpful error :(</title>
      <link>https://communities.vmware.com/t5/Site-Recovery-Manager/Deployed-vSphere-Replication-however-seem-to-be-getting-the/m-p/484522#M2084</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have a a vSphere 6 environment with SRM and vSphere replication 6.0 appliances configured.&amp;nbsp; I have followed the instruction to the mark to the best of my knowledge.&amp;nbsp; I have configured the Replication appliances with additional separate NICs dedicated to replication alone.&amp;nbsp; These separate NICs are on their own dedicated VLAN and subnet and both appliances can ping each others replication NICs (across sites).&amp;nbsp; I have been assured there are absolutely no firewalls in the way or ports blocked.&amp;nbsp; Despite this I am encountering the following problem after configuring a VM for replication on the target site ....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;VM appears to be replicating with progress bar for the initial sync however eventually I get the below error at the recovery site (despite seeing a 100% progress bar completing)...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TestVM Configuration error: Replication "TestVM" on the source site has been force-stopped&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After further examination of the datastore contents at the recovery site, I see the VM directory and stub files however the actual file sizes are 2-3KB where as the "Provisioned Size" is correct 27GB any idea's ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;TABLE cellpadding="0" cellspacing="0" style="font-family: Arial, Tahoma, Helvetica, sans-serif;"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD align="left" style="font-size: 12px;"&gt;&lt;TABLE cellpadding="0" cellspacing="0"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD align="left"&gt;&lt;P class="vami-page-label" style="font-size: 16px; color: #001100; font-weight: bold; padding-top: 5px; padding-bottom: 5px;"&gt;System Information&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD align="left" style="font-size: 12px;"&gt;&lt;TABLE cellpadding="0" cellspacing="0"&gt;&lt;TBODY&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD align="left" style="font-size: 12px;"&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD align="left" height="100%" style="font-size: 12px;" width="100%"&gt;&lt;TABLE cellpadding="0" cellspacing="0"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD align="left" height="100%" width="100%"&gt;&lt;TABLE cellpadding="0" cellspacing="0"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD align="left" width="100%"&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD align="left" height="100%" width="100%"&gt;&lt;P&gt;&lt;/P&gt;&lt;DIV class="vami-page-content"&gt;&lt;TABLE cellpadding="0" cellspacing="0" style="padding-bottom: 1px;"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD align="left"&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;Vendor:&lt;/TD&gt;&lt;TD class="vami-bold" style="font-weight: bold;"&gt;VMware, Inc.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;Appliance Name:&lt;/TD&gt;&lt;TD class="vami-bold" style="font-weight: bold;"&gt;vSphere Replication Appliance&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;Appliance Version:&lt;/TD&gt;&lt;TD class="vami-bold" style="font-weight: bold;"&gt;6.1.1.14190 Build 4595498&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 02 Aug 2017 08:21:44 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Site-Recovery-Manager/Deployed-vSphere-Replication-however-seem-to-be-getting-the/m-p/484522#M2084</guid>
      <dc:creator>lukeglazebrook</dc:creator>
      <dc:date>2017-08-02T08:21:44Z</dc:date>
    </item>
    <item>
      <title>Re: Deployed vSphere Replication however seem to be getting the attached unhelpful error :(</title>
      <link>https://communities.vmware.com/t5/Site-Recovery-Manager/Deployed-vSphere-Replication-however-seem-to-be-getting-the/m-p/484523#M2085</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What do you mean when you say you configured a separate NIC separated to replication alone on the appliances? This is not a documented configuration, so far as I can see (if I am mistaken, please provide me the link). If you want to separate replication on the appliances, you should deploy out additional HBR servers for the replication.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, the ESXi hosts on the source site must also be able to reach the replication ports. Run the following commands on the host that is managing the 'TestVM'.&lt;/P&gt;&lt;P&gt;"vim-cmd vmsvc/getallvms"&lt;/P&gt;&lt;P&gt;Then note the VMID of the TestVM (it will be an integer)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then run:&lt;/P&gt;&lt;P&gt;vim-cmd hbrsvc/vmreplica.getConfig &amp;lt;VMID&amp;gt;&lt;/P&gt;&lt;P&gt;where &amp;lt;VMID&amp;gt; is replaced with the VMID you recorded above.&lt;/P&gt;&lt;P&gt;Check the Destination IP Address for the replication and ensure that your host can reach this address on port 31031. You could use the 'nc -z &amp;lt;IP Address&amp;gt; 31031' command to test the connectivity.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 02 Aug 2017 09:16:44 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Site-Recovery-Manager/Deployed-vSphere-Replication-however-seem-to-be-getting-the/m-p/484523#M2085</guid>
      <dc:creator>jameseydoyle</dc:creator>
      <dc:date>2017-08-02T09:16:44Z</dc:date>
    </item>
    <item>
      <title>Re: Deployed vSphere Replication however seem to be getting the attached unhelpful error :(</title>
      <link>https://communities.vmware.com/t5/Site-Recovery-Manager/Deployed-vSphere-Replication-however-seem-to-be-getting-the/m-p/484524#M2086</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Greg from VMware support came back on this one ....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'Arial',sans-serif;"&gt;Error: Replication "TestVM" &lt;STRONG&gt;on the source site has been force-stopped.&lt;/STRONG&gt;&lt;BR /&gt; &lt;BR /&gt; This is an issue with the hbr disks and the sync, as opposed to the configuration of the environment.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'Arial',sans-serif;"&gt;The only way to get around this is to recreate the replication for the VM from as new.&lt;BR /&gt; &lt;BR /&gt; You will need to force stop the replication to delete the replicated data and then re-configure the VM's replication.&lt;BR /&gt; &lt;BR /&gt; Make sure all target sites are authenticated under the Manage tab for vsphere Replication.&lt;BR /&gt; &lt;BR /&gt; Make sure after Force Stop the VM is removed from the incoming and outgoing tabs for the sites. &lt;BR /&gt; &lt;BR /&gt; You could also replicate the disks to a new datastore to ensure the new data does not get referenced in anyway to the old.&lt;BR /&gt; &lt;BR /&gt; &lt;SPAN style="text-decoration: underline;"&gt;SSH commands&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;You can run these commands from ssh to query the replication of a VM.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;#vim-cmd vmsvc/getallvms grep -i VMname&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;GID=&amp;gt; # vim-cmd hbrsvc/vmreplica.getConfig &lt;STRONG&gt;VMID&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;#vmreplica.getState Returns the state of replication. If there is currently a replication task in progress it will show the status of the ongoing replication.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;#vmreplica.queryReplicationState Returns the current replication state of a virtual machine and the amount of data transferred.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Aug 2017 10:00:42 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Site-Recovery-Manager/Deployed-vSphere-Replication-however-seem-to-be-getting-the/m-p/484524#M2086</guid>
      <dc:creator>lukeglazebrook</dc:creator>
      <dc:date>2017-08-04T10:00:42Z</dc:date>
    </item>
  </channel>
</rss>

