<div>
What does the cluster manager ---&gt; storage show you?
</div>


<div>
this is not the age old issues of serial numbers of disk mis-matching in the registry.
</div>


<div>
The cluster service is not starting I tried even with /fixquorum option too
</div>


<div>
<div class="content wysiwyg-content">
Hi, <br />
<br />
I'm trying to replicate my prod SQL Cluster environment into an isolated network.<br />
<br />
The Current setup is 2 node Windows 2003 Ent. SP2 with MSCS CLuster hosted in VMware with the data disks connected as RDMs including the quorum. SCSI sharing is enabled.<br />
<br />
I had powered down the VMs and &nbsp;cloned the datastore and RDM LUNs at the storage level and re-presented with different UIDs.<br />
<br />
I added the VM to inventory and removed existing RDM disks and added the new RDMs. Changed the network to private and powered on the VM, RDM disk shows up in disk management but when tried to access I get an error &quot;Device is not ready&quot;<br />
<br />
When I connect the RDMs to another windows 2003 STD or Windows 2008 the disk shows up without any issues. but same issues with windows 2003 ent.<br />
<br />
I'm not able to bring up the cluster since quorum disk is also in that<br />
<br />
I'm not sure how to proceed on this any suggestions will be helpful.<br />
<a href="https://filedb.experts-exchange.com/incoming/2016/01_w03/1070395/Capture.PNG" target="_blank" class="file-inline" title="screenshot (213 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>Capture.PNG</a>
</div>
</div>


Capture.PNG

Hi, 

I'm trying to replicate my prod SQL Cluster environment into an isolated network.

The Current setup is 2 node Windows 2003 Ent. SP2 with MSCS CLuster hosted in VMware with the data disks connected as RDMs including the quorum. SCSI sharing is enabled.

I had powered down the VMs and  cloned the datastore and RDM LUNs at the storage level and re-presented with different UIDs.

I added the VM to inventory and removed existing RDM disks and added the new RDMs. Changed the network to private and powered on the VM, RDM disk shows up in disk management but when tried to access I get an error "Device is not ready"

When I connect the RDMs to another windows 2003 STD or Windows 2008 the disk shows up without any issues. but same issues with windows 2003 ent.

I'm not able to bring up the cluster since quorum disk is also in that

I'm not sure how to proceed on this any suggestions will be helpful.

Windows 2003 Cluster clone does not identify the disks anymore

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).

Windows Server 2003

Virtualization is the act of creating a virtual (rather than actual) version of something, including (but not limited to) a virtual computer hardware platform, operating system (OS), storage device, or computer network resources. Virtualization is usually the creation of a system that executes separate from the underlying hardware resources, or the creation of an entire desktop for systems located elsewhere, similar to thin clients.