<?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: Disaster Recovery Simplivity in HPE SimpliVity</title>
    <link>https://community.hpe.com/t5/hpe-simplivity/disaster-recovery-simplivity/m-p/7077425#M1200</link>
    <description>&lt;P&gt;The svtcli password is used for situations where VC is not available and is really only intended as an emergency access not all commands will run in the absence of not being able to reach VC.&lt;/P&gt;&lt;P&gt;As VC is down all vms can be restored including VC with the&amp;nbsp; svt-backup-restore command using the --emergency switch.&lt;/P&gt;&lt;P&gt;it is a cli operation and it would be a slow process in comparision to the GUI option&amp;nbsp; &amp;nbsp;and needs additional information&amp;nbsp; like datastore and VM name or GUID&amp;nbsp; to restore every VM.&lt;/P&gt;&lt;P&gt;It would be best in DR situation to restore the VC using the --emergency switch ,there after you should be able to use the GUI to complete the rest of the VMs (tip practice&amp;nbsp; a few backup restores of VC on the DR site and keep a note&amp;nbsp; of cli commands used to restore the VC&amp;nbsp; &amp;nbsp;this will speed up any real world DR senario also avoid having VC machine using a distributed virtual switch that it manages ).&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is it intended to run the VC on simplivity.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 30 Jan 2020 10:24:53 GMT</pubDate>
    <dc:creator>DaveOb</dc:creator>
    <dc:date>2020-01-30T10:24:53Z</dc:date>
    <item>
      <title>Disaster Recovery Simplivity</title>
      <link>https://community.hpe.com/t5/hpe-simplivity/disaster-recovery-simplivity/m-p/7077415#M1198</link>
      <description>&lt;P&gt;Helo I have this&lt;/P&gt;&lt;P&gt;Data Center &lt;STRONG&gt;DEMO&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Two Cluster&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;CLUSTER MAIN&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;4X HPE SimpliVity 325 Gen10 Node&lt;/P&gt;&lt;P&gt;Vcenter run over this cluster&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;CLUSTER DR&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;2X HPE SimpliVity 325 Gen10 Node&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We make backup with simplivity the VM Cluster Main to Cluster DR every 1h&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Questions:&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;1.&amp;nbsp;&lt;/STRONG&gt; Is it possible recover Vcenter backup simplivity in Cluster DR if the Cluster Main is down?&lt;/P&gt;&lt;P&gt;I try a demo, simulate down the cluster Main, after connect ssh to OVC on Esx over Cluster DR with user&amp;nbsp;&lt;SPAN&gt;&lt;STRONG&gt;svtcli&lt;/STRONG&gt; and password &lt;STRONG&gt;Simplicity,&amp;nbsp;&lt;/STRONG&gt;but i can't run command because need connect to Vcenter.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Other test was: with Veeam Backup, we make replicate vcenter every 10 min to cluster DR. , but whe down the cluster main, and run manually the vcenter_replicate, the plugins HPE simplivity is loading.....&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;too connect to ssh to OVC any commnad is lock.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;STRONG&gt;2.&lt;/STRONG&gt; What is it the step correct for make a disaster recovery with simplivity if you have a vcenter on cluster main?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Best Regards!&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 30 Jan 2020 08:49:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-simplivity/disaster-recovery-simplivity/m-p/7077415#M1198</guid>
      <dc:creator>Elfegume</dc:creator>
      <dc:date>2020-01-30T08:49:47Z</dc:date>
    </item>
    <item>
      <title>Re: Disaster Recovery Simplivity</title>
      <link>https://community.hpe.com/t5/hpe-simplivity/disaster-recovery-simplivity/m-p/7077425#M1200</link>
      <description>&lt;P&gt;The svtcli password is used for situations where VC is not available and is really only intended as an emergency access not all commands will run in the absence of not being able to reach VC.&lt;/P&gt;&lt;P&gt;As VC is down all vms can be restored including VC with the&amp;nbsp; svt-backup-restore command using the --emergency switch.&lt;/P&gt;&lt;P&gt;it is a cli operation and it would be a slow process in comparision to the GUI option&amp;nbsp; &amp;nbsp;and needs additional information&amp;nbsp; like datastore and VM name or GUID&amp;nbsp; to restore every VM.&lt;/P&gt;&lt;P&gt;It would be best in DR situation to restore the VC using the --emergency switch ,there after you should be able to use the GUI to complete the rest of the VMs (tip practice&amp;nbsp; a few backup restores of VC on the DR site and keep a note&amp;nbsp; of cli commands used to restore the VC&amp;nbsp; &amp;nbsp;this will speed up any real world DR senario also avoid having VC machine using a distributed virtual switch that it manages ).&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is it intended to run the VC on simplivity.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 30 Jan 2020 10:24:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-simplivity/disaster-recovery-simplivity/m-p/7077425#M1200</guid>
      <dc:creator>DaveOb</dc:creator>
      <dc:date>2020-01-30T10:24:53Z</dc:date>
    </item>
  </channel>
</rss>

