> ============ Last updated: Fri Dec 7 10:18:29 2007 Current DC: NodeA > (2a7021a1-ab44-403d-80a4-5ff9b4e24fcc) 2 Nodes configured. 1 > Resources configured. ============ > > Node: NodeA (2a7021a1-ab44-403d-80a4-5ff9b4e24fcc): standby Node: > NodeB (296a344e-4ca5-4aae-be0b-7fc4473a7e05): online > > > I still don't know what is "standby" - seems to refer to a node; It > also seems the opposite of "standby" is "online". What does that > mean? It also seems my DC is in "standby". I could really use some > help to get a grasp of these concepts as they confuse me and even > simple things like this I don;t know how to interpret.
Standby means Heartbeat (on that node) is in "standby" mode, i.e. running, but unable to run any resources. > > [RH] well, I would like to have the two nodes of the cluster be one > active and one passive (active and passive in plain English - just in > case they happen to clash with HA terminology I just don't master > yet). The active node is the one I connect to if I use the cluster > IP, and runs all the services I am interested in. Forcing a fail over > in my mind means having the active node become passive, the passive > node become active and offering the same services the active node was > offering (say a simple web server). If I ssh to the same cluster IP > address I'd end up on the newly active node. I was under the > impression this would be fairly easy achieved using a simple command, > which seems not to be the case. Essentially I want one node to do > everything until I force a failover and then I want the other node to > do everything. No resource distribution, nothing fancy. Then always keep node B in standby mode, and when you need to failover, put node A in standby (assuming it's still running), then take node B off standby. See the crm_standby command (crm_standby --help). As well, you'll need to tell your cluster to ignore quorum. Yan
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
