<?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 Relocating Microsoft Cluster Quorum using SnapMirror in Data Protection</title>
    <link>https://community.netapp.com/t5/Data-Protection/Relocating-Microsoft-Cluster-Quorum-using-SnapMirror/m-p/30005#M9999</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This weekend we are relocating all our LUN volumes on our filer to new disks using SnapMirror and will be maintaining the same drive signatures.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have a couple of Microsoft cluster servers and I'll be stopping the microsoft cluster services beforehand, I assume I just need to disconnect the existing drives and reconnect them through SnapDrive. The only trepidation I have is with the quorum, if the Microsoft Cluster service is stopped is there anything special I need to consider in terms of SnapDrive to disconnect and then reconnect the quorum drive? I realise SnapDrive is cluster aware, I just want to make sure the steps I go through will be correct and not cause any problems.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 05 Jun 2025 07:23:20 GMT</pubDate>
    <dc:creator>woodwarg07</dc:creator>
    <dc:date>2025-06-05T07:23:20Z</dc:date>
    <item>
      <title>Relocating Microsoft Cluster Quorum using SnapMirror</title>
      <link>https://community.netapp.com/t5/Data-Protection/Relocating-Microsoft-Cluster-Quorum-using-SnapMirror/m-p/30005#M9999</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This weekend we are relocating all our LUN volumes on our filer to new disks using SnapMirror and will be maintaining the same drive signatures.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have a couple of Microsoft cluster servers and I'll be stopping the microsoft cluster services beforehand, I assume I just need to disconnect the existing drives and reconnect them through SnapDrive. The only trepidation I have is with the quorum, if the Microsoft Cluster service is stopped is there anything special I need to consider in terms of SnapDrive to disconnect and then reconnect the quorum drive? I realise SnapDrive is cluster aware, I just want to make sure the steps I go through will be correct and not cause any problems.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 07:23:20 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/Relocating-Microsoft-Cluster-Quorum-using-SnapMirror/m-p/30005#M9999</guid>
      <dc:creator>woodwarg07</dc:creator>
      <dc:date>2025-06-05T07:23:20Z</dc:date>
    </item>
    <item>
      <title>Re: Relocating Microsoft Cluster Quorum using SnapMirror</title>
      <link>https://community.netapp.com/t5/Data-Protection/Relocating-Microsoft-Cluster-Quorum-using-SnapMirror/m-p/30010#M10000</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;STRONG&gt;Create and move Quorum to a Temp Location&lt;/STRONG&gt;&lt;STRONG&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;UL&gt;&lt;LI&gt;Create a new 500 MB lun to be the temp location for the Quorum resource &lt;UL&gt;&lt;LI&gt;Place it in the same group that contains the current quorum &lt;/LI&gt;&lt;LI&gt;Make a note of the drive letter used (X: in this example)&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;Open the cluster administrator on the active node &lt;UL&gt;&lt;LI&gt;Expand the cluster group and verify the new disk is in this group.&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;Right click on the cluster name in the upper left hand pane and choose "properties" &lt;/LI&gt;&lt;LI&gt;Click the "Quorum" tab &lt;/LI&gt;&lt;LI&gt;In the Quorum Resource drop down choose the new temp location (Disk X: in this example) &lt;/LI&gt;&lt;LI&gt;Go back to the group containing the Quorum resource and take offline the Microsoft Distributed Transaction Coordinator (MSDTC) service. &lt;/LI&gt;&lt;LI&gt;Once the MSDTC resource is offline, delete the MSDTC resource&lt;/LI&gt;&lt;/UL&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN&gt;&lt;STRONG&gt;Free Up the Original Quorum Drive Letter&lt;/STRONG&gt;&lt;UL&gt;&lt;LI&gt;&lt;/LI&gt;&lt;LI&gt;Back in cluster administrator offline then delete the Q: disk resource (If you missed a step trying to offline the disk will produce errors)&lt;/LI&gt;&lt;/UL&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Create and move Quorum to new final location&lt;/STRONG&gt;&lt;BR /&gt;&lt;SPAN&gt;&lt;SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;UL&gt;&lt;LI&gt;&lt;/LI&gt;&lt;LI&gt;Open the cluster administrator on the active node &lt;UL&gt;&lt;LI&gt; Expand the cluster group and verify the new disk is in this group.&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;Right click on the cluster name in the upper left hand pane and choose "properties" &lt;/LI&gt;&lt;LI&gt;Click the "Quorum" tab &lt;/LI&gt;&lt;LI&gt;In the Quorum Resource drop down choose the new location (Disk Q: in this example)&lt;/LI&gt;&lt;/UL&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Remove the Temp Quorum LUN &amp;amp;Reinstall &lt;/STRONG&gt;&lt;STRONG&gt;MSDTC&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;In cluster Administrator, open the group containing the quorum and take offline then delete the temp Quorum disk (X: for this example) &lt;/LI&gt;&lt;LI&gt;Starting with the active node, open a CLI and type "msdtc -uninstall" then "msdtc -install" &lt;/LI&gt;&lt;LI&gt;Repeat this step for each passive node. &lt;/LI&gt;&lt;LI&gt;In cluster administrator the MSDTC resource should automatically appear &lt;/LI&gt;&lt;LI&gt;Check the properties of the MSDTC service and verify the dependency is on the cluster name and the Quorum disk, should be Q: &lt;/LI&gt;&lt;LI&gt;Online the MSDTC resource&lt;STRONG&gt;Testing and Clean-up&lt;/STRONG&gt;&lt;SPAN&gt;&lt;SPAN&gt;&lt;UL&gt;&lt;LI&gt;&lt;/LI&gt;&lt;LI&gt;Using SnapDrive or your other storage management tools remove/unmask the LUNs that are no longer needed. &lt;UL&gt;&lt;LI&gt;In the example here it would be the R:\ and X:\ drives &lt;/LI&gt;&lt;LI&gt;If you make a mistake here or this process takes your cluster down just remap all the luns used for this process and then troubleshoot accordingly.&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;Move the group containing the Quorum to each of the passive nodes and then back to the "active" node. &lt;UL&gt;&lt;LI&gt;If this process completes the quorum and MSDTC service are working properly.&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;Create another new 500 MB LUN to be the final location for the quorum resource. &lt;UL&gt;&lt;LI&gt;Place it in the same group that contains the current (but temporary) quorum resource &lt;/LI&gt;&lt;LI&gt;You should now be able to use the original drive letter, Q: for the sake of this demonstration.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;Using disk administrator change the drive letter of the original quorum drive (Q: in this example) to something else, lets use R:&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 07 Oct 2009 07:12:14 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/Relocating-Microsoft-Cluster-Quorum-using-SnapMirror/m-p/30010#M10000</guid>
      <dc:creator>sourav</dc:creator>
      <dc:date>2009-10-07T07:12:14Z</dc:date>
    </item>
  </channel>
</rss>

