- 论坛徽章:
- 0
|
试试，说白了就是先disconnect再reconnect
- Using Cluster Administrator, delete the affected offline disk resources from the group. This won't destroy or offline the LUN, but it will tell Cluster Administrator not to include the LUN as a cluster resource. You might get an error message while you attempt to delete the disk resource, saying that because other resources are dependent on the disk resource, you are not allowed to remove the disk resource. You can work around this by changing the dependency of that other cluster resource: in other words, make that other resource dependent on another disk resource instead of the one you want to delete. This will not affect Windows or database functionality: neither SQL nor Exchange require having one disk resource instead of the other set as dependent. If you wish, you may change it back once you have re-added the disk resource.
- Using SnapDrive, disconnect the affected LUN (those which showed as offline in Cluster Admin and you just deleted) and reconnect to them. You may do this operation one LUN at the time or first disconnect them all and then reconnect them all.
- Using Cluster Administrator, create a new resource (of type disk) in the same group as it was before. (example: if you deleted a disk resource representing an exchange database LUN, recreate a disk resource for that LUN inside the Exchange group).
- Do the above for all LUNs you deleted previously from Cluster Admin.
- At this point, you should be able to bring the disk resources online, because the cluster service will now know that it needs to point to the LUNs with the new signature.
|
|
免费注册
发表于 2009-03-15 00:45
