US2014040658A1PendingUtilityA1
Disaster Recovery Framework
Est. expiryFeb 23, 2025(expired)· nominal 20-yr term from priority
G06F 11/2038G06F 11/2033G06F 11/1415G06F 11/203G06F 11/2025
46
PatentIndex Score
0
Cited by
0
References
0
Claims
Abstract
A System and method of orchestrating failover operations of servers providing services to an internal computer network includes a DR server configured to execute a control script that performs a failover operation. Information needed to perform the failover operation is stored on the DR server thereby eliminating the need to store agents on each of the application's primary and backup servers. The DR server may provide a centralized location for the maintenance an update of the failover procedures for the internal network's redundant services. A failover operation may be initiated by an authorized user in communication with the internal computer network.
Claims
exact text as granted — not AI-modifiedWhat is claimed:
1 . A system comprising:
a primary server in communication with an internal computer network, the primary server executing an application providing a service to the internal computer network; a backup server in communication with the internal computer network, the backup server configured to execute the application; a DR server in communication with the internal computer network; and a failover script stored on the DR server, the failover script performing a failover operation on the backup server when executed on the DR server.
2 . The system of claim 1 wherein the internal computer network is an intranet.
3 . The system of claim 1 wherein the failover operation comprises a migration of the service from the primary server to the backup server.
4 . The system of claim 1 wherein the failover operation comprises a takeover of the service by the backup server.
5 . The system of claim 1 wherein the failover operation comprises a failback of the service from the backup server to the primary server.
6 . The system of claim 1 wherein the failover script is initiated to begin execution on the DR server from a computer in communication with the internal computer network.
7 . A method of orchestrating a failover operation from a DR server in communication with an internal computer network, a primary server and a backup server, the primary server and backup server configured to execute an application that provides a service to the internal computer network, the method comprising:
receiving a command through the internal computer network from a user to perform a failover operation for the application; retrieving a security ticket from the primary server based on the user; reading a configuration file stored on the DR server, the configuration file containing information for the failover operation for the application; and executing the failover operation for the application based on the information read from the configuration file.
8 . The method of claim 7 wherein the step of executing further comprises:
logging on to a DNS server providing a domain name service to the internal computer network; and
switching a DNS alias of the primary server with a DNS alias of the backup server.
9 . The method of claim 7 wherein the step of executing further comprises:
logging on to a gatekeeper host providing storage area network management service to the internal computer network; and
switching a state of a primary storage with a state of a secondary storage thereby enabling mounting of the secondary storage for the backup server.
10 . The method of claim 7 wherein the step of executing further comprises executing a script command from the configuration file.
11 . The method of claim 10 wherein the step of executing further comprises:
receiving a return signal indicating a status of the executed script command;
recording the status in a log file; and
displaying the status to the user.
12 . The method of claim 11 wherein the script command is re-executed if the status of the executed script command indicates failure.
13 . The method of claim 11 wherein if the status of the executed script command indicates failure, a next script command from the configuration file is executed.Cited by (0)
No later patents cite this yet.
References (0)
No backward citations on record.