Remote snappable linking

Patent metadata

Field	Value
Publication number	US-11249865-B1
Application number	US-202117150130-A
Country	US
Kind code	B1
Filing date	Jan 15, 2021
Priority date	Jan 15, 2021
Publication date	Feb 15, 2022
Grant date	Feb 15, 2022

Abstract

In some examples, a data management and storage (DMS) cluster comprises peer DMS nodes and a distributed data store implemented across the peer DMS nodes. The peer DMS nodes are configured to collectively implement operations in a method of remote linking of snappables for data transfer between a first node cluster and a second node cluster among the peer DMS nodes.

First claim

What is claimed is:

1. In a data management and storage (DMS) cluster comprising peer DMS nodes and a distributed data store implemented across the peer DMS nodes, a method of remote linking of snappables for data transfer between a first node cluster and a second node cluster among the peer DMS nodes, the method comprising:
identifying the first node cluster;
identifying the second node cluster;
creating a snappable group including multiple remote snappables, each remote snappable representing a same first virtual machine, each remote snappable registrable on at least the first and second node clusters of the peer DMS nodes;
creating or identifying remote links to each of the remote snappables in the snappable group;
designating a single member of the snappable group as an overall active member of the group;
assigning, to the active member only, a backup or replication job of the virtual machine; and
based on the assigned job, backing up or replicating the virtual machine using the remote snappable links.

2. The method of claim 1 , wherein:
the backup or replication job is associated with a failover operation or an instant recovery of the first virtual machine; and
wherein the method further comprises:
creating, in the second cluster, a second snappable group comprising a first remote link to a first remote snappable associated with the first virtual machine, and a second remote link to a second remote snappable relating to a second virtual machine; and
designating the second virtual machine as the overall active member.

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

4. The method of claim 3 , wherein the first node cluster is a source cluster; and
wherein the backup or replication job is associated with a source cluster refresh (SCR), the method further comprising:
identifying the second snappable group in the second cluster created during the failover operation or instant recovery of the first virtual machine;
recognizing a same snappable group in the first node cluster; and
based on the recognition, performing the SCR incrementally.

5. The method of claim 1 , further comprising resolving a discrepancy in the designation of the overall active member in response to an identification of a new member of the snappable group.

6. The method of claim 1 , wherein the snappable group further comprises at least one local snappable; and
wherein the method further comprises linking snappables together based on an elevated level of trust assigned to the at least one local snappable.

7. A data management and storage (DMS) cluster, comprising:
peer DMS nodes; and
a distributed data store implemented across the peer DMS nodes, wherein the peer DMS nodes are configured to collectively implement operations in a method of remote linking of snappables for data transfer between a first node cluster and a second node cluster among the peer DMS nodes, the operations comprising:
identifying the first node cluster;
identifying the second node cluster;
creating a snappable group including multiple remote snappables, each remote snappable representing a same first virtual machine, each remote snappable registrable on at least the first and second node clusters of the peer DMS nodes;
creating or identifying remote links to each of the remote snappables in the snappable group;
designating a single member of the snappable group as an overall active member of the group;
assigning, to the active member only, a backup or replication job of the virtual machine; and
based on the assigned job, backing up or replicating the virtual machine using the remote snappable links.

8. The DMS cluster of claim 7 , wherein:
the backup or replication job is associated with a failover operation or an instant recovery of the first virtual machine; and wherein the operations further comprise:
creating, in the second cluster, a second snappable group comprising a first remote link to a first remote snappable associated with the first virtual machine, and a second remote link to a second remote snappable relating to a second virtual machine; and
designating the second virtual machine as the overall active member.

9. The DMS cluster of claim 8 , wherein the operations further comprise:
based on a backup or replication request relating to the second virtual machine, storing a backup of the second virtual machine incrementally on top of replicated snapshots of the first virtual machine.

10. The DMS cluster of claim 9 , wherein the first node cluster is a source cluster; and wherein
the backup or replication job is associated with a source cluster refresh (SCR); and wherein
the operations further comprise:
identifying the second snappable group in the second cluster created during the failover operation or instant recovery of the first virtual machine;
recognizing a same snappable group in the first node cluster; and
based on the recognition, performing the SCR incrementally.

11. The DMS cluster of claim 7 , wherein the operations further comprise resolving a discrepancy in the designation of the overall active member in response to an identification of a new member of the snappable group.

12. The DMS cluster of claim 7 , wherein the snappable group further comprises at least one local snappable; and wherein the operations further comprise linking snappables together based on an elevated level of trust assigned to the at least one local snappable.

13. A non-transitory machine-readable medium comprising instructions which, when executed by a machine, cause the machine to implement operations in a process at a data management and storage (DMS) cluster comprising peer DMS nodes and a distributed data store implemented across the peer DMS nodes, the process including a remote linking of snappables for data transfer between a first node cluster and a second node cluster among the peer DMS nodes, the operations comprising at least:
identifying the first node cluster;
identifying the second node cluster; creating a snappable group including multiple remote snappables, each remote snappable representing a same first virtual machine, each remote snappable registrable on at least the first and second node clusters of the peer DMS nodes;
creating or identifying remote links to each of the remote snappables in the snappable group;
designating a single member of the snappable group as an overall active member of the group;
assigning, to the active member only, a backup or replication job of the virtual machine; and
based on the assigned job, backing up or replicating the virtual machine using the remote snappable links.

14. The medium of claim 13 , wherein:
the backup or replication job is associated with a failover operation or an instant recovery of the first virtual machine; and wherein
the operations further comprise:
creating, in the second cluster, a second snappable group comprising a first remote link to a first remote snappable associated with the first virtual machine, and a second remote link to a second remote snappable relating to a second virtual machine; and
designating the second virtual machine as the overall active member.

15. The medium of claim 14 , wherein the operations further comprise:
based on a backup or replication request relating to the second virtual machine, storing a backup of the second virtual machine incrementally on top of replicated snapshots of the first virtual machine.

Assignees

• Rubrik Inc

Inventors

• AGRAWAL Rohit
• Malpani Mudit
• Sarkar Prasenjit

Classifications

• G06F11/2041

  with more than one idle spare processing component · CPC title

• G06F11/2028

  eliminating a faulty processor or activating a spare · CPC title

• G06F11/1484

  involving virtual machines · CPC title

• G06F11/1451

  by selection of backup contents · CPC title

• G06F2201/815

  Virtual · CPC title