Proactive disaster recovery based on external event monitoring

1. A method for proactive disaster recovery preparation, the method comprising:

detecting a first event based on sensor data received from a sensor in a data center, wherein the sensor data captures an attribute of an environment proximate to a server in the data center;

determining a first severity grade indicative of a likelihood of the first event triggering data loss or breach at the server;

predicting a second event with a second severity grade that will occur after the first event, wherein the second severity grade is greater than the first severity grade;

identifying, from a plurality of event escalation trees, an event escalation tree comprising both the first event and the second event, wherein each respective event escalation tree defines a sequence of events and an action of a disaster recovery preparation process to execute for each respective event, wherein an amount of server resources utilized for the action is correlated with a respective severity grade of the respective event;

responsive to detecting events at the data center sequentially ordered in accordance with the identified event escalation tree, sequentially executing corresponding actions of the disaster recovery preparation process; and

subsequent to executing a respective action of the disaster recovery preparation process corresponding to the second event, triggering a disaster recovery state at the server.

2. The method of claim 1 , wherein sequentially executing corresponding actions comprises:

executing a first action corresponding to the first event in the event escalation tree;

monitoring subsequent sensor data for a next event directly after the first event in the event escalation tree, wherein the next event has a respective severity grade greater than the first severity grade; and

responsive to detecting the next event, executing a next action corresponding to the next event.

3. The method of claim 2 , wherein the first action comprises provisioning at least one virtual machine for use as a recovery virtual machine, the next action comprises transferring a portion of data stored on the server to the recovery virtual machine such that the portion is deleted from the server, and the respective action corresponding to the second event comprises transferring a remaining portion of the data to the recovery virtual machine.

4. The method of claim 2 , wherein the first action comprises removing all secure passwords and keys from the server, the next action comprises breaking all client and user connections to the server, and the respective action corresponding to the second event comprises deleting data classified as critical on the server.

5. The method of claim 2 , wherein the identified event escalation tree further defines a maximum time period between the first event and the next event, further comprising:

monitoring the subsequent sensor data for the next event within the maximum time period; and

in response to determining that the next event has not occurred within the maximum time period, identifying a different event escalation tree from the plurality of event escalation trees that comprises the first event and the second event.

6. The method of claim 1 , wherein the first event is a detection of an unauthorized individual near the data center and the second event is a detection of the unauthorized individual attempting to enter the data center.

7. The method of claim 1 , wherein the first event is a detection of a sign of a environmental condition developing that can damage hardware of the server and the second event is a detection of the developed environmental condition.

8. The method of claim 7 , wherein the sensor is in a first location of the data center, and wherein a first action of the disaster recovery preparation process comprises:

receiving additional sensor data from an additional sensor of a plurality of sensors comprising the sensor, wherein the additional sensor is in a second location of the data center;

subsequent to detecting the first event in the first location, determining whether the additional sensor data is indicative of the first event in the second location; and

in response to determining that the additional sensor data is not indicative of the first event, transferring data from the server to a different server in the second location of the data center.

9. The method of claim 8 , wherein the respective action corresponding to the second event comprises transferring the data from the different server to a cloud environment responsive to detecting the first event at the second location.

10. The method of claim 1 , wherein the respective action corresponding to the second event comprises moving data from a backup archive stored in a cold storage system of the server to a virtual machine disk file stored on a hot storage system of the server.

11. The method of claim 1 , wherein predicting the second event is in response to determining that the first severity grade is greater than a threshold severity grade.

12. The method of claim 11 , wherein the first severity grade is not greater than the threshold severity grade, further comprising:

detecting a third event based on additional sensor data received from an additional sensor of a plurality of sensors comprising the sensor, wherein the additional sensor data captures a different attribute of the environment proximate to the server;

determining a third severity grade of the third event;

responsive to determining that the third severity grade is not greater than the threshold severity grade, determining whether a combination of the sensor data and the additional sensor data correspond to an event with a severity grade greater than the threshold severity grade; and

responsive to determining that the severity grade is greater than the threshold severity grade, identifying a corresponding event escalation tree from the plurality of event escalating trees.

13. A system for proactive disaster recovery preparation, the system comprising: a hardware processor configured to:

detect a first event based on sensor data received from a sensor in a data center, wherein the sensor data captures an attribute of an environment proximate to a server in the data center;

determine a first severity grade indicative of a likelihood of the first event triggering data loss or breach at the server;

predict a second event with a second severity grade that will occur after the first event, wherein the second severity grade is greater than the first severity grade;

identify, from a plurality of event escalation trees, an event escalation tree comprising both the first event and the second event, wherein each respective event escalation tree defines a sequence of events and an action of a disaster recovery preparation process to execute for each respective event, wherein an amount of server resources utilized for the action is correlated with a respective severity grade of the respective event;

responsive to detecting events at the data center sequentially ordered in accordance with the identified event escalation tree, sequentially execute corresponding actions of the disaster recovery preparation process; and

subsequent to executing a respective action of the disaster recovery preparation process corresponding to the second event, trigger a disaster recovery state at the server.

14. The system of claim 13 , wherein the hardware processor is configured to sequentially execute corresponding actions by:

executing a first action corresponding to the first event in the event escalation tree;

monitoring subsequent sensor data for a next event directly after the first event in the event escalation tree, wherein the next event has a respective severity grade greater than the first severity grade; and

responsive to detecting the next event, executing a next action corresponding to the next event.

15. The system of claim 14 , wherein the first action comprises provisioning at least one virtual machine for use as a recovery virtual machine, the next action comprises transferring a portion of data stored on the server to the recovery virtual machine such that the portion is deleted from the server, and the respective action corresponding to the second event comprises transferring a remaining portion of the data to the recovery virtual machine.

16. The system of claim 14 , wherein the first action comprises removing all secure passwords and keys from the server, the next action comprises breaking all client and user connections to the server, and the respective action corresponding to the second event comprises deleting data classified as critical on the server.

17. The system of claim 14 , wherein the identified event escalation tree further defines a maximum time period between the first event and the next event, wherein the hardware processor is further configured to:

monitor the subsequent sensor data for the next event within the maximum time period; and

in response to determining that the next event has not occurred within the maximum time period, identify a different event escalation tree from the plurality of event escalation trees that comprises the first event and the second event.

18. The system of claim 13 , wherein the first event is a detection of an unauthorized individual near the data center and the second event is a detection of the unauthorized individual attempting to enter the data center.

19. The system of claim 13 , wherein the first event is a detection of a sign of a environmental condition developing that can damage hardware of the server and the second event is a detection of the developed environmental condition.

20. A non-transitory computer readable medium comprising computer executable instructions for proactive disaster recovery preparation, including instructions for:

detecting a first event based on sensor data received from a sensor in a data center, wherein the sensor data captures an attribute of an environment proximate to a server in the data center;

determining a first severity grade indicative of a likelihood of the first event triggering data loss or breach at the server;

predicting a second event with a second severity grade that will occur after the first event, wherein the second severity grade is greater than the first severity grade;

identifying, from a plurality of event escalation trees, an event escalation tree comprising both the first event and the second event, wherein each respective event escalation tree defines a sequence of events and an action of a disaster recovery preparation process to execute for each respective event, wherein an amount of server resources utilized for the action is correlated with a respective severity grade of the respective event;

responsive to detecting events at the data center sequentially ordered in accordance with the identified event escalation tree, sequentially executing corresponding actions of the disaster recovery preparation process; and

subsequent to executing a respective action of the disaster recovery preparation process corresponding to the second event, triggering a disaster recovery state at the server.