Remote snappable linking

Patent metadata

Field	Value
Publication number	US-11748214-B2
Application number	US-202217567946-A
Country	US
Kind code	B2
Filing date	Jan 4, 2022
Priority date	Jan 15, 2021
Publication date	Sep 5, 2023
Grant date	Sep 5, 2023

Abstract

In some examples, a duster comprises peer nodes and a distributed data store implemented across the peer nodes, a method of remote linking of data objects for data transfer between a first node cluster and a second node cluster among the peer nodes; the method comprising: creating a data object group including multiple remote data objects, wherein a plurality of remote data objects in the data object group represent a same first virtual machine and are registrable on at least the first and second node clusters of the peer DMS nodes; creating or identifying remote links to a plurality of the remote data objects in the data object group; designating a member of the data object group as an active member of the group; and assigning a task to the active member to be completed using remote links.

First claim

What is claimed is:

1. A method, comprising:
creating a first data object group including a plurality of remote data objects that represent a same first virtual machine and are registrable on at least a first node cluster and a second node cluster of a set of peer DMS nodes;
creating, in the second node cluster, a second data object group comprising a first remote link to a first remote data object associated with the first virtual machine and a second remote link to a second remote snappable relating to a second virtual machine;
designating the second virtual machine as an overall active member of the first data object group and the second data object group; and
assigning a task to the overall active member to be completed using the first remote link and the second remote link, wherein the task is associated with a failover operation or an instant recovery of the first virtual machine.

2. The method of claim 1 , further comprising:
storing, based on a backup request or a replication request relating to the second virtual machine, a backup of the second virtual machine incrementally on top of replicated snapshots of the first virtual machine.

3. The method of claim 2 , wherein the first node cluster is a source cluster; and wherein the task includes a backup job or a replication job associated with a source cluster refresh, the method further comprising:
identifying the second data object group in the second node cluster created during the failover operation or the instant recovery of the first virtual machine;
recognizing an equivalent data object group in the first node cluster; and
performing the source cluster refresh incrementally based on the recognizing.

4. The method of claim 1 , further comprising:
resolving, based at least in part on the designating, a discrepancy in a designation of the overall active member in response to an identification of a new member of the first data object group.

5. The method of claim 1 , wherein the first data object group further comprises at least one local data object; and wherein the method further comprises:
linking data objects together based on an elevated level of trust assigned to the at least one local data object.

6. A cluster, comprising:
a set of peer DMS nodes comprising a first node cluster and a second node cluster; and
a distributed data store implemented across the set of peer DMS nodes, wherein the set of peer DMS nodes is configured to:
create a first data object group including a plurality of remote data objects that represent a same first virtual machine and are registrable on at least the first node cluster and the second node cluster;
create, in the second node cluster, a second data object group comprising a first remote link to a first remote data object associated with the first virtual machine and a second remote link to a second remote snappable relating to a second virtual machine;

designate the second virtual machine as an overall active member of the first data object group and the second data object group; and
assign a task to the overall active member to be completed using remote links the first remote link and the second remote link, wherein the task is associated with a failover operation or an instant recovery of the first virtual machine.

7. The cluster of claim 6 , wherein the set of peer DMS nodes is further configured to:
store, based on a backup request or a replication request relating to the second virtual machine, a backup of the second virtual machine incrementally on top of replicated snapshots of the first virtual machine.

8. The cluster of claim 7 , wherein the first node cluster is a source cluster, wherein the task includes a backup job or a replication job associated with a source cluster refresh, and wherein the set of peer DMS nodes is further configured to:
identify the second data object group in the second node cluster created during the failover operation or the instant recovery of the first virtual machine;
recognize an equivalent data object group in the first node cluster; and
perform the source cluster refresh incrementally based on the recognizing.

9. The cluster of claim 6 , wherein the set of peer DMS nodes is further configured to:
resolve, based at least in part on the designating, a discrepancy in a designation of the overall active member in response to an identification of a new member of the first data object group.

10. The cluster of claim 6 , wherein the first data object group further comprises at least one local data object, and wherein the set of peer DMS nodes is further configured to:
link data objects together based on an elevated level of trust assigned to the at least one local data object.

11. A non-transitory, machine-readable medium comprising instructions which, when executed by a processor of a machine, cause the machine to:
create a first data object group including a plurality of remote data objects that represent a same first virtual machine and are registrable on at least a first node cluster and a second node clusters cluster of a set of peer DMS nodes;
create, in the second node cluster, a second data object group comprising a first remote link to a first remote data object associated with the first virtual machine and a second remote link to a second remote snappable relating to a second virtual machine;
designate the second virtual machine as an overall active member of the first data object group and the second data object group; and
assign a task to the overall active member to be completed using the first remote link and the second remote link, wherein the task is associated with a failover operation or an instant recovery of the first virtual machine.

12. The non-transitory, machine-readable medium of claim 11 , wherein the instructions are further executable by the processor to cause the machine to:
store, based on a backup request or a replication request relating to the second virtual machine, a backup of the second virtual machine incrementally on top of replicated snapshots of the first virtual machine.

13. The non-transitory, machine-readable medium of claim 12 , wherein the first node cluster is a source cluster; and wherein the task includes a backup job or a replication job associated with a source cluster refresh, and
wherein the instructions are further executable by the processor to cause the machine to:
identify the second data object group in the second node cluster created during the failover operation or the instant recovery of the first virtual machine;
recognize an equivalent data object group in the first node cluster; and
perform the source cluster refresh incrementally based on the recognizing.

14. The non-transitory, machine-readable medium of claim 11 , wherein the instructions are further executable by the processor to cause the machine to:
resolve, based at least in part on the designating, a discrepancy in a designation of the overall active member in response to an identification of a new member of the first data object group.

15. The non-transitory, machine-readable medium of claim 11 , wherein the first data object group further comprises at least one local data object; and
wherein the instructions are further executable by the processor to cause the machine to:
link data objects together based on an elevated level of trust assigned to the at least one local data object.

Assignees

• Rubrik Inc

Inventors

• AGRAWAL Rohit
• Malpani Mudit
• Sarkar Prasenjit

Classifications

• G06F11/1469 Primary

  Backup restoration techniques · CPC title

• G06F11/1451

  by selection of backup contents · CPC title

• G06F11/1464 Primary

  for networked environments · CPC title

• G06F11/1484

  involving virtual machines · CPC title

• G06F11/2023

  Failover techniques · CPC title