Enterprise service availability through identity preservation
View Patent ↗Systems and methods are described for service availability that provides automated recovery of server service in a timely and application intelligent manner, maintaining application consistency and integrity, while preserving server identity. The systems and methods, referred to herein as a Service Preservation System (SPS), manage complete recovery of server data and preserve continuity of server service, reestablishing user access to server(s) after an event or disaster in which in which primary or other server(s) fail. The failures, disasters, and losses referred to herein can be at many levels and include, but are not limited to, accidental deletion of an item, loss of an entire mailbox, loss of an entire disk drive, loss of an entire server, and/or loss of an entire server site.
1. A system comprising:
a number of near-line servers, including a first near-line server coupled to a second near-line server and one or more live servers that include data that provides services to a plurality of clients, wherein the number of near-line servers are coupled to one or more standby servers; and
an application aware engine coupled to the near-line servers and configured to continuously shadow the live servers by generating and maintaining a replica of the data used in providing the services to the clients in computer storage associated with the first near-line server;
the shadowing including generating and maintaining a replica of the first near-line server data in computer storage associated with the second near-line server;
wherein the engine is configured to automatically restore the services to the clients using the one or more standby servers in response to a detected failure of the one or more live servers, the restoring including materializing a recent and useable replica of the data and copying the recent and useable replica of the data from the first near-line server to a select standby server.
2. The system of claim 1 , further comprising at least one network coupled to the near-line servers.
3. The system of claim 2 , wherein the at least one network includes a local area network (LAN), wide area network (WAN), metropolitan area network (MAN), and storage area network (SAN).
4. The system of claim 1 , wherein each of the live servers and the standby servers is identified and addressed independently.
5. The system of claim 1 , wherein the shadowing generates and maintains the replica of the data in near real-time on the number of near-line servers, wherein the shadowing maintains complete integrity and consistency of the data.
6. The system of claim 1 , wherein the restoring includes one or more of the number of near-line servers preserving continuity of the services by automatically re-establishing access to the services by the clients.
7. The system of claim 1 , wherein the restoring includes one or more of the number of near-line servers restarting services corresponding to the data on the select standby server.
8. The system of claim 1 , wherein the restoring includes one or more of the number of near-line servers rebinding mailboxes in a directory service to the select standby server.
9. The system of claim 1 , wherein the restoring includes one or more of the number of near-line servers re-homing the clients.
10. The system of claim 1 , wherein the first near-line server is co-located with the live servers at a first site and the second near-line server is located at a second site.
11. The system of claim 10 , wherein the replica of the data is stored on the first near-line server during the shadowing, wherein the replica of the data is replicated from the first near-line server to the second near-line server.
12. The system of claim 11 , wherein the replica of the data is propagated to the select standby server from the first near-line server.
13. The system of claim 11 , wherein the replica of the data is propagated to the select standby server from the second near-line server.
14. The system of claim 1 , wherein the first near-line server is co-located with the live servers at a first site and the second near-line server is co-located with the one or more standby servers at a second site.
15. The system of claim 14 , wherein the replica of the data is stored on the first near-line server during the shadowing, wherein the replica of the data is replicated from the first near-line server to the second near-line server.
16. The system of claim 15 , wherein the replica of the data is copied to the select standby server from the first near-line server.
17. The system of claim 15 , wherein the replica of the data is copied to the select standby server from the second near-line server.
18. The system of claim 1 , wherein the data includes one or more of application data, databases, storage groups, mailbox data, and server data.
19. The system of claim 1 , wherein the one or more live servers include one or more of local servers, remote servers, database servers, messaging servers, electronic mail servers, instant messaging servers, Exchange Servers, voice-over Internet Protocol servers, collaboration servers, portals, customer relationship management (CRM) servers, enterprise resource planning (ERP) servers, business-to-business servers, and content management servers.
20. The system of claim 1 , wherein generating and maintaining the replica includes host-based replication of the data on the one or more standby servers.
21. The system of claim 20 , wherein host-based replication comprises:
writing data of the live servers to local storage of the live servers; and
writing data of the live servers to remote storage of the select standby server.
22. The system of claim 21 , wherein automatically restoring the services includes the select standby server assuming an identity and address of a live server that has failed.
23. The system of claim 1 , wherein generating and maintaining the replica includes storage-based replication of the data on the one or more standby servers.
24. The system of claim 23 , wherein storage-based replication comprises
writing data of the live servers to local storage of the live servers; and
replicating data of the local storage of the live servers to remote storage of the one or more standby server.
25. The system of claim 24 , wherein automatically restoring the services includes the select standby server assuming an identity and address of a live server that has failed.
26. The system of claim 1 , further comprising at least one proxy coupled between the clients, the live servers, and the standby servers, wherein generating and maintaining the replica includes the proxy writing data of the plurality of clients to components of at least one of the live servers and to components of at least one of the standby servers.
27. The system of claim 26 , wherein automatically restoring the services includes the proxy switching the clients from a failed live server to the select standby server to which data was written.