Method and system to tag and route the striped backups to a single deduplication instance on a deduplication appliance

Patent metadata

Field	Value
Publication number	US-2020241971-A1
Application number	US-201916259469-A
Country	US
Kind code	A1
Filing date	Jan 28, 2019
Priority date	Jan 28, 2019
Publication date	Jul 30, 2020
Grant date	—

Abstract

A method for managing backups includes receiving, via a first backup stream, first data associated with a first tagged backup stripe, wherein the first tagged backup stripe is associated with a first routing tag, directing, based on the first routing tag, the first data to a first backup instance, receiving, via a second backup stream, second data associated with a second tagged backup stripe, wherein the second tagged backup stripe is associated with the first routing tag, directing, based on the first routing tag, the second data to the first backup instance, and performing, in the first backup instance, a deduplication operation on the first data and the second data.

First claim

What is claimed is:

1 . A method for managing backups, the method comprising:
receiving, via a first backup stream, first data associated with a first tagged backup stripe, wherein the first tagged backup stripe is associated with a first routing tag; directing, based on the first routing tag, the first data to a first backup instance; receiving, via a second backup stream, second data associated with a second tagged backup stripe, wherein the second tagged backup stripe is associated with the first routing tag; directing, based on the first routing tag, the second data to the first backup instance; and performing, in the first backup instance, a deduplication operation on the first data and the second data.

2 . The method of claim 1 , further comprising:
receiving, via a third backup stream, third data associated with a third tagged backup stripe, wherein the third tagged backup stripe is associated with a second routing tag; and directing, based on the second routing tag, the third data to a second backup instance.

3 . The method of claim 2 , further comprising:
performing, in the second backup instance, a second deduplication operation on the third data, wherein the second deduplication operation is performed independently of the first deduplication operation.

4 . The method of claim 1 , further comprising:
receiving, via a third backup stream, third data associated with a non-tagged backup stripe; and directing, based on a load balancing operation, the third data to a second backup instance.

5 . The method of claim 1 , further comprising:
receiving, via a third backup stream, third data associated with a non-tagged backup stripe; and directing, based on a load balancing operation, the third data to the first backup instance.

6 . The method of claim 1 , further comprising:
prior to receiving the first data:
obtaining the first routing tag; and
associating the first routing tag with the first backup instance.

7 . The method of claim 1 , wherein the first routing tag is stored with the first data in the first backup instance.

8 . A non-transitory computer readable medium comprising computer readable program code, which when executed by a computer processor enables the computer processor to perform a method, the method comprising:
receiving, via a first backup stream, first data associated with a first tagged backup stripe, wherein the first tagged backup stripe is associated with a first routing tag; directing, based on the first routing tag, the first data to a first backup instance; receiving, via a second backup stream, second data associated with a second tagged backup stripe, wherein the second tagged backup stripe is associated with the first routing tag; directing, based on the first routing tag, the second data to the first backup instance; and performing, in the first backup instance, a first deduplication operation on the first data and the second data.

9 . The non-transitory computer readable medium of claim 8 , further comprising:
receiving, via a third backup stream, third data associated with a third tagged backup stripe, wherein the third tagged backup stripe is associated with a second routing tag; and directing, based on the second routing tag, the third data to a second backup instance.

10 . The non-transitory computer readable medium of claim 9 , further comprising:
performing, in the second backup instance, a second deduplication operation on the third data, wherein the second deduplication operation is performed independently of the first deduplication operation.

11 . The non-transitory computer readable medium of claim 8 , further comprising:
receiving, via a third backup stream, third data associated with a non-tagged backup stripe; and directing, based on a load balancing operation, the third data to a second backup instance.

12 . The non-transitory computer readable medium of claim 8 , further comprising:
receiving, via a third backup stream, third data associated with a non-tagged backup stripe; and directing, based on a load balancing operation, the third data to the first backup instance.

13 . The non-transitory computer readable medium of claim 8 , further comprising:
prior to receiving the first data:
obtaining the first routing tag; and
associating the first routing tag with the first backup instance.

14 . The non-transitory computer readable medium of claim 8 , wherein the first routing tag is stored with the first data in the first backup instance.

15 . A system, comprising:
a processor; a database; memory comprising instructions which when executed by the processor perform a method, the method comprising:
receiving, via a first backup stream, first data associated with a first tagged backup stripe, wherein the first tagged backup stripe is associated with a first routing tag;
directing, based on the first routing tag, the first data to a first backup instance;
receiving, via a second backup stream, second data associated with a second tagged backup stripe, wherein the second tagged backup stripe is associated with the first routing tag;
directing, based on the first routing tag, the second data to the first backup instance; and
performing, in the first backup instance, a first deduplication operation on the first data and the second data.

16 . The system of claim 15 , wherein the method further comprises:
receiving, via a third backup stream, third data associated with a third tagged backup stripe, wherein the third tagged backup stripe is associated with a second routing tag; and directing, based on the second routing tag, the third data to a second backup instance.

17 . The system of claim 16 , wherein the method further comprises:
performing, in the second backup instance, a second deduplication operation on the third data, wherein the second deduplication operation is performed independently of the first deduplication operation.

18 . The system of claim 15 , wherein the method further comprises:
receiving, via a third backup stream, third data associated with a non-tagged backup stripe; and directing, based on a load balancing operation, the third data to a second backup instance.

19 . The system of claim 15 , wherein the method further comprises:
receiving, via a third backup stream, third data associated with a non-tagged backup stripe; and directing, based on a load balancing operation, the third data to the first backup instance.

20 . The system of claim 15 , wherein the method further comprises:
prior to receiving the first data:
obtaining the first routing tag; and
associating the first routing tag with the first backup instance.

Assignees

• Emc Ip Holding Co Llc

Inventors

• Madan Nitin
• Viswanathan Srikant
• Godbole Kedar Sadanand

Classifications

• G06F11/1453 Primary

  using de-duplication of the data · CPC title

• G06F11/1451 Primary

  by selection of backup contents · CPC title

• H04L67/1095

  Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes · CPC title

• H04L45/50

  using label swapping, e.g. multi-protocol label switch [MPLS] · CPC title

• G06F3/0641

  De-duplication techniques · CPC title