From: R Aldridge (r_e_aldridge@yahoo.com)
Date: Sun Dec 22 2002 - 23:37:33 EST
Thanks for the responses.
The basic way to remove the cluster is:
- shutdown the system to be removed
- use clu_delete_member on the remaining node, and
remove the other node
One recommendation is to reboot the remaining node
from the non-clustered partition. I don't think this
would be advisable because the non-cluster partition
[if I understand your recommendation] is the original
system boot disk (internal SCSI drive), not the
current
system-disk that is in the shared StorageWorks array.
So, I'd basically be dropping back to a 2-year old
system disk if I did this.
Another recommendation is to remove the quorum disk.
I'll have to review the instructions, but I didn't
think a one-node cluster would function, without the
presence of either a quorum disk or a second node.
The current system disk is mirrored across the two
StorageWorks shelves, so I think I am in decent shape
to proceed.
One final recommendation is to review the
applications. In our case, several license managers
(license keys) are tied to the hardware id of the node
to be removed, so I will need to obtain new licenses
from the various application vendors.
Thanks again,
Robert
------Original posting---------------------
I'm planning to remove (sell) one of the two ES40
Alphaservers in our 2-node TruCluster.
Any special recommendations on how to make this
painless?
The cluster disks are currently shared (via
fibre/HSG60) -- and the disks will stay. The only
thing being removed is one of the ES40 systems.
I think it should be as easy as shutting down the one
node and removing it from the cluster configuration --
but if you have other advice that would be
appreciated.
__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:02 EDT