<?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 Moving SAN Drives in MSA Storage</title>
    <link>https://community.hpe.com/t5/msa-storage/moving-san-drives/m-p/914807#M3757</link>
    <description>I'm replacing my existing Windows 2003 Adv. cluster with a new cluster running Windows 2003 Adv. R2.  I built the 2nd cluster and it functions fine.  Now I want to unpresent the data drives from the old cluster and reattach them to the new cluster.  I unpresented the drives from the old cluster and presented them to the new.&lt;BR /&gt;
&lt;BR /&gt;
The drives show up, but they are completely inaccessible.  In disk manager, the partition information is correct for the drive; however, the format information seems to be gone and there appears to be no data on the disk.  I move the disk back to the old server and the same thing occurred.  Furthermore, I'm unable to format or repartition the disk from either server.&lt;BR /&gt;
&lt;BR /&gt;
In order to get the data back, I had to create a new SAN drive, reconfigure the cluster resource and restore the data.&lt;BR /&gt;
&lt;BR /&gt;
Does anyone know why this occurred?  Have I missed a step in the process?&lt;BR /&gt;
&lt;BR /&gt;
I still have the original, inaccessible drive available and I like to see if I can access the data on this drive before making future attempts to move larger, more important disks to the new cluster.</description>
    <pubDate>Fri, 22 Feb 2008 02:23:11 GMT</pubDate>
    <dc:creator>Chris VanderVelde</dc:creator>
    <dc:date>2008-02-22T02:23:11Z</dc:date>
    <item>
      <title>Moving SAN Drives</title>
      <link>https://community.hpe.com/t5/msa-storage/moving-san-drives/m-p/914807#M3757</link>
      <description>I'm replacing my existing Windows 2003 Adv. cluster with a new cluster running Windows 2003 Adv. R2.  I built the 2nd cluster and it functions fine.  Now I want to unpresent the data drives from the old cluster and reattach them to the new cluster.  I unpresented the drives from the old cluster and presented them to the new.&lt;BR /&gt;
&lt;BR /&gt;
The drives show up, but they are completely inaccessible.  In disk manager, the partition information is correct for the drive; however, the format information seems to be gone and there appears to be no data on the disk.  I move the disk back to the old server and the same thing occurred.  Furthermore, I'm unable to format or repartition the disk from either server.&lt;BR /&gt;
&lt;BR /&gt;
In order to get the data back, I had to create a new SAN drive, reconfigure the cluster resource and restore the data.&lt;BR /&gt;
&lt;BR /&gt;
Does anyone know why this occurred?  Have I missed a step in the process?&lt;BR /&gt;
&lt;BR /&gt;
I still have the original, inaccessible drive available and I like to see if I can access the data on this drive before making future attempts to move larger, more important disks to the new cluster.</description>
      <pubDate>Fri, 22 Feb 2008 02:23:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/msa-storage/moving-san-drives/m-p/914807#M3757</guid>
      <dc:creator>Chris VanderVelde</dc:creator>
      <dc:date>2008-02-22T02:23:11Z</dc:date>
    </item>
    <item>
      <title>Re: Moving SAN Drives</title>
      <link>https://community.hpe.com/t5/msa-storage/moving-san-drives/m-p/914808#M3758</link>
      <description>What storage platform are you using?  If you did not reconfigure the disk the data by and large should still be there.  Are you using multipath software? Sometime you will see the ghost of a drive in disk mgmt and not the real disk. If you see the disk you want on the new cluster host in disk mgmr you should just need to assign it a drv ltr, and then add it as a cl resource to a group.</description>
      <pubDate>Sat, 23 Feb 2008 22:03:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/msa-storage/moving-san-drives/m-p/914808#M3758</guid>
      <dc:creator>James Muell</dc:creator>
      <dc:date>2008-02-23T22:03:13Z</dc:date>
    </item>
    <item>
      <title>Re: Moving SAN Drives</title>
      <link>https://community.hpe.com/t5/msa-storage/moving-san-drives/m-p/914809#M3759</link>
      <description>We utilizing an EVA3000, the drive is configured as a RAID5 volume.  I've tried to assign the drive a letter, but it's still inaccessible.  The drive shows up on the server.</description>
      <pubDate>Mon, 25 Feb 2008 14:01:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/msa-storage/moving-san-drives/m-p/914809#M3759</guid>
      <dc:creator>Chris VanderVelde</dc:creator>
      <dc:date>2008-02-25T14:01:58Z</dc:date>
    </item>
    <item>
      <title>Re: Moving SAN Drives</title>
      <link>https://community.hpe.com/t5/msa-storage/moving-san-drives/m-p/914810#M3760</link>
      <description>With Clustering the disks are not identified by LUN number or drive letter.  Clustering uses a disk signature to identify a clustered disk and the disk signature information is stored in the registry.  Disk signature information is written on the volume and recorded in the registry at the time the disk is first mounted and brought online.  To get another cluster to recognize the disk, the disk's signature would have to be recorded in the registry.  There are a number of recovery procedures for different cluster recovery scenarios on the support.microsoft.com web site.</description>
      <pubDate>Sun, 02 Mar 2008 21:33:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/msa-storage/moving-san-drives/m-p/914810#M3760</guid>
      <dc:creator>JR-Pounds</dc:creator>
      <dc:date>2008-03-02T21:33:06Z</dc:date>
    </item>
  </channel>
</rss>

