High availability system outage recovery

1 . A recovery system for high availability system outage recovery, the recovery system comprising:

one or more memories; and

one or more processors, communicatively coupled to the one or more memories, configured to:

communicate, based on a trigger to generate a system resource document for a target system, with a set of resources of the target system to perform an auto-discovery procedure;

generate, based on a result of the auto-discovery procedure, the system resource document identifying the set of resources of the target system;

store, after validating one or more network addresses associated with the target system in a recovery archive, the system resource document and the one or more network addresses;

obtain, after storing the system resource document and the one or more network addresses associated with the target system in the recovery archive, and based on an outage event, the system resource document from the recovery archive; and

transmit a set of signals to execute a set of recovery actions on the set of resources of the target system, using the system resource document recovered from the recovery archive, to re-instantiate one or more resources, of the set of resources, on a new target system,

wherein executing the set of recovery actions includes rerouting inbound traffic associated with the set of resources to the new target system based on the one or more network addresses stored prior to the outage event.

2 . The recovery system of claim 1 , wherein the one or more processors, to transmit the set of signals to execute the set of recovery actions, are configured to:

identify, using the system resource document, a class of a resource of the set of resources; and

transmit a signal, of the set of signals, to execute a recovery action, of the set of recovery actions, associated with the class of the resource.

3 . The recovery system of claim 2 , wherein the class of the resource is a particular class, and

wherein the one or more processors, to transmit the signal to execute the recovery action, are configured to:

fail over the resource from the target system to the new target system without stopping the inbound traffic associated with the resource based on the class of the resource being the particular class.

4 . The recovery system of claim 2 , wherein the class of the resource is a particular class, and

wherein the one or more processors, to transmit the signal to execute the recovery action, are configured to:

stop the inbound traffic associated with the resource based on the class of the resource being the particular class;

fail over the resource from the target system to the new target system based on stopping the inbound traffic associated with the resource; and

resume the inbound traffic associated with the resource based on failing over the resource.

5 . The recovery system of claim 1 , wherein the outage event is a testing event, and

wherein the one or more processors are further configured to:

receive information identifying a timing periodicity for the testing event; and

trigger the outage event based on the timing periodicity for the testing event.

6 . The recovery system of claim 5 , wherein the one or more processors, to trigger the outage event, are configured to:

detect an availability period during which the target system is configured to be available; and

trigger the outage event outside the availability period.

7 . The recovery system of claim 1 , wherein the outage event is a non-testing event, and

wherein the one or more processors are further configured to:

monitor, using the system resource document, a status of the set of resources of the target system; and

detect, based on monitoring the status of the set of resources of the target system, a change to the status of the set of resources of the target system.

8 . The recovery system of claim 1 , wherein the one or more processors are further configured to:

establish a periodicity for triggering the outage event;

attempt to receive a signal canceling the outage event during a period of time associated with the periodicity for triggering the outage event; and

detect the outage event at an end of the period of time based on whether the signal canceling the outage event is received.

9 . A non-transitory computer-readable medium storing a set of instructions, the set of instructions comprising:

one or more instructions that, when executed by one or more processors of a recovery system, cause the recovery system to:

auto-discover, based on a trigger to generate a system resource document for a target system, a set of resources of the target system;

generate, for the set of resources of the target system, a set of auto-discovery files;

encapsulate the set of auto-discovery files in the system resource document;

store, after validating one or more network addresses associated with the target system in a recovery archive, the system resource document and the one or more network addresses associated with the target system in a recovery archive;

obtain, after storing the system resource document and the one or more network addresses associated with the target system in the recovery archive, and based on an outage event, the system resource document from the recovery archive; and

transmit a set of signals to cause a set of recovery actions on the set of resources of the target system, using the set of auto-discovery files encapsulated in the system resource document to re-instantiate one or more resources, of the set of resources, on a new target system,

wherein the set of recovery actions includes rerouting inbound traffic associated with the set of resources to the new target system based on the one or more network addresses stored prior to the outage event.

10 . The non-transitory computer-readable medium of claim 9 , wherein the one or more instructions, when executed by the one or more processors of the recovery system, further cause the recovery system to:

transmit information identifying the new target system to one or more client devices associated with the target system.

11 . The non-transitory computer-readable medium of claim 10 , wherein set of attributes includes at least one of:

a resiliency tier attribute,

a domain name service (DNS) mapping attribute,

a relational database service (RDS) attribute, or

an endpoint attribute.

12 . The non-transitory computer-readable medium of claim 10 , wherein the set of resources includes a set of cloud applications deployed on a cloud network associated with the target system.

13 . The non-transitory computer-readable medium of claim 9 , wherein the one or more instructions, that cause the recovery system to auto-discover the set of resources, cause the recovery system to:

auto-discover a plurality of different types of resources, the plurality of different types of resources including at least one of:

a datastore type of resource,

an event type of resource, or

an application programming interface type of resource.

14 . The non-transitory computer-readable medium of claim 13 , wherein the one or more instructions, when executed by the one or more processors, further cause the recovery system to:

update an existing system resource document periodically according to a configured periodicity.

15 . The non-transitory computer-readable medium of claim 9 , wherein the one or more instructions, when executed by the one or more processors, further cause the recovery system to:

establish a periodicity for triggering the outage event;

attempt to receive a signal canceling the outage event during a period of time associated with the periodicity for triggering the outage event; and

detect the outage event at an end of the period of time based on whether the signal canceling the outage event is received.

16 . A method, comprising:

communicating, by a recovery system and based on a trigger to generate a system resource document for a target system, with a set of resources of the target system to perform an auto-discovery procedure;

generating, by the recovery system based on a result of the auto-discovery procedure, the system resource document identifying the set of resources of the target system;

storing, by the recovery system and after validating one or more network addresses associated with the target system in a recovery archive, the system resource document and the one or more network addresses associated with the target system in a recovery archive;

obtaining, by the recovery system, after storing the system resource document and the one or more network addresses associated with the target system in the recovery archive, and based on an outage event, the system resource document from the recovery archive;

failing over, by the recovery system, the set of resources of the target system to a new target system,

wherein failing over the set of resources includes rerouting inbound traffic associated with the set of resources to the new target system based on the one or more network addresses stored prior to the outage event; and

transmitting, by the recovery system, a set of notifications associated with the new target system.

17 . The method of claim 16 , wherein failing over the set of resources comprises:

failing over a resource, of the set of resources, from the target system to the new target system without stopping the inbound traffic associated with the resource based on an attribute of the resource.

18 . The method of claim 16 , wherein failing over the set of resources comprises:

stopping the inbound traffic associated with a resource, of the set of resources, based on an attribute of the resource;

failing over the resource from the target system to the new target system based on stopping the inbound traffic associated with the resource; and

resuming the inbound traffic associated with the resource based on failing over the resource.

19 . The method of claim 16 , wherein the outage event is a testing event, and

further comprising:

receiving information identifying a timing periodicity for the testing event; and

triggering the outage event based on the timing periodicity for the testing event.

20 . The method of claim 19 , wherein triggering the outage event comprises:

detecting an availability period during which the target system is configured to be available; and

triggering the outage event outside the availability period.