<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://msmvps.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Cluster Help : Storage Area Network</title><link>http://msmvps.com/blogs/clusterhelp/archive/tags/Storage+Area+Network/default.aspx</link><description>Tags: Storage Area Network</description><dc:language>en</dc:language><generator>CommunityServer 2008.5 SP2 (Build: 40407.4157)</generator><item><title>Which Exchange Server 2007 Server Cluster Type Should I use, CCR or SCC?</title><link>http://msmvps.com/blogs/clusterhelp/archive/2007/10/31/which-exchange-server-2007-server-cluster-type-should-i-use-ccr-or-scc.aspx</link><pubDate>Wed, 31 Oct 2007 19:36:00 GMT</pubDate><guid isPermaLink="false">d67277c4-116b-43f1-b688-e9ef184ea916:1275915</guid><dc:creator>cluster</dc:creator><slash:comments>0</slash:comments><description>This is becoming a pretty common question in my Exchange classes. Which should I use? Why one over the other? My current recommendation is to use CCR whenever possible vs. SCC. Why? I am glad you asked that question. High Availability, see my definition...(&lt;a href="http://msmvps.com/blogs/clusterhelp/archive/2007/10/31/which-exchange-server-2007-server-cluster-type-should-i-use-ccr-or-scc.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://msmvps.com/aggbug.aspx?PostID=1275915" width="1" height="1"&gt;</description><category domain="http://msmvps.com/blogs/clusterhelp/archive/tags/Exchange/default.aspx">Exchange</category><category domain="http://msmvps.com/blogs/clusterhelp/archive/tags/Storage+Area+Network/default.aspx">Storage Area Network</category></item><item><title>Moving a Cluster to a New SAN - Original Posted Jul 22, 2005</title><link>http://msmvps.com/blogs/clusterhelp/archive/2005/08/05/moving-a-cluster-to-a-new-san-original-posted-jul-22-2005.aspx</link><pubDate>Fri, 05 Aug 2005 13:14:00 GMT</pubDate><guid isPermaLink="false">d67277c4-116b-43f1-b688-e9ef184ea916:61741</guid><dc:creator>cluster</dc:creator><slash:comments>1</slash:comments><description>&lt;div&gt;&lt;font size="3"&gt;A fairly common scenario for a cluster administrator is to move a cluster from one SAN to another as SAN equipment is replaced with newer/faster SANs or the old SAN&amp;#39;s lease is up and a new one is being brought in.&lt;/font&gt;&lt;/div&gt;
&lt;div&gt;&lt;font size="3"&gt;&lt;/font&gt;&amp;nbsp;&lt;/div&gt;
&lt;div&gt;&lt;font size="3"&gt;The easiest way that I have found to do this is to use these steps (this is from memory, let me know if I missed one or two):&lt;/font&gt;&lt;/div&gt;
&lt;div&gt;&lt;font size="3"&gt;&lt;/font&gt;&amp;nbsp;&lt;/div&gt;
&lt;div&gt;&lt;font size="3"&gt;Super High Level Steps:&lt;/font&gt;&lt;/div&gt;
&lt;ol&gt;
&lt;li&gt;&lt;font size="3"&gt;Put the new array in the same fabric as the existing array&lt;/font&gt; 
&lt;li&gt;&lt;font size="3"&gt;Create new LUNs on the new array and make sure they are visible to the nodes&lt;/font&gt; 
&lt;li&gt;&lt;font size="3"&gt;Map the new LUNs to the old drive letters&lt;/font&gt; 
&lt;li&gt;&lt;font size="3"&gt;Copy data from the old drive to the new drive&lt;/font&gt; 
&lt;li&gt;&lt;font size="3"&gt;Move quorum and MSDTC&lt;/font&gt;&lt;/li&gt;&lt;/ol&gt;
&lt;div&gt;&lt;font size="3"&gt;Slightly More Detailed Steps:&lt;/font&gt;&lt;/div&gt;
&lt;ol&gt;
&lt;li&gt;&lt;font size="3"&gt;Carve the new LUNs on the new array&lt;/font&gt; 
&lt;li&gt;&lt;font size="3"&gt;Add the new array and its LUNs to the same switch as the existing array&lt;/font&gt; 
&lt;li&gt;&lt;font size="3"&gt;Configure the LUN masking on the switch to expose the new LUNs to NodeA and NodeB&lt;/font&gt; 
&lt;li&gt;&lt;font size="3"&gt;Use the disk management tools in Windows to rescan the drives&lt;/font&gt; 
&lt;li&gt;&lt;font size="3"&gt;Use the active node to partition and format the disks&lt;/font&gt; 
&lt;li&gt;&lt;font size="3"&gt;Use Cluster Administrtor to create the new physical disk resources and put them into their proper cluster groups&lt;/font&gt; 
&lt;li&gt;&lt;font size="3"&gt;Move the Quorum using the GUI to a temp location&lt;/font&gt; 
&lt;ol&gt;
&lt;li&gt;&lt;font size="3"&gt;In Cluster Administrator, right click the cluster name&lt;/font&gt; 
&lt;li&gt;&lt;font size="3"&gt;Select Properties&lt;/font&gt; 
&lt;li&gt;&lt;font size="3"&gt;Select the Quorum tab&lt;/font&gt; 
&lt;li&gt;&lt;font size="3"&gt;Use the drop down box to select a temp location for the quorum &lt;/font&gt;&lt;/li&gt;&lt;/ol&gt;
&lt;li&gt;&lt;font size="3"&gt;Delete the existing MSDTC folder (if any)&lt;/font&gt; 
&lt;ol&gt;
&lt;li&gt;&lt;font size="3"&gt;Stop the MSDTC resource &lt;/font&gt;
&lt;li&gt;&lt;font size="3"&gt;Copy the MSDTC folder from Q: to the final qurom disk target location &lt;/font&gt;
&lt;li&gt;&lt;font size="3"&gt;Stop&amp;nbsp;the Q: resource (remember, the quorum isn&amp;#39;t there anymore) &lt;/font&gt;
&lt;li&gt;&lt;font size="3"&gt;Delete the MSDTC resource &lt;/font&gt;&lt;/li&gt;&lt;/ol&gt;
&lt;li&gt;&lt;font size="3"&gt;Move the quorum to its final location&lt;/font&gt; 
&lt;ol&gt;
&lt;li&gt;&lt;font size="3"&gt;Go into disk management and change the Q: name to another letter&lt;/font&gt; 
&lt;li&gt;&lt;font size="3"&gt;Use disk management and name the final quorum drive to Q:&lt;/font&gt; 
&lt;li&gt;&lt;font size="3"&gt;Repeat steps 7.1-7.4 to move the quorum to its final destination&lt;/font&gt;&lt;/li&gt;&lt;/ol&gt;
&lt;li&gt;&lt;font size="3"&gt;Recreate the MSDTC resource&lt;/font&gt; 
&lt;ol&gt;
&lt;li&gt;&lt;font size="3"&gt;Create a new MSDTC resource with the clustername network name resource&amp;nbsp;and the new Q: as dependencies &lt;/font&gt;
&lt;li&gt;&lt;font size="3"&gt;Bring the MSDTC resource online&lt;/font&gt;&lt;/li&gt;&lt;/ol&gt;
&lt;li&gt;&lt;font size="3"&gt;Stop the cluster service and the application cluster groups (you can just stop the application resources if you want to move app data an app at a time) &lt;/font&gt;
&lt;li&gt;&lt;font size="3"&gt;Move the data from the old disks to the new ones&lt;/font&gt; 
&lt;li&gt;&lt;font size="3"&gt;Re-letter the old disks to something outside the current range, but do not remove them yet - you might need to use them in your back out plan&lt;/font&gt; 
&lt;li&gt;&lt;font size="3"&gt;Re-letter the new disks to the same drive letter as the old ones (no, you do not have to worry about disk signatures as applications don&amp;#39;t understand disk signatures and don&amp;#39;t care about anything other than drive letters)&lt;/font&gt; 
&lt;li&gt;Verify that all dependent resources are pointing to the proper physical disk resource. 
&lt;li&gt;&lt;font size="3"&gt;Restart the cluster service&lt;/font&gt; 
&lt;li&gt;&lt;font size="3"&gt;Make sure the new drive letters and disk resources are showing up properly in cluster administrator&lt;/font&gt; 
&lt;li&gt;&lt;font size="3"&gt;Bring everything back online&lt;/font&gt;&lt;/li&gt;&lt;/ol&gt;
&lt;p&gt;&lt;font size="3"&gt;Again, these are basic steps. Some of the individual steps will require lots of work. I have done this now several times and am very happy with the results.&lt;/font&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://msmvps.com/aggbug.aspx?PostID=61741" width="1" height="1"&gt;</description><category domain="http://msmvps.com/blogs/clusterhelp/archive/tags/Storage+Area+Network/default.aspx">Storage Area Network</category></item></channel></rss>