Dear All,
I need to have a relocation task two weeks later, so I did a lab test recently.
My background is shown as below,
servers: srv01, srv02
OS: Windows Server 2008 R2 Enterprise
current IDC: IDC_A
current SAN storage: HP EVA
new IDC: IDC_B
new SAN storage: HP 3Par
I did a test last night in VM. srv01 and srv02 formed a failover clustering with iSCSI shared storage successfully. Then I removed the quorum disk (Disk 1) and the data disk (Disk 2) remain unchange, confirmed the quorum disk (Disk 1) was removed in the disk management. Then added another 1g quorum disk back to those two servers, the disk order (Disk 1 - quorum, Disk 2 - data) remained unchange. I initialized the quorum disk, assigned the original drive letter and volume label, followed by removing the drive letter.
Until this stage, since the disk signature of the quorum disk was changed, I expected I cannot start the cluster service. However, when I started the cluster service in svr01 only (svr02 remain stopped), the cluster was working properly, the quorum disk is online state. The quorum type I use is "Node and Disk Majority".
The question I asked myself is why it seems repair automatically. Is this a normal case for my task?
I just have experience for the coming relocation task in Windows Server 2003 cluster only, I dump the disk signature back to the new quorum disk and then type "net start clussvc /rq" to recreate the quorum disk.
Would anyone mind to share with me if you have similar experience?
Thanks.
Best Regards,
NeverFine