<?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: Fail Over Manager - no disk space in StoreVirtual Storage</title>
    <link>https://community.hpe.com/t5/storevirtual-storage/fail-over-manager-no-disk-space/m-p/7057181#M12094</link>
    <description>&lt;P&gt;Hi Peter,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I hope you are not having FOM on the storage cluster and saniq version and patches are on the latest.&lt;/P&gt;&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;CAUTION: Do not install the Failover Manager on a volume that is served from HP StoreVirtual&lt;/P&gt;&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;Storage, since this would defeat the purpose of the Failover Manager.&lt;/P&gt;&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;&lt;STRONG&gt;Please check, if you are using less than 15 GB of disk space for FOM.&lt;/STRONG&gt;&lt;/P&gt;&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;Minimum system requirements for using FOM with Microsoft Hyper-V Server&lt;/P&gt;&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;• Supported versions of Windows Server&lt;/P&gt;&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;◦ Windows Server 2012&lt;/P&gt;&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;◦ Windows Server 2008 R2 Standard&lt;/P&gt;&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;◦ Windows Server 2008 R2 Enterprise&lt;/P&gt;&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;◦ Windows Server 2008 R2 Datacenter&lt;/P&gt;&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;◦ Windows Server 2008 R2 Server Core&lt;/P&gt;&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;◦ Windows Server 2008 SP2, except for Core, which is not supported&lt;/P&gt;&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;• 15 GB available drive space on the Windows server for the Failover Manager&lt;/P&gt;&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;• Hyper-V role installed and running&lt;/P&gt;&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;• At least 1 GB of memory reserved for the Failover Manager&lt;/P&gt;&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;• Two virtual CPUs with at least 2000 MHz reserved&lt;/P&gt;&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;There is not much space that can be recalimed from deleting FOM logs.&lt;/P&gt;&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;Even it is not suggested, as in case of storage down situations FOM logs are the best logs which can tell story of both storage nodes simultaneously.&lt;/P&gt;&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;Thanks and Regards,&lt;/P&gt;&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;Rahul Gupta&lt;/P&gt;&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;Technical Solutions Consultant&lt;/P&gt;&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;Simplivity/Storevirtual Team&lt;/P&gt;&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 01 Aug 2019 11:54:57 GMT</pubDate>
    <dc:creator>RahulGupta1</dc:creator>
    <dc:date>2019-08-01T11:54:57Z</dc:date>
    <item>
      <title>Fail Over Manager - no disk space</title>
      <link>https://community.hpe.com/t5/storevirtual-storage/fail-over-manager-no-disk-space/m-p/7057165#M12093</link>
      <description>&lt;P&gt;&lt;FONT&gt;Hello,&lt;BR /&gt;we have two 4730 Store Virtual with a Fail Over Manager, which runs as a Hyper-V machine on a windows server.&lt;BR /&gt;Now Hyper-V reports that the Fail Over Manager has too little disk space and stops the FOM.&lt;BR /&gt;How can I delete logs I don't need in FOM to get more disk space?&amp;nbsp; &lt;/FONT&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 01 Aug 2019 10:09:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storevirtual-storage/fail-over-manager-no-disk-space/m-p/7057165#M12093</guid>
      <dc:creator>Peterschwarzz</dc:creator>
      <dc:date>2019-08-01T10:09:12Z</dc:date>
    </item>
    <item>
      <title>Re: Fail Over Manager - no disk space</title>
      <link>https://community.hpe.com/t5/storevirtual-storage/fail-over-manager-no-disk-space/m-p/7057181#M12094</link>
      <description>&lt;P&gt;Hi Peter,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I hope you are not having FOM on the storage cluster and saniq version and patches are on the latest.&lt;/P&gt;&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;CAUTION: Do not install the Failover Manager on a volume that is served from HP StoreVirtual&lt;/P&gt;&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;Storage, since this would defeat the purpose of the Failover Manager.&lt;/P&gt;&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;&lt;STRONG&gt;Please check, if you are using less than 15 GB of disk space for FOM.&lt;/STRONG&gt;&lt;/P&gt;&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;Minimum system requirements for using FOM with Microsoft Hyper-V Server&lt;/P&gt;&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;• Supported versions of Windows Server&lt;/P&gt;&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;◦ Windows Server 2012&lt;/P&gt;&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;◦ Windows Server 2008 R2 Standard&lt;/P&gt;&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;◦ Windows Server 2008 R2 Enterprise&lt;/P&gt;&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;◦ Windows Server 2008 R2 Datacenter&lt;/P&gt;&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;◦ Windows Server 2008 R2 Server Core&lt;/P&gt;&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;◦ Windows Server 2008 SP2, except for Core, which is not supported&lt;/P&gt;&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;• 15 GB available drive space on the Windows server for the Failover Manager&lt;/P&gt;&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;• Hyper-V role installed and running&lt;/P&gt;&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;• At least 1 GB of memory reserved for the Failover Manager&lt;/P&gt;&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;• Two virtual CPUs with at least 2000 MHz reserved&lt;/P&gt;&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;There is not much space that can be recalimed from deleting FOM logs.&lt;/P&gt;&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;Even it is not suggested, as in case of storage down situations FOM logs are the best logs which can tell story of both storage nodes simultaneously.&lt;/P&gt;&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;Thanks and Regards,&lt;/P&gt;&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;Rahul Gupta&lt;/P&gt;&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;Technical Solutions Consultant&lt;/P&gt;&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;Simplivity/Storevirtual Team&lt;/P&gt;&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;"&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 01 Aug 2019 11:54:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storevirtual-storage/fail-over-manager-no-disk-space/m-p/7057181#M12094</guid>
      <dc:creator>RahulGupta1</dc:creator>
      <dc:date>2019-08-01T11:54:57Z</dc:date>
    </item>
    <item>
      <title>Re: Fail Over Manager - no disk space</title>
      <link>https://community.hpe.com/t5/storevirtual-storage/fail-over-manager-no-disk-space/m-p/7057269#M12095</link>
      <description>&lt;P&gt;It wasn't the size of the FOM disk but the size of the partition of the Hyper-V host. I cleaned up the Windows partition and the FOM could be started again.&lt;/P&gt;&lt;P&gt;Sorry for that&lt;/P&gt;</description>
      <pubDate>Fri, 02 Aug 2019 08:50:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storevirtual-storage/fail-over-manager-no-disk-space/m-p/7057269#M12095</guid>
      <dc:creator>Peterschwarzz</dc:creator>
      <dc:date>2019-08-02T08:50:52Z</dc:date>
    </item>
  </channel>
</rss>

