<?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 Heartbeat (Linux HA) and NetApp? in Data Protection</title>
    <link>https://community.netapp.com/t5/Data-Protection/Heartbeat-Linux-HA-and-NetApp/m-p/14405#M9519</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV class="post-text"&gt;&lt;P&gt;Does anyone have any experience setting up a high&amp;nbsp; availability two node Linux cluster using heartbeat (linux-ha.org) and&amp;nbsp; NetApp storage (preferably using SnapDrive for Linux)?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Basically I would like to mount the same NetApp LUN over Fibre&amp;nbsp; Channel to two servers in an Active/Passive mode (only one server can&amp;nbsp; access the LUN at a time)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If so, is there a How-To document or at least a list of things to watch out for?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 05 Jun 2025 07:16:55 GMT</pubDate>
    <dc:creator>drew_kutchar</dc:creator>
    <dc:date>2025-06-05T07:16:55Z</dc:date>
    <item>
      <title>Heartbeat (Linux HA) and NetApp?</title>
      <link>https://community.netapp.com/t5/Data-Protection/Heartbeat-Linux-HA-and-NetApp/m-p/14405#M9519</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV class="post-text"&gt;&lt;P&gt;Does anyone have any experience setting up a high&amp;nbsp; availability two node Linux cluster using heartbeat (linux-ha.org) and&amp;nbsp; NetApp storage (preferably using SnapDrive for Linux)?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Basically I would like to mount the same NetApp LUN over Fibre&amp;nbsp; Channel to two servers in an Active/Passive mode (only one server can&amp;nbsp; access the LUN at a time)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If so, is there a How-To document or at least a list of things to watch out for?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 07:16:55 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/Heartbeat-Linux-HA-and-NetApp/m-p/14405#M9519</guid>
      <dc:creator>drew_kutchar</dc:creator>
      <dc:date>2025-06-05T07:16:55Z</dc:date>
    </item>
    <item>
      <title>Re: Heartbeat (Linux HA) and NetApp?</title>
      <link>https://community.netapp.com/t5/Data-Protection/Heartbeat-Linux-HA-and-NetApp/m-p/14410#M9520</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;For DataFabric Manager, we used Veritas to cluster 2 Linux hosts.&lt;/P&gt;&lt;P&gt;I used SnapDrive to create the LUN from one host, &amp;amp; then from another host issued a connect command.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;From my experience I can list a few of the points to take care of&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Basically if an application needs to be accessing the shared disk, then&lt;/P&gt;&lt;P&gt;1. Disable automatic startup of application during reboot on both the hosts&lt;/P&gt;&lt;P&gt;2. At any point only one host must be accessing the shared disk, so that data is not getting corrupted&lt;/P&gt;&lt;P&gt;You set the cluster server software to mount the shared disk on only one host at a time.&lt;/P&gt;&lt;P&gt;3. And before the application service is started, the DiskGroup &amp;amp; logical Volume must be enabled &amp;amp; disk mounted.&lt;/P&gt;&lt;P&gt;You can create a dependency tree, using cluster software.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 19 Mar 2010 03:49:08 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/Heartbeat-Linux-HA-and-NetApp/m-p/14410#M9520</guid>
      <dc:creator>prasads</dc:creator>
      <dc:date>2010-03-19T03:49:08Z</dc:date>
    </item>
  </channel>
</rss>

