can someone please share their process on how to kernel patch a red hat ent 4 with veritas cluster 5? it's compose of a primary and backup node. the resources are db, disk, nic.
it doesn't need to be detail, just give me the steps like:
login to the backup node and update the kernel
reboot the backup node
check the kernel is updated
failover the cluster and check if the resources are up on the backup node
patch the primary node with the new kernel and reboot
failover it back
I wanted to extend a veritas file system which is running on veritas cluster and mounted on node2 system.
-- System State Frozen
A node1 running 0
A node2 running 0
-- Group State
-- Group System Probed ... (1 Reply)
I am working with a Sun StoredgeTek 6540 disk array connected to two Sun 490 servers. After taking one of the 490 nodes on the cluster down to single user mode I proceeded to install the latest cluster patch from Oracle. After the patch was completed the system rebooted, failed to rejoin the... (2 Replies)
Yesterday my customer told me to expect a vcs upgrade to happen in the future. He also plans to stop using HDS and move to EMC.
Am thinking how to migrate to sun cluster setup instead.
My plan as follows leave the existing vcs intact as a fallback plan.
Then install and build suncluster on... (5 Replies)
I need to update my redhatas4 kernel with kernel-2.6.9-67.0.20.EL.src.rpm.
When I run this
# rpm -ivh kernel-2.6.9-67.0.20.EL.src.rpm
warning: user brewbuilder does not exist - using root
warning: group brewbuilder does not exist - using root
warning: user brewbuilder does... (2 Replies)
Discussion started by: itik
LEARN ABOUT CENTOS
mkqdisk(8) Quorum Disk Management mkqdisk(8)NAME
mkqdisk - Cluster Quorum Disk Utility
Use of this command can cause the cluster to malfunction.
mkqdisk [-?|-h] | [-L] | [-f label] [-c device -l label] [-d [-d ...]]
The mkqdisk command is used to create a new quorum disk or display existing quorum disks accessible from a given cluster node.
OPTIONS -c device -l label
Initialize a new cluster quorum disk. This will destroy all data on the given device. If a cluster is currently using that device
as a quorum disk, the entire cluster will malfunction. Do not run this on an active cluster when qdiskd is running. Only one
device on the SAN should ever have the given label; using multiple different devices is currently not supported (it is expected a
RAID array is used for quorum disk redundancy). The label can be any textual string up to 127 characters - and is therefore enough
space to hold a UUID created with uuidgen(1).
Find the cluster quorum disk with the given label and display information about it.
-L Display information on all accessible cluster quorum disks.
-d Increase debugging level. Specify multiple times for more information. Currently, specifying more than twice has no effect.
SEE ALSO qdisk(5), qdiskd(8), uuidgen(1)
July 2006 mkqdisk(8)