Server control automation
View Patent ↗Control over servers and partitions within a computer network may be automated to improve response to disaster events within the computer network. For example, a monitoring server may be configured to automatically monitor servers through remote communications sessions. A disaster event may be detected based on information received from the partitions and servers within the network. After a disaster event occurs, the monitoring server may automatically execute a script or take other action to make a backup server or partition available. For example, the monitoring server may stop and deactivate a first partition that has failed, activate a second partition that is a mirror image of the first partition, and start the second partition.
1. A method, comprising:
detecting, by a monitoring server, a disaster event affecting a first partition of a first server;
deactivating, by the monitoring server, the first partition of the first server;
setting by the monitoring server, jump keys for the second partition;
setting by the monitoring server, boot settings for the second partition;
activating, by the monitoring server, a second partition of a second server; and
starting, by the monitoring server, the second partition of the second server.
2. The method of claim 1 , further comprising applying, by the monitoring server, boot settings to the second partition before starting the second partition.
3. The method of claim 1 , further comprising selecting, by the monitoring server, an application to recover before activating the second partition, in which the second partition of the second server corresponds to the selected application.
4. The method of claim 1 , further comprising communicating, by the monitoring server, with the second server through a remote communications session.
5. The method of claim 1 , further comprising stopping, by the monitoring server, the first partition of the first server.
6. The method of claim 1 , further comprising:
activating, by the monitoring server, a third partition of a third. server; and
starting, by the monitoring server, the third partition of the third server.
7. The method of claim 6 , in which the third partition and the second partition are started in a predetermined order by the monitoring server.
8. A computer program product, comprising:
a non-transitory computer readable medium comprising:
code to detect, by a monitoring server, a disaster event affecting a first partition of a first server;
code to deactivate, by the monitoring server, the first partition of the first server;
code to set, by the monitoring server, jump keys for the second partition;
code to set, by the monitoring server, boot settings for the second partition;
code to activate, by the monitoring server, a second partition of a second server; and
code to start, by the monitoring server, the second partition of the second server.
9. The computer program product of claim 8 , in which the medium further comprises code to apply, by the monitoring server, boot settings to the second partition before starting the second partition.
10. The computer program product of claim 8 , in which the medium further comprises code to select, by the monitoring server, an application to recover before activating the second partition, in which the second partition of the second server corresponds to the selected application.
11. The computer program product of claim 8 , in which the medium further comprises code to communicate, by the monitoring server, with the second server through a remote communications session,
12. The computer program product of claim 8 , in which the medium further comprises code to stop, by the monitoring server, the first partition of the first server.
13. The computer program product of claim 8 , in which the medium further comprises:
code to activate, by the monitoring server, a third partition of a third server; and
code to start, by the monitoring server, the third partition of the third server.
14. The computer program product of claim 13 , in which the medium further comprises code to start the second partition and to start the third partition in a predetermined order.
15. An apparatus, comprising:
a memory;
a network interface; and
a processor coupled to the memory and the network interface, in which the processor is configured:
to detect, through the network interface, a disaster event affecting a first partition of a first server;
to deactivate, through the network interface, the first partition of the first server;
to set, through the network interface, jump keys for the second partition:
to set, through the network interface, boot settings for the second partition;
to activate, through the network interface, a second partition of a second server; and
to start, through the network interface, the second partition of the second server.
16. The apparatus of claim 15 , in which the processor is further configured to apply, through the network interface, boot settings to the second partition before starting the second partition.
17. The apparatus of claim 15 , in which the processor is further configured to select, through the network interface, an application to recover before activating the second partition, in which the second partition of the second server corresponds to the selected application.
18. The apparatus of claim 15 , in which the processor is further configured to communicate, through the network interface, with the second server through a remote communications session.
19. The apparatus of claim 15 , in which the processor is further configured:
to activate, through the network interface, a third partition of a third server; and
to start, through the network interface, the third partition of the third server.
20. The apparatus of claim 15 , in which the processor is further configured to start the second partition and to start the third partition in a predetermined order.