# US 2018/0324252 A1 · Remote Cloud Backup of Data

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

- Number: US 2018/0324252 A1
- Document ID: US20180324252A1
- Status: Published application
- Kind: A1
- Application number: 16/034,448
- Filed: 2018-07-13
- Published: 2018-11-08
- Earliest claimed: 2002-08-27
- Assignees: AT&T Intellectual Property II, L.P.
- Applicants: AT&T Intellectual Property II, L.P.
- Inventors: James A. Gardner; Darrell G. Freeman
- Web page: https://patentgrep.com/patent/US20180324252A1

## CPC

- H04L 67/1097: 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]
- G06F 11/1443: {Transmit or communication errors}
- G06F 11/2064: {while ensuring consistency}
- G06F 11/2071: {using a plurality of controllers}
- H04L 43/10: Active monitoring, e.g. heartbeat, ping or trace-route
- H04L 67/1095: Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
- H04L 67/568: Storing data temporarily at an intermediate stage, e.g. caching
- H04L 69/28: Timers or timing mechanisms used in protocols
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Methods, systems, and products mirror data between local memory and remote storage. A write command is sent from a server to a remote storage device, and a timer is established. A current time of the timer is compared to a maximum time period. If the maximum time period expires without receipt of an acknowledgment to the write command, then a write error is assumed to exist to the remote storage device.

## Claims

### Claim 1

A method, comprising:
sending, by a device, a request for a cloud-based remote storage of data;
determining, by the device, a latency associated with the request for the cloud-based remote storage of the data;
determining, by the device, an expiration of the latency without a receipt of an acknowledgment for the cloud-based remote storage of the data; and
resubmitting, by the device, the request for the cloud-based remote storage of the data in response to the expiration of the latency.

### Claim 2 (depends on 1)

The method of claim 1, further comprising sending a ping command for the determining of the latency.

### Claim 3 (depends on 1)

The method of claim 1, further comprising retrieving the latency from a memory device.

### Claim 4 (depends on 1)

The method of claim 1, further comprising erasing a block of the data in response to the expiration of the latency.

### Claim 5 (depends on 1)

The method of claim 1, further comprising caching the data to a local storage device.

### Claim 6 (depends on 1)

The method of claim 1, further comprising initializing a timer that counts the latency.

### Claim 7 (depends on 6)

The method of claim 6, further comprising re-establishing the timer in response to the resubmitting of the request for the cloud-based remote storage of the data.

### Claim 8

A system, comprising:
a hardware processor; and
a memory device, the memory device storing instructions, the instructions when executed causing the hardware processor to perform operations, the operations comprising:
sending a request for a cloud-based remote storage of data;
determining a latency associated with the request for the cloud-based remote storage of the data;
determining an expiration of the latency without a receipt of an acknowledgment for the cloud-based remote storage of the data; and
resubmitting the request for the cloud-based remote storage of the data in response to the expiration of the latency.

### Claim 9 (depends on 8)

The system of claim 8, wherein the operations further comprise sending a ping command for the determining of the latency.

### Claim 10 (depends on 8)

The system of claim 8, wherein the operations further comprise retrieving the latency from a memory device.

### Claim 11 (depends on 8)

The system of claim 8, wherein the operations further comprise erasing a block of the data in response to the expiration of the latency.

### Claim 12 (depends on 8)

The system of claim 8, wherein the operations further comprise caching the data to a local storage device.

### Claim 13 (depends on 8)

The system of claim 8, wherein the operations further comprise initializing a timer that counts the latency.

### Claim 14 (depends on 13)

The system of claim 13, wherein the operations further comprise re-establishing the timer in response to the resubmitting of the request for the cloud-based remote storage of the data.

### Claim 15

A memory device storing instructions that when executed cause a hardware processor to perform operations, the operations comprising:
sending a request for a cloud-based remote storage of data;
determining a latency associated with the request for the cloud-based remote storage of the data;
determining an expiration of the latency without a receipt of an acknowledgment for the cloud-based remote storage of the data; and
resubmitting the request for the cloud-based remote storage of the data in response to the expiration of the latency.

### Claim 16 (depends on 15)

The memory device of claim 15, wherein the operations further comprise sending a ping command for the determining of the latency.

### Claim 17 (depends on 15)

The memory device of claim 15, wherein the operations further comprise retrieving the latency from a memory device.

### Claim 18 (depends on 15)

The memory device of claim 15, wherein the operations further comprise erasing a block of the data in response to the expiration of the latency.

### Claim 19 (depends on 15)

The memory device of claim 15, wherein the operations further comprise caching the data to a local storage device.

### Claim 20 (depends on 15)

The memory device of claim 15, wherein the operations further comprise initializing a timer that counts the latency.