Thursday, May 1, 2008

Metaset problem in a cluster node

To correct metaset problem. please follow the action plan below:
NodeA and NodeB. I assume that NodeB is not having metaset information
Action plan to correct the metaset issue this will require downtime on the node (NodeB)which is not having metaset information.
On node NodeB:
# init 0
on node NodeA:
# metaset -s setname -f -d -h NodeB
(this may take a 3/4 minute or so to return)
on node NodeB:
ok> boot
(wait for not to fully join the cluster)
on node NodeA:
# metaset -s setname-a -h NodeB
on node NodeB:
# metaset (should now list the metaset information)
test Cluster switchover with a: This requires an outage.
# scswitch -z -g RGname -h NodeB

No comments: