<?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: srm vm appliance and 3par sra in Site Recovery Manager Discussions</title>
    <link>https://communities.vmware.com/t5/Site-Recovery-Manager/srm-vm-appliance-and-3par-sra/m-p/2843198#M13812</link>
    <description>&lt;P&gt;I recommend working with HP on this&lt;/P&gt;</description>
    <pubDate>Wed, 21 Apr 2021 23:42:21 GMT</pubDate>
    <dc:creator>vbrowncoat</dc:creator>
    <dc:date>2021-04-21T23:42:21Z</dc:date>
    <item>
      <title>srm vm appliance and 3par sra</title>
      <link>https://communities.vmware.com/t5/Site-Recovery-Manager/srm-vm-appliance-and-3par-sra/m-p/2840474#M13790</link>
      <description>&lt;P&gt;&lt;SPAN&gt;While I am adding the storage array pairs to the SRM, i am getting below error.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;"SRA command 'discoverArrays' failed. Unable to connect to HPE Storage system &amp;lt;IP Address &amp;gt;. Make sure you have entered the correct address for HPE Storage system, storage system is up and running, and WSAPI server is started on the storage system and check if there is any problem with your network connection."&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;wsapi is already enabled and&amp;nbsp;It seems i am hitting this issue -&amp;nbsp;&lt;A href="https://kb.vmware.com/s/article/2149830" target="_blank"&gt;https://kb.vmware.com/s/article/2149830&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;SRM vm appliance is used, and array SRA is already deployed. TPDsrm seems to be the binary used only for a windows SRM, any idea what's the binary used for SRM vm appliance ?&lt;/P&gt;</description>
      <pubDate>Wed, 07 Apr 2021 17:48:29 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Site-Recovery-Manager/srm-vm-appliance-and-3par-sra/m-p/2840474#M13790</guid>
      <dc:creator>hp_avik2401</dc:creator>
      <dc:date>2021-04-07T17:48:29Z</dc:date>
    </item>
    <item>
      <title>Re: srm vm appliance and 3par sra</title>
      <link>https://communities.vmware.com/t5/Site-Recovery-Manager/srm-vm-appliance-and-3par-sra/m-p/2843198#M13812</link>
      <description>&lt;P&gt;I recommend working with HP on this&lt;/P&gt;</description>
      <pubDate>Wed, 21 Apr 2021 23:42:21 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Site-Recovery-Manager/srm-vm-appliance-and-3par-sra/m-p/2843198#M13812</guid>
      <dc:creator>vbrowncoat</dc:creator>
      <dc:date>2021-04-21T23:42:21Z</dc:date>
    </item>
    <item>
      <title>Re: srm vm appliance and 3par sra</title>
      <link>https://communities.vmware.com/t5/Site-Recovery-Manager/srm-vm-appliance-and-3par-sra/m-p/2843286#M13816</link>
      <description>&lt;P&gt;thanks. it was due to the name resolution issue for the srm appliance...it had an incorrect entry in their dns server.&lt;/P&gt;</description>
      <pubDate>Thu, 22 Apr 2021 11:16:23 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Site-Recovery-Manager/srm-vm-appliance-and-3par-sra/m-p/2843286#M13816</guid>
      <dc:creator>hp_avik2401</dc:creator>
      <dc:date>2021-04-22T11:16:23Z</dc:date>
    </item>
  </channel>
</rss>

