Self-contained disaster detection for replicated multi-controller systems
Self-contained disaster detection for replicated multi-controller systems is described herein. A system as described herein can include a memory that stores computer executable components and a processor that executes computer executable components stored in the memory. The computer executable components can include a data synchronization component that replicates data written at a primary production site, resulting in replicated data from the primary production site; a status monitoring component that reads status identifiers contained in the replicated data at periods of a time interval, wherein the status identifiers are written by respective controllers at the primary production site; and a disaster recovery component that initializes a failover procedure at the primary production site in response to an absence of updates to a first threshold number of the status identifiers within a second threshold number of the periods.
1. A system, comprising:
a memory that stores executable components; and
a processor that executes the executable components stored in the memory, wherein the executable components comprise:
a data synchronization component that replicates data written at a primary production site, resulting in replicated data from the primary production site;
a status monitoring component that reads status identifiers contained in the replicated data at periods of a time interval, wherein the status identifiers are written by respective controllers at the primary production site; and
a disaster recovery component that initializes a failover procedure at the primary production site in response to an absence of updates to a first threshold number of the status identifiers within a second threshold number of the periods.
2. The system of claim 1 , wherein the first threshold number of the status identifiers comprises at least two status identifiers.
3. The system of claim 2 , wherein the disaster recovery component initializes a controller recovery procedure at the primary production site in response to the absence of at least some of the updates to at least one of the status identifiers and less than the first threshold number of the status identifiers within the second threshold number of the periods.
4. The system of claim 1 , wherein the executable components further comprise:
a verification component that confirms a primary site failure at the primary production site in response to the absence of the updates from the primary production site to the first threshold number of the status identifiers within the second threshold number of the periods, wherein the disaster recovery component initializes the failover procedure at the primary production site further in response to the verification component confirming the primary site failure at the primary production site.
5. The system of claim 1 , wherein the executable components further comprise:
a notification component that generates a user notification in response to the absence of at least some of the updates to at least one of the status identifiers within the second threshold number of the periods.
6. The system of claim 1 , wherein the status identifiers comprise a timestamp.
7. The system of claim 1 , wherein the primary production site comprises a storage array, and wherein the replicated data is written by the primary production site to a logical unit of the storage array.
8. The system of claim 7 , wherein the logical unit is divided into a group of partitions, and wherein the status identifiers are written by the respective controllers associated with the primary production site to respective ones of the group of partitions.
9. The system of claim 1 , wherein the status identifiers are first status identifiers, and wherein the executable components further comprise:
a status reporting component that generates respective second status identifiers corresponding to respective local controllers.
10. The system of claim 9 , wherein the data synchronization component replicates the second status identifiers to the primary production site.
11. A method, comprising:
mirroring, by a device operatively coupled to a processor, data written at a primary computing site, resulting in mirrored data from the primary computing site;
reading, by the device, status indicators contained in the mirrored data at periods of a time interval, wherein the status indicators are written by respective controllers at the primary computing site; and
initializing, by the device, a disaster recovery procedure at the primary computing site in response to an absence of updates to a first threshold number of the status indicators within a second threshold number of the periods.
12. The method of claim 11 , wherein the first threshold number of the status indicators comprises at least two status identifiers, and wherein the method further comprises:
initializing a controller recovery procedure at the primary computing site in response to the absence of at least some of the updates to at least one of the status indicators and less than the first threshold number of the status indicators within the second threshold number of the periods.
13. The method of claim 11 , further comprising:
confirming, by the device, a primary site failure at the primary computing site in response to the absence of the updates from the primary computing site to the first threshold number of the status indicators within the second threshold number of the periods, wherein the initializing the disaster recovery procedure comprises initializing the disaster recovery procedure at the primary computing site further in response to the confirming.
14. The method of claim 11 , wherein the status indicators comprise a timestamp.
15. The method of claim 11 , wherein the primary computing site comprises a storage array, and wherein the mirrored data is written by the primary computing site to a logical unit of the storage array.
16. The method of claim 15 , wherein the logical unit is divided into a group of partitions, and wherein the status indicators are written by the respective controllers associated with the primary computing site to respective ones of the group of partitions.
17. A machine-readable storage medium comprising executable instructions that, when executed by a processor of a replicated computing site, facilitate performance of operations, the operations comprising:
creating a local copy of data written at a primary computing site;
reading status identifiers contained in the local copy of the data written at the primary computing site at periods of a time interval, wherein the status identifiers are written by respective controllers at the primary computing site; and
triggering a disaster recovery procedure at the primary computing site in response to an absence of updates to a first threshold number of the status identifiers within a second threshold number of the periods.
18. The machine-readable storage medium of claim 17 , wherein the first threshold number of the status identifiers comprises at least two status identifiers, and wherein the operations further comprise:
triggering a controller recovery procedure at the primary computing site in response to the absence of at least some of the updates to at least one of the status identifiers and less than the first threshold number of the status identifiers within the second threshold number of the periods.
19. The machine-readable storage medium of claim 17 , wherein the operations further comprise:
confirming a primary site failure at the primary computing site in response to the absence of the updates to the first threshold number of the status identifiers within the second threshold number of the periods; and
triggering the disaster recovery procedure at the primary computing site further in response to the confirming.
20. The machine-readable storage medium of claim 17 , wherein the primary computing site comprises a storage array, wherein the data written at the primary computing site is written to respective partitions of a logical unit of the storage array, and wherein the status identifiers are written by the respective controllers associated with the primary computing site to the respective partitions.