Re: Quorum disk removal
- From: John <norad869@xxxxxxxxx>
- Date: Fri, 09 Feb 2007 02:09:08 -0600
Exactly - no cluster reboot is my goal and yes, I want to try this.
I was somewhat expecting that each non-QW would maintain the disk quorum somewhere - and my goal of avoiding a cluster reboot may be in vain.
I would not have 2 different disks - at least from the respect of the DISK_QUORUM - however back to what is in memory.
That said, I have booted a server with the DISK_QUORUM set (same as the other servers) - however the quorum disk was not mounted. The resulting OPCOM message had something like "remote access" and "please mount quorum disk". And if I remember correctly, it did boot - just the OPCOM messages every so oftern. Which leads me to believe that I can do this - just that OPCOM will complain during the transition.
Thanks Volker
Volker Halle wrote:
John,
I know one thing for sure from prior experience:
If you had a quorum disk in a cluster and have set DISK_QUORUM="" in
the various cluster members over time and rebooted each of them, the
'knowledge' about the 'previous' quorum disk name still exists in the
dynamic cluster data structures in memory. SHOW CLUSTER/CONT and ADD
QD_NAME still shows that old quorum disk name, even if it has been
removed from all individual systems. It does show QF_VOTE: NO
As it is not allowed/supported to have 2 different quorum disks in a
cluster, bringing in a new quorum disk may cause problems, but it may
also work. A cluster reboot would be the only supported way to change
the quorum disk - but you probably know this and just want to try to
prevent a cluster reboot...
Volker.
.
- Follow-Ups:
- Re: Quorum disk removal
- From: JF Mezei
- Re: Quorum disk removal
- From: Volker Halle
- Re: Quorum disk removal
- Prev by Date: Re: Quorum disk removal
- Next by Date: Re: Help configuring VMS mail with Dynaccess.com
- Previous by thread: Re: Quorum disk removal
- Next by thread: Re: Quorum disk removal
- Index(es):
Relevant Pages
|