# US 2020/0349036 A1 · Self-contained disaster detection for replicated multi-controller systems

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2020/0349036 A1
- Document ID: US20200349036A1
- Status: Published application
- Kind: A1
- Application number: 16/403,192
- Filed: 2019-05-03
- Published: 2020-11-05
- Earliest claimed: 2019-05-03
- Assignees: EMC IP Holding Company LLC
- Applicants: EMC IP Holding Company LLC
- Inventors: Bharadwaj R. Sathavalli; Shampavman Chenjeri Gururajarao
- Web page: https://patentgrep.com/patent/US20200349036A1

## CPC

- G06F 11/0751: {Error or fault detection not based on redundancy (power supply failures G06F1/30; network fault management H04L41/06)}
- G06F 11/2025: {using centralised failover control functionality}
- G06F 11/0709: {in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems}
- G06F 11/0712: {in a virtual computing platform, e.g. logically partitioned systems}
- G06F 11/0727: {in a storage system, e.g. in a DASD or network based storage system (drivers for digital recording or reproducing units G06F3/06; circuits for error detection or correction within digital recording or reproducing units G11B20/18; for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS], H04L67/1097)}
- G06F 11/1464: {for networked environments}
- G06F 11/1471: involving logging of persistent data for recovery
- G06F 11/2082: {Data synchronisation}
- G06F 11/301: {where the computing system is a virtual computing platform, e.g. logically partitioned systems (virtual machines G06F9/45533; logical partitioning of resources G06F9/5077)}
- G06F 11/2089: {Redundant storage control functionality}
- G06F 2201/81: Threshold
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

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.

## Claims

### Claim 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.

### Claim 2 (depends on 1)

The system of claim 1, wherein the first threshold number of the status identifiers comprises at least two status identifiers.

### Claim 3 (depends on 2)

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.

### Claim 4 (depends on 1)

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.

### Claim 5 (depends on 1)

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.

### Claim 6 (depends on 1)

The system of claim 1, wherein the status identifiers comprise a timestamp.

### Claim 7 (depends on 1)

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.

### Claim 8 (depends on 7)

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.

### Claim 9 (depends on 1)

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.

### Claim 10 (depends on 9)

The system of claim 9, wherein the data synchronization component replicates the second status identifiers to the primary production site.

### Claim 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.

### Claim 12 (depends on 11)

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.

### Claim 13 (depends on 11)

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.

### Claim 14 (depends on 11)

The method of claim 11, wherein the status indicators comprise a timestamp.

### Claim 15 (depends on 11)

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.

### Claim 16 (depends on 15)

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.

### Claim 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.

### Claim 18 (depends on 17)

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.

### Claim 19 (depends on 17)

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.

### Claim 20 (depends on 17)

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.
