<?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 Re: problem between 3par and srm in HPE 3PAR StoreServ Storage</title>
    <link>https://community.hpe.com/t5/hpe-3par-storeserv-storage/problem-between-3par-and-srm/m-p/7073681#M5490</link>
    <description>&lt;P&gt;Hello did you ever get this resolved ?&amp;nbsp;&lt;BR /&gt;We are also encourtering the same issue.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 20 Dec 2019 22:58:28 GMT</pubDate>
    <dc:creator>cititechs</dc:creator>
    <dc:date>2019-12-20T22:58:28Z</dc:date>
    <item>
      <title>problem between 3par and srm</title>
      <link>https://community.hpe.com/t5/hpe-3par-storeserv-storage/problem-between-3par-and-srm/m-p/7071098#M5459</link>
      <description>&lt;P&gt;Hello,&lt;BR /&gt;I have problem with SRM and two 3par.&lt;BR /&gt;my environment is configured in the following way:&lt;/P&gt;&lt;P&gt;protected site&lt;BR /&gt;a 3par 7200 (HPE 3PAR OS version Current 3.2.2.709 (MU6) + P99, P107, P119, P131, P135, P138, P139, P140, P149)&lt;BR /&gt;VMware-srm-va-8.2.0.3658-14761906&lt;BR /&gt;VMWare-vSphere_Replication-8.2.0-14761900&lt;BR /&gt;SRA version HPE3PARSRA_8.2.0.26.zip&lt;BR /&gt;Vcenter in vcsa 6.5.0 build 14836121 format&lt;BR /&gt;esxi 6.5.0 build 14990892&lt;/P&gt;&lt;P&gt;recovery site&lt;BR /&gt;a 3par 8200 (3.3.1.460 (MU3) + P49, P50, P53)&lt;BR /&gt;VMware-srm-va-8.2.0.3658-14761906&lt;BR /&gt;VMWare-vSphere_Replication-8.2.0-14761900&lt;BR /&gt;SRA version HPE3PARSRA_8.2.0.26.zip&lt;BR /&gt;Vcenter in vcsa 6.5.0 build 14836121 format&lt;BR /&gt;esxi 6.5.0 build 14990892&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;The 3par are in periodic sync replication&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;I created a recovery group on the 3par containing a lun with a vm. The vm is called testdr.&lt;BR /&gt;This recovery group was created to perform a test with srm.&lt;BR /&gt;I created a protection group that contains vm testdr and I created a recovery plan that contains only this vm.&lt;BR /&gt;First I tried to test the recovery plan and returned the following error:&lt;BR /&gt;Error- Failed to create snapshots of replica devices. Failed to create snapshot of replica consistency group DR-TEST.r38093. SRA command 'testFailoverStart' failed for consistency group 'DR-TEST.r38093'. Secondary volume &amp;lt;DR-TEST.r&amp;gt; is not exported to any host.&lt;/P&gt;&lt;P&gt;Please manually export the secondary volumes to corresponding host(s).&lt;/P&gt;&lt;P&gt;I solved the problem by exporting the lun to the revovery site.&lt;BR /&gt;In fact, I re-launched the test and it went well.&lt;BR /&gt;At this point I tried to do a recovery. I did a planned migration with storages synchronization.&lt;BR /&gt;The recovery plan is not successful and he reports the following error:&lt;BR /&gt;ERROR&lt;BR /&gt;Operation Failed Failed to demote source consistency group 'DR-TEST'. SRA command 'prepareFailover' failed for consistency group 'DR-TEST'. Unable to execute PrepareFailover command workflow. Additional information: [Errno 13] Permission denied: '/srm/sra/conf/data/rcgroupinfo_38093.xml' If the error is caused due to remote copy link down, you need to bring up the remote copy link and retry the operation. If the error is due to unexpected remote copy replication roles or group state, you need to check with your storage administrator for assistance. If the error is related to the network issue, you need to check if you have problem with your network connection.&lt;/P&gt;&lt;P&gt;I was looking on the internet to find a similar error in hpe&lt;BR /&gt;&lt;A href="https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00068960en_us&amp;amp;docLocale=en_US" target="_blank"&gt;https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00068960en_us&amp;amp;docLocale=en_US&lt;/A&gt;&lt;BR /&gt;which is solved using the SRA version 6.5.6 which I cannot use.&lt;BR /&gt;Alternatively by reading the HPE 3PAR Storage Replication Adapter for 8.2.0 VMware® vCenter Guide Site Recovery Manager ™ User Guide it is stated that SRA parameters can be modified using the TpdSrm.exe command.&lt;BR /&gt;Unfortunately from what I understand this command is present only with SRA in windows version so I can't do anything.&lt;BR /&gt;Do you have any idea how to solve my problem?&lt;BR /&gt;How can I eliminate the recovery plan that is currently in an incomplete recovery state?&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Wed, 27 Nov 2019 11:20:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-3par-storeserv-storage/problem-between-3par-and-srm/m-p/7071098#M5459</guid>
      <dc:creator>Pazzoide1976</dc:creator>
      <dc:date>2019-11-27T11:20:48Z</dc:date>
    </item>
    <item>
      <title>Re: problem between 3par and srm</title>
      <link>https://community.hpe.com/t5/hpe-3par-storeserv-storage/problem-between-3par-and-srm/m-p/7073681#M5490</link>
      <description>&lt;P&gt;Hello did you ever get this resolved ?&amp;nbsp;&lt;BR /&gt;We are also encourtering the same issue.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 20 Dec 2019 22:58:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-3par-storeserv-storage/problem-between-3par-and-srm/m-p/7073681#M5490</guid>
      <dc:creator>cititechs</dc:creator>
      <dc:date>2019-12-20T22:58:28Z</dc:date>
    </item>
    <item>
      <title>Re: problem between 3par and srm</title>
      <link>https://community.hpe.com/t5/hpe-3par-storeserv-storage/problem-between-3par-and-srm/m-p/7074388#M5506</link>
      <description>&lt;DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;PRE&gt;&lt;SPAN&gt;Hello,
I solved it by opening a call in hpe.
It's a permission problem related to the 3par SRA.
Internally in HPE the problem is known.

Regards&lt;/SPAN&gt;&lt;/PRE&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Tue, 31 Dec 2019 09:35:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-3par-storeserv-storage/problem-between-3par-and-srm/m-p/7074388#M5506</guid>
      <dc:creator>Pazzoide1976</dc:creator>
      <dc:date>2019-12-31T09:35:09Z</dc:date>
    </item>
  </channel>
</rss>

