We help IT Professionals succeed at work.

Unable to move Exchange cluster after adding new disks

tmazowski
tmazowski asked
on
We are running a two-node Exchange 2003 cluster, and are in the process of migrating the storage to a new SAN. After adding the new disks, we can not move the Exchange cluster group over to the standby node. When we try to move the group, three of the four new disks show up as 'Failed' then it fails back. Everything works fine on the current node. The three disks contain a mixture of Logs and DBs. All of the disks have been added as dependencies for the MS Exchange System Attendant cluster resource.

When we attempt to move the group, we get the following System Event for each disk that fails:

Event Type:      Error
Event Source:      ClusSvc
Event Category:      Failover Mgr
Event ID:      1069
Date:            6/13/2010
Time:            7:23:47 AM
User:            N/A
Computer:      AM-USQPT-EX-03
Description:
Cluster resource 'Disk J:' in Resource Group 'Exchange Group' failed.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Comment
Watch Question

Commented:
Did you add these SAN disks to the other node before you clustered them?

Author

Commented:
Yes. Everything is zoned to both servers in the SAN.

Commented:
Did you test that both nodes could see the disks in Windows and had the same drive letters assigned before you clustered them?

Author

Commented:
I did not check on the drive letters on the standby host. I thought they would get picked up by the cluster configuration. Is there any way to verify this?

Commented:
can you confirm that you can see all of the disks on the standby node in Windows Disk management snap-in?  They should show up as Unknown/Unreadable, but you should see the same number of disks as on your active node.

Author

Commented:
Yes, they are all visible on the standby node.

Commented:
I think you will need to disable the cluster disk driver on both nodes and verify that the same drive letters are used for the disk resources on each node before re-enabling the cluster disk service.

Author

Commented:
We have to wait two weeks to test this, so if the moderators can leave this open, I'll respond then.

Commented:
Did u resolve this issue?
SOLVED - there are registry keys under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ClusDisk whihc did not mathc up properly. I exported them from the active node to the passive (after doing a backup), then everything was happy again.