I need to be able to power down a system insert and CD/USB boot from that device and then backup the entire system to a network share.
The backup needs to support RHEL and the VLM partition.
What product do I need?
I have two system cms-app-49-51 and cms-app-49-52 that I have been testing an ungraceful shutdown between systems (hard power off)
After failing over from cms-app-49-52 to cms-app-49-51 I brought cms-app-49-52 back up and cleared all error (or so I t...
Steps:
1. Failover Cluster from say app1 to App2 by shutting down App1.
2. Bring up the App1 server and now failover App2 to App1 server.
When the same scenario occurs multiple times then observed that all the services are offline at some poin...
I dont think there is a solution to this, becuse it would violate HA, but I need to ask the question.
Prerequisite: HA Setup is up and running.
Steps:
1). Unplug the heartbeat cable. (eth1)
2). Unplug/failover the primary system.
Secondary sy...
I have two groups for the VCS cluster, App_Cluster & App_Notifier setup in an active/passive setup. The App_Notifier runs the vcs notifer server and send out e-mail on Error level events. The App_Cluster contains all the service to be monitored. Ever...
Yes this would be a physical system, and of course the system would be powered back on and booted from the USB or CD drive. The point of the "offline backup" is not the have the native OS running while backing up the entire system. You used to have ...
Mike
I cleared out the error. and VCS then showed eveythign was offline on 49.52 before faulting 49.51. So i guess the next questions is do i need to clear the error on 52 then restart vcs on 52 before tring to failover again?
I think what is happening is that sometime when the server comes back online its is then sets the groups to AutoDisabled to True preventing the group from automatically failing over again
Mike,
The test in question is when we pull the power on the active box and not a service group failure. Once power is restored to the system, the same action is performed on the second system (the one that was failover too) without any checking of th...