# US 2025/0094284 A1 · Detection and recovery of platform specific replication failures in sdnas solution on a storage system

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

- Number: US 2025/0094284 A1
- Document ID: US20250094284A1
- Status: Published application
- Kind: A1
- Application number: 18/467,076
- Filed: 2023-09-14
- Published: 2025-03-20
- Earliest claimed: 2023-09-14
- Assignees: Dell Products L.P.
- Applicants: Dell Products L.P.
- Inventors: Rashmi Shashidhar; Kumaravel Palanisamy; Likith Prasanna P
- Web page: https://patentgrep.com/patent/US20250094284A1

## CPC

- 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/2094: {Redundant storage or storage space (G06F11/2056 takes precedence)}
- G06F 11/0706: {the processing taking place on a specific hardware platform or in a specific software environment}
- G06F 11/1402: {Saving, restoring, recovering or retrying}
- G06F 2201/805: Real-time
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

An example methodology includes monitoring a replication workflow execution on a storage system and, responsive to a detection of a failure of the replication workflow, determining whether the failure is in a Software Defined Network Attached Storage (SDNAS) or in an underlying storage array platform. The method also includes, responsive to a determination that the failure is in the SDNAS, validating health of the SDNAS for performing the replication workflow and, responsive to validating the health of the SDNAS, performing recovery of the failed replication workflow. The method further includes, responsive to a determination that the failure is in the underlying storage array platform, determining that the underlying storage array platform can be rolled back to a previously known good state for performing the replication workflow, performing a rollback of the underlying storage array platform to the previously known good state, and performing the recovery of the failed replication workflow.

## Claims

### Claim 1

A method comprising:
monitoring, by a computing device, a replication workflow execution on a storage system; and
responsive to a detection of a failure of the replication workflow, by the computing device:
determining whether the failure is in a Software Defined Network Attached Storage (SDNAS) or in an underlying storage array platform; and
responsive to a determination that the failure is in the SDNAS:
validating a health of the SDNAS for performing the replication workflow; and
responsive to validating the health of the SDNAS, performing a recovery of the failed replication workflow.

### Claim 2 (depends on 1)

The method of claim 1, wherein the validating a health of the SDNAS for performing the replication workflow includes checking one or more components of the SDNAS which are needed to perform the replication workflow.

### Claim 3 (depends on 1)

The method of claim 1, further comprising, responsive to failing to validate the health of the SDNAS for performing the replication workflow, reporting an original error associated with the failure of the replication workflow in the SDNAS.

### Claim 4 (depends on 1)

The method of claim 1, wherein performing recovery of the failed replication workflow includes attempting forward execution of the replication workflow from a failed replication operation in the replication workflow.

### Claim 5 (depends on 1)

The method of claim 1, further comprising reporting a result of the recovery of the failed replication workflow.

### Claim 6 (depends on 1)

The method of claim 1, wherein determining whether the failure is in the underlying storage array platform includes determining whether the failure is in a data replication facility of the underlying storage array platform.

### Claim 7 (depends on 1)

The method of claim 1, further comprising:
responsive to a determination that the failure is in the underlying storage array platform:
determining whether the underlying storage array platform can be rolled back to a previously known good state for performing the replication workflow; and
responsive to a determination that the underlying storage array platform can be rolled back to the previously known good state:
performing a rollback of the underlying storage array platform to the previously known good state; and
performing the recovery of the failed replication workflow.

### Claim 8 (depends on 7)

The method of claim 7, wherein the determining whether the underlying storage array platform can be rolled back to the previously known good state includes determining whether a data replication facility of the underlying storage array platform is available.

### Claim 9 (depends on 7)

The method of claim 7, further comprising, responsive to the determination that the failure is in the underlying storage array platform, responsive to a determination that the replication workflow is an unplanned failover, performing the recovery of the failed replication workflow without the rollback of the underlying storage array platform to the previously known good state.

### Claim 10 (depends on 7)

The method of claim 7, further comprising, responsive to a determination that the underlying storage array platform cannot be rolled back to the previously known good state, reporting an original error associated with the failure of the replication workflow in the underlying storage array platform.

### Claim 11 (depends on 7)

The method of claim 7, wherein the performing the recovery of the failed replication workflow responsive to the determination that the underlying storage array platform can be rolled back to the previously known good state includes retrying the failed replication workflow.

### Claim 12 (depends on 11)

The method of claim 11, further comprising reporting a result of the retrying of the failed replication workflow.

### Claim 13

A computing device comprising:
one or more non-transitory machine-readable mediums configured to store instructions; and
one or more processors configured to execute the instructions stored on the one or more non-transitory machine-readable mediums, wherein execution of the instructions causes the one or more processors to carry out a process comprising:
monitoring a replication workflow execution on a storage system; and
responsive to a detection of a failure of the replication workflow:
determining whether the failure is in a Software Defined Network Attached Storage (SDNAS) or in an underlying storage array platform; and
responsive to a determination that the failure is in the SDNAS:
validating a health of the SDNAS for performing the replication workflow; and
responsive to validating the health of the SDNAS, performing a recovery of the failed replication workflow.

### Claim 14 (depends on 13)

The computing device of claim 13, wherein the validating a health of the SDNAS for performing the replication workflow includes checking one or more components of the SDNAS which are needed to perform the replication workflow.

### Claim 15 (depends on 13)

The computing device of claim 13, wherein performing the recovery of the failed replication workflow includes attempting forward execution of the replication workflow from a failed replication operation in the replication workflow.

### Claim 16 (depends on 13)

The computing device of claim 13, wherein determining whether the failure is in the underlying storage array platform includes determining whether the failure is in a data replication facility of the underlying storage array platform.

### Claim 17 (depends on 13)

The computing device of claim 13, wherein the process further comprises:
responsive to a determination that the failure is in the underlying storage array platform:
determining whether the underlying storage array platform can be rolled back to a previously known good state for performing the replication workflow; and
responsive to a determination that the underlying storage array platform can be rolled back to the previously known good state:
performing a rollback of the underlying storage array platform to the previously known good state; and
performing the recovery of the failed replication workflow.

### Claim 18 (depends on 17)

The computing device of claim 17, wherein the determining whether the underlying storage array platform can be rolled back to the previously known good state includes determining whether a data replication facility of the underlying storage array platform is available.

### Claim 19 (depends on 17)

The computing device of claim 17, wherein the process further comprises, responsive to the determination that the failure is in the underlying storage array platform, responsive to a determination that the replication workflow is an unplanned failover, performing the recovery of the failed replication workflow without the rollback of the underlying storage array platform to the previously known good state.

### Claim 20

A non-transitory machine-readable medium encoding instructions that when executed by one or more processors cause a process to be carried out, the process including:
monitoring a replication workflow execution on a storage system; and
responsive to a detection of a failure of the replication workflow:
determining whether the failure is in a Software Defined Network Attached Storage (SDNAS) or in an underlying storage array platform;
responsive to a determination that the failure is in the SDNAS:
validating a health of the SDNAS for performing the replication workflow; and
responsive to validating the health of the SDNAS, performing a recovery of the failed replication workflow; and
responsive to a determination that the failure is in the underlying storage array platform:
determining whether the underlying storage array platform can be rolled back to a previously known good state for performing the replication workflow; and
responsive to a determination that the underlying storage array platform can be rolled back to the previously known good state:
performing a rollback of the underlying storage array platform to the previously known good state; and
performing the recovery of the failed replication workflow.
