Managing data center failure events
Managing data center recovery from failure events can include a failure event platform having aspects provided via a user interface that integrates multiple failure and recovery management and execution features. The features can include, among others, application drift monitoring between production and recovery environments, real-time health checks of system components, user-modifiable scripting for prioritizing and customizing data center recovery actions, and a recovery execution tool.
1. A system for managing data center failure events, comprising:
one or more processors; and
non-transitory computer-readable storage media encoding instructions which, when executed by the one or more processors, cause the system to:
monitor drift between a production environment and a recovery environment by using rules on multiple layers associated with the production environment, the multiple layers including an application layer, an operation system layer, a database layer, and a middleware layer, the monitor drift including:
to compare, at at least one of the layers, a production version of a component associated with the production environment and a recovery version of the component associated with the recovery environment and, based thereon;
detect a difference between the recovery version and the production version, the difference corresponding to a detected drift;
generate a drift alert based on the detected drift;
automate a failover to the recovery environment, including to execute a failure protocol defined by a failure script; and
simulate a failure event for the production environment by executing the failure script in a simulation environment that is different from the production environment.
2. The system of claim 1 , wherein further instructions, when executed by the one or more processors, cause the system to assign a severity to the detected drift.
3. The system of claim 2 , wherein further instructions, when executed by the one or more processors, cause the system to generate a graphical interface displaying one or more graphical elements representing the severity.
4. The system of claim 1 , wherein the failure script includes a recovery time objective or a recovery point objective for execution of the failover.
5. The system of claim 1 , wherein the failure protocol includes to reroute internet protocol traffic from one server to another server.
6. The system of claim 1 , wherein further instructions, when executed by the one or more processors, cause the system to generate a rules modification interface configured to receive input to modify aspects of the failure script.
7. The system of claim 6 ,
wherein the rules modification interface includes a recovery template; and
wherein one or more of the aspects are defined by the recovery template.
8. The system of claim 1 , wherein further instructions, when executed by the one or more processors, cause the system to determine an inefficiency in the failure protocol or in the failure script.
9. A computer implemented method, comprising: monitoring drift between a production environment and a recovery environment by using rules on multiple layers associated with the production environment, the multiple layers including an application layer, an operation system layer, a database layer, and a middleware layer, the monitoring drift including: comparing, at at least one of the layers, a production version of a component associated with the production environment and a recovery version of the component associated with the recovery environment and, based thereon; detecting a difference between the recovery version and the production version, the difference corresponding to a detected drift; generating a drift alert based on the detected drift; automating a failover to the recovery environment, including executing a failure protocol defined by a failure script; and simulating a failure event for the production environment by executing the failure script in a simulation environment that is different from the production environment.
10. The computer-implemented method of claim 9 , further comprising assigning a severity to the detected drift.
11. The computer-implemented method of claim 10 , further comprising generating a graphical interface displaying one or more graphical elements representing the severity.
12. The computer-implemented method of claim 9 , wherein the failure script includes a recovery time objective or a recovery point objective for execution of the failover.
13. The computer-implemented method of claim 9 , wherein the failure protocol includes rerouting internet protocol traffic from one server to another server.
14. The computer-implemented method of claim 9 , further comprising generating a rules modification interface configured to receive input to modify aspects of the failure script.
15. The computer-implemented method of claim 14 ,
wherein the rules modification interface includes a recovery template; and
wherein one or more of the aspects are defined by the recovery template.
16. The computer-implemented method of claim 9 , further comprising determining an inefficiency in the failure protocol or in the failure script.