RECOVERY SERVICE LOCATION FOR A SERVICE
First Claim
1. A method for establishing and maintaining a recovery service location for a service, comprising:
- synchronizing a primary location of a service with a secondary location of the service while the primary location of the service is actively receiving requests from users, wherein the secondary location of the service is substantially configured the same as the primary location of the service and is updated as the primary location is updated;
detecting a network failure of the primary location of the service; and
setting the secondary location of the service as the primary location in response to the network failure.
2 Assignments
0 Petitions
Accused Products
Abstract
A secondary location of a network acts as a recovery network for a primary location of the service. The secondary location is maintained in a warm state that is configured to replace the primary location in a case of a failover. During normal operation, the primary location actively services user load and performs backups that include full backups, incremental backups and transaction logs that are automatically replicated to the secondary location. Information is stored (e.g. time, retry count) that may be used to assist in determining when the backups are restored correctly at the secondary location. The backups are restored and the transaction logs are replayed at the secondary location to reflect changes (content and administrative) that are made to the primary location. After failover to the secondary location, the secondary location becomes the primary location and begins to actively service the user load.
-
Citations
20 Claims
-
1. A method for establishing and maintaining a recovery service location for a service, comprising:
-
synchronizing a primary location of a service with a secondary location of the service while the primary location of the service is actively receiving requests from users, wherein the secondary location of the service is substantially configured the same as the primary location of the service and is updated as the primary location is updated; detecting a network failure of the primary location of the service; and setting the secondary location of the service as the primary location in response to the network failure. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9)
-
-
10. A computer-readable storage medium having computer-executable instructions for establishing and maintaining a recovery service location for a service, comprising:
-
synchronizing a primary location of a service with a secondary location of the service while the primary location of the service is actively receiving requests from users by performing actions, comprising; creating full backups of databases; creating incremental backups between the full backups of the databases; creating transaction logs; providing the full backups, incremental backups and transaction logs to the secondary location, wherein the transaction logs are replayed at the secondary location; detecting a network failure of the primary location of the service; and setting the secondary location of the service as the primary location in response to the network failure. - View Dependent Claims (11, 12, 13, 14, 15)
-
-
16. A system for establishing and maintaining a recovery service location for a service, comprising:
-
a processor and a computer-readable medium; an operating environment stored on the computer-readable medium and executing on the processor; and a cloud manager operative to perform actions, comprising; synchronizing a primary location of a service with a secondary location of the service while the primary location of the service is actively receiving requests from users by performing actions, comprising; creating backups including transaction logs of databases; providing the backups and the transaction logs to the secondary location for replay at the secondary location; detecting a network failure of the primary location of the service; and setting the secondary location of the service as the primary location in response to the network failure. - View Dependent Claims (17, 18, 19, 20)
-
Specification