US 10,896,101 B2Granted

Multiclient backup replication apparatuses, methods and systems

AssigneeDatto, Inc.

InventorDesmond Wayne Yeung

Life of this patent

Estimating the term…

Loading patent…

Abstract

The Multiclient Backup Replication Apparatuses, Methods and Systems (“MBR”) transforms pairing request, replication data stream inputs via MBR components into pairing response, replication confirmation outputs. A replication notification for a snapshot of a backup volume at a source node is obtained. A source node named pipe for the snapshot is created. A priority for the snapshot is determined. When appropriate to send the snapshot to a replication target node, snapshot data is read from the source node named pipe and serialized into chunks Chunks associated with the snapshot and other snapshots are multiplexed into a replication data stream and sent to the replication target node via a persistent network connection. The replication data stream is received by the replication target node and chunks associated with the snapshot are deserialized. A replication target node named pipe for the snapshot is created and used to write snapshot data to a replication volume.

Claims18

Dependent claims

A multi-client snapshot replicating apparatus, comprising:

a memory;
a component collection in the memory, including:
a source replication component, and
a target replication component;
a processor disposed in communication with the memory, and configured to issue a plurality of processing instructions from the component collection stored in the memory,
wherein the processor issues instructions from the source replication component, stored in the memory, to:
obtain, via at least one processor, a replication notification associated with a snapshot of a backup volume at a source node;
determine, via at least one processor, a replication target node associated with the replication notification;
create, via at least one processor, a source node named pipe associated with the snapshot, wherein the source node named pipe is configured to facilitate reading snapshot data of the snapshot from the backup volume;
determine, via at least one processor, a snapshot priority for the snapshot, wherein snapshot priority determines how to order snapshot data from a plurality of snapshots for replication from the source node to the replication target node;
determine, via at least one processor, that the snapshot priority of the snapshot indicates that it is time to send the snapshot to the replication target node;
serialize, via at least one processor, snapshot data of the snapshot, read from the source node named pipe, into one or more chunks;
multiplex, via at least one processor, the one or more chunks associated with the snapshot and one or more chunks associated with one or more other snapshots from the plurality of snapshots into a replication data stream;
and
send, via at least one processor, the replication data stream to the replication target node via a persistent network connection between the source node and the replication target node;
wherein the processor issues instructions from the target replication component, stored in the memory, to:
receive, via at least one processor, the replication data stream;
deserialize, via at least one processor, a first chunk associated with the snapshot received via the replication data stream;
determine, via at least one processor, a replication volume associated with the snapshot at the replication target node based on the first chunk's payload;
create, via at least one processor, a replication target node named pipe associated with the snapshot, wherein the replication target node named pipe is configured to facilitate writing snapshot data of the snapshot to the replication volume;
deserialize, via at least one processor, a second chunk associated with the snapshot received via the replication data stream;
and
write, via at least one processor, to the replication target node named pipe snapshot data of the snapshot provided in the second chunk's payload.

20 more elements

A processor-readable multi-client snapshot replicating non-transient physical medium storing processor-executable components, the components, comprising:

a component collection stored in the medium, including:
a source replication component, and
a target replication component;
wherein the source replication component, stored in the medium, includes processor-issuable instructions to:
obtain, via at least one processor, a replication notification associated with a snapshot of a backup volume at a source node;
determine, via at least one processor, a replication target node associated with the replication notification;
create, via at least one processor, a source node named pipe associated with the snapshot, wherein the source node named pipe is configured to facilitate reading snapshot data of the snapshot from the backup volume;
determine, via at least one processor, a snapshot priority for the snapshot, wherein snapshot priority determines how to order snapshot data from a plurality of snapshots for replication from the source node to the replication target node;
determine, via at least one processor, that the snapshot priority of the snapshot indicates that it is time to send the snapshot to the replication target node;
serialize, via at least one processor, snapshot data of the snapshot, read from the source node named pipe, into one or more chunks;
multiplex, via at least one processor, the one or more chunks associated with the snapshot and one or more chunks associated with one or more other snapshots from the plurality of snapshots into a replication data stream;
and
send, via at least one processor, the replication data stream to the replication target node via a persistent network connection between the source node and the replication target node;
wherein the target replication component, stored in the medium, includes processor-issuable instructions to:
receive, via at least one processor, the replication data stream;
deserialize, via at least one processor, a first chunk associated with the snapshot received via the replication data stream;
determine, via at least one processor, a replication volume associated with the snapshot at the replication target node based on the first chunk's payload;
create, via at least one processor, a replication target node named pipe associated with the snapshot, wherein the replication target node named pipe is configured to facilitate writing snapshot data of the snapshot to the replication volume;
deserialize, via at least one processor, a second chunk associated with the snapshot received via the replication data stream;
and
write, via at least one processor, to the replication target node named pipe snapshot data of the snapshot provided in the second chunk's payload.

18 more elements

A processor-implemented multi-client snapshot replicating system, comprising:

a source replication component means, to:
obtain, via at least one processor, a replication notification associated with a snapshot of a backup volume at a source node;
determine, via at least one processor, a replication target node associated with the replication notification;
create, via at least one processor, a source node named pipe associated with the snapshot, wherein the source node named pipe is configured to facilitate reading snapshot data of the snapshot from the backup volume;
determine, via at least one processor, a snapshot priority for the snapshot, wherein snapshot priority determines how to order snapshot data from a plurality of snapshots for replication from the source node to the replication target node;
determine, via at least one processor, that the snapshot priority of the snapshot indicates that it is time to send the snapshot to the replication target node;
serialize, via at least one processor, snapshot data of the snapshot, read from the source node named pipe, into one or more chunks;
multiplex, via at least one processor, the one or more chunks associated with the snapshot and one or more chunks associated with one or more other snapshots from the plurality of snapshots into a replication data stream;
and
send, via at least one processor, the replication data stream to the replication target node via a persistent network connection between the source node and the replication target node;
a target replication component means, to:
receive, via at least one processor, the replication data stream;
deserialize, via at least one processor, a first chunk associated with the snapshot received via the replication data stream;
determine, via at least one processor, a replication volume associated with the snapshot at the replication target node based on the first chunk's payload;
create, via at least one processor, a replication target node named pipe associated with the snapshot, wherein the replication target node named pipe is configured to facilitate writing snapshot data of the snapshot to the replication volume;
deserialize, via at least one processor, a second chunk associated with the snapshot received via the replication data stream;
and
write, via at least one processor, to the replication target node named pipe snapshot data of the snapshot provided in the second chunk's payload.

15 more elements

A processor-implemented multi-client snapshot replicating method, comprising:

executing processor-implemented source replication component instructions to:
obtain, via at least one processor, a replication notification associated with a snapshot of a backup volume at a source node;
determine, via at least one processor, a replication target node associated with the replication notification;
create, via at least one processor, a source node named pipe associated with the snapshot, wherein the source node named pipe is configured to facilitate reading snapshot data of the snapshot from the backup volume;
determine, via at least one processor, a snapshot priority for the snapshot, wherein snapshot priority determines how to order snapshot data from a plurality of snapshots for replication from the source node to the replication target node;
determine, via at least one processor, that the snapshot priority of the snapshot indicates that it is time to send the snapshot to the replication target node;
serialize, via at least one processor, snapshot data of the snapshot, read from the source node named pipe, into one or more chunks;
multiplex, via at least one processor, the one or more chunks associated with the snapshot and one or more chunks associated with one or more other snapshots from the plurality of snapshots into a replication data stream;
and
send, via at least one processor, the replication data stream to the replication target node via a persistent network connection between the source node and the replication target node;
executing processor-implemented target replication component instructions to:
receive, via at least one processor, the replication data stream;
deserialize, via at least one processor, a first chunk associated with the snapshot received via the replication data stream;
determine, via at least one processor, a replication volume associated with the snapshot at the replication target node based on the first chunk's payload;
create, via at least one processor, a replication target node named pipe associated with the snapshot, wherein the replication target node named pipe is configured to facilitate writing snapshot data of the snapshot to the replication volume;
deserialize, via at least one processor, a second chunk associated with the snapshot received via the replication data stream;
and
write, via at least one processor, to the replication target node named pipe snapshot data of the snapshot provided in the second chunk's payload.

15 more elements

Dependencies are inferred from the claim text.

Facts

Application: 16/424,469Filed 28 May 2019 · continuation in part
Priority: 7 Aug 2017
Published: US 2020/0057697 A120 Feb 2020
Granted: 19 Jan 2021
Term ends: Not estimatedThe source records don’t support an estimate.

Classification7 codes

G06F 11/1451
Management of the data involved in backup or backup restore: by selection of backup contents
G06F 11/1469
Management of the backup or restore process: backup restoration techniques
G06F 9/542
Interprogram communication: event management; Broadcasting; Multicasting; Notifications
G06F 11/1464
Management of the backup or restore process: for networked environments

Family

Application62/541,952Us provisional application · filed 7 Aug 2017
Application16/055,347Parent of this continuation-in-part · filed 6 Aug 2018
Application16/391,243Parent of this continuation-in-part · filed 22 Apr 2019
Application16/391,205Parent of this continuation-in-part · filed 22 Apr 2019
US 2020/0057697 A1Pre-grant publication · published 20 Feb 2020
US 10,884,871 B2Related patent
US 10,915,407 B2Related patent
US 11,093,344 B2Related patent
US 2019/0042373 A1Published application
US 2019/0250995 A1Published application
US 2019/0391878 A1Published application
US 10,896,101 B2This patent

From the US filing history. Foreign family members aren’t listed.