System and method for dynamically enabling an application for business continuity
System and method for dynamically enabling an application for business continuity are described. In one embodiment, a business continuity engine (“BCE”) for managing and controlling a high-availability applications comprises a configuration management module for maintaining information regarding the current configuration of a BC application; a status monitor for monitoring a status of the BC application via a high-availability (“HA”) wrapper thereof and initiating a migration of the BC application from a first server of a primary cluster to a second location of a secondary cluster based on the determined status; and an application migration module for migrating the BC application to the second server responsive to the initiating. The BCE further comprises a storage area network (“SAN”) migration module for enabling storage media for use by the BC application; and a communications module for facilitating an exchange of data between the BC engine and the BC application.
1. A business continuity engine (“BCE”) for managing and controlling high-availability applications, the BCE comprising:
a computer;
a configuration management module executing on the computer for maintaining information regarding the current configuration of a BC application executing on a first server of a primary cluster of servers, the BC application comprising a software interface that exposes a set of high-availability (“HA”) APIs, said APIs enabling said BC application to provide information to and retrieve information from the BCE;
a status monitor executing on the computer for monitoring a status of the BC application via a high-availability (“HA”) wrapper thereof and initiating a migration of the BC application to load the application from the first server of the primary cluster to a second server of a secondary cluster for execution thereon based on the determined status, the HA wrapper enabling the BC application to retrieve information about servers available for said migration in the secondary cluster;
an application migration module executing on the computer for loading the BC application to the second server for said execution responsive to the initiating;
a storage area network (“SAN”) migration module executing on the computer for enabling storage media for use by the BC application upon being loaded to the second server; and
a communications module executing on the computer for facilitating an exchange of data between the BC engine and the BC application.
2. The BCE of claim 1 wherein the BCE interacts with the BC application via said high-availability (“HA”) wrapper and said APIs.
3. The BCE of claim 1 , wherein the HA wrapper enables customized monitoring and application status to enable dynamic monitoring based on an awareness of the BC application.
4. The BCE of claim 1 , wherein the HA wrapper enables customized monitoring and application status to enable dynamic monitoring based on information external to the BC application.
5. The BCE of claim 1 , wherein the HA wrapper enables dynamic definition of system requirements necessary for loading of the BC application to the second server at a current state thereof.
6. The BCE of claim 1 , wherein the HA wrapper enables dynamic definition of steps for unloading the BC application from the first server and loading it to the second server.
7. A method for managing and controlling high-availability applications in a business continuity (“BC”) cluster system comprising first and second clusters, each of the clusters comprising a plurality of servers connected to a respective storage network, the method comprising:
loading a BC engine (“BCE”) onto each of the servers, the BCE for managing and controlling BC applications running on one of the servers;
running a BC application on a selected one of the plurality of servers of the first cluster, the BC application including a software application and a high-availability (“HA”) wrapper comprising a software interface that exposes a set of HA APIs to the software application, said APIs enabling said BC application to provide information to and retrieve information from the BCE, and the HA wrapper enabling the BC application to retrieve information about servers available for migration in the secondary cluster;
mirroring data of the BC application to another one selected server of the second cluster; and
responsive to failure of the selected one server of the first cluster, loading the BC application from the selected one server of the first cluster to said another one selected server of the second cluster using the HA APIs.
8. The method of claim 7 wherein the first and second clusters are geographically dispersed.
9. The method of claim 7 further comprising, responsive to failure of the selected one server of the first cluster, selecting said another one selected server of the second cluster using the HA APIs prior to loading the BC application to said another one selected server of the second cluster.
10. The method of claim 7 wherein the HA wrapper enables customized monitoring and application status to enable dynamic monitoring based on an awareness of the BC application.
11. The method of claim 7 wherein the HA wrapper enables customized monitoring and application status to enable dynamic monitoring based on information external to the BC application.
12. The method of claim 7 wherein the HA wrapper enables dynamic definition of system requirements necessary for migration of the BC application at a current state thereof.
13. The method of claim 7 wherein the HA wrapper enables dynamic definition of steps for unloading the BC application from the server of the first cluster and loading it to the selected server of the second cluster.
14. A system for managing and controlling high-availability applications in a business continuity (“BC”) cluster network comprising first and second clusters, each of the clusters comprising a plurality of servers connected to a storage network, the system comprising:
a BC engine (“BCE”) loaded onto each of the servers, the BCE for managing and controlling BC applications running on one of the servers;
a BC application executing on a selected one of the servers of the first cluster, the BC application including a software application and a high-availability (“HA”) wrapper comprising a software interface that exposes a set of HA APIs to the software application, said APIs enabling said BC application to provide information to and retrieve information from the BCE, and the HA wrapper enabling the BC application to retrieve information about servers available for migration in the secondary cluster;
and
an application migration module responsive to failure of the selected one server of the first cluster for loading the BC application from the selected one of the servers of the first cluster to another selected one of the servers of the second cluster using the HA APIs; wherein the application migration module mirrors data of the BC application to the second cluster.
15. The system of claim 14 wherein the first and second clusters are geographically dispersed.
16. The system of claim 14 further comprising, responsive to failure of the selected server of the first cluster, selecting said selected one of the servers of the second cluster using the HA APIs prior to loading the BC application to said selected one of the servers of the second cluster.
17. The system of claim 14 wherein the HA wrapper enables customized monitoring and application status to enable dynamic monitoring based on an awareness of the BC application.
18. The system of claim 14 wherein the HA wrapper enables customized monitoring and application status to enable dynamic monitoring based on information external to the BC application.
19. The system of claim 14 wherein the HA wrapper enables dynamic definition of system requirements necessary for migration of the BC application at a current state thereof.
20. The system of claim 7 wherein the HA wrapper enables dynamic definition of steps for unloading the BC application from the server of the first cluster and loading it to the selected server of the second cluster.