System and method for high priority backup

• US 10,509,587 B2
• Filed: 04/24/2018
• Issued: 12/17/2019
• Est. Priority Date: 04/24/2018
• Status: Active Grant

• Current Assignee: Emc IP Holding Company LLC (Dell Technologies Inc.)
• Original Assignee: Emc IP Holding Company LLC (Dell Technologies Inc.)
• Inventors: Chopra, Shelesh, Kulkarni, Gururaj
• Primary Examiner(s): Rones, Charles
• Assistant Examiner(s): Li, Hewy H
• Application Number:
  US15/960,715
• Publication Number:
  US 20190324653A1
• Time in Patent Office: 602 Days
• CPC Class Codes: G06F 11/1456 Hardware arrangements for backup
• CPC Class Codes: G06F 11/1464 for networked environments
• CPC Class Codes: G06F 12/0866 for peripheral storage systems, e.g. disk cache
• CPC Class Codes: G06F 12/0868 Data transfer between cache memory and other subsystems, e.g. storage devices or host systems
• CPC Class Codes: G06F 12/0888 using selective caching, e.g. bypass
• CPC Class Codes: G06F 2212/1044 Space efficiency improvement
• CPC Class Codes: G06F 3/0604 Improving or facilitating administration, e.g. storage management
• CPC Class Codes: G06F 3/0641 De-duplication techniques
• CPC Class Codes: G06F 3/065 Replication mechanisms
• CPC Class Codes: G06F 3/0659 Command handling arrangements, e.g. command buffers, queues, command scheduling
• CPC Class Codes: G06F 3/067 Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
• CPC Class Codes: H04L 67/1008 based on parameters of servers, e.g. available memory or workload monitoring of computer activity G06F11/30
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching

Abstract

A coordination point for assigning clients to remote backup storages includes a persistent storage and a processor. The persistent storage stores gateway pool cache capacities of the remote backup storages. The processor obtains a data storage request for data from a client of the clients; obtains an indirect cache estimate for servicing the data storage request; selects a remote backup storage of the remote backup storages based on the obtained indirect cache estimate using the gateway pool cache capacities; and assign the selected remote backup storage to service the data storage request. The selected remote backup storage has a higher client load at a time selection than a second client load of a second remote backup storage of the remote backup storages.

Claims

1. A coordination point for assigning clients to remote backup storages, comprising:

a persistent storage storing gateway pool cache capacities of the remote backup storages; and

a processor programmed to;

obtain a data storage request for data from a client of the clients;

obtain an indirect cache estimate for servicing the data storage request;

select a remote backup storage of the remote backup storages based on the obtained indirect cache estimate using the gateway pool cache capacities; and

assign the selected remote backup storage to service the data storage request,

wherein the selected remote backup storage has a higher client load at a time of the selection of the remote backup storage than a second client load of a second remote backup storage of the remote backup storages.

2. The coordination point of claim 1, wherein the processor is further programmed to:

obtain a second data storage request for second data from a second client of the clients;

obtain a second indirect cache estimate for servicing the second data storage request;

make a determination that none of the remote backup storages have sufficient cache based on the obtained second indirect cache estimate using the gateway pool cache capacities;

in response to the determination;

assign a gateway to a third remote data storage;

select the third remote backup storage after assigning the gateway; and

assign the selected third remote backup storage to service the second data storage request.

3. The coordination point of claim 2, wherein assigning the gateway to the third remote data storage comprises:

selecting an unassigned gateway; and

distributing a portion of a distributed cache of the third remote data storage across a cache of the unassigned gateway.

4. The coordination point of claim 2, wherein assigning the gateway to the third remote data storage comprises:

selecting an assigned gateway of a fourth remote data storage;

removing a portion of a distributed cache of the fourth remote data storage from a cache of the selected assigned gateway; and

distributing a portion of a distributed cache of the third remote data storage across the cache of the assigned gateway.

5. The coordination point of claim 1, wherein the processor is further programmed to:

obtain a notification from the selected remote backup storage that the obtained indirect cache estimate underestimated an actual cache use by the client;

in response to the notification;

assign a gateway to the selected remote backup storage; and

distribute a portion of a distributed cache of the selected remote data storage across a cache of the gateway.

6. The coordination point of claim 5, wherein the gateway was assigned to a third remote data storage before being assigned to the selected remote data storage.

7. The coordination point of claim 1, wherein the gateway pool cache capacities specifies cache capacities of distributed caches of the remote data storages.

8. The coordination point of claim 7, wherein each respective distributed cache is hosted by a plurality of gateways of a respective remote data storage of the remote data storages.

9. The coordination point of claim 1, wherein obtaining the indirect cache estimate for servicing the data storage request comprises:

identifying a type of application generating the data.

10. The coordination point of claim 9, wherein obtaining the indirect cache estimate for servicing the data storage request further comprises:

identifying a transaction rate of the identified type of application generating the data.

11. The coordination point of claim 1, wherein obtaining the indirect cache estimate for servicing the data storage request comprises:

identifying a computing resource capacity of the client.

12. The coordination point of claim 1, wherein obtaining the indirect cache estimate for servicing the data storage request comprises:

identifying an average available bandwidth between the client and the remote backup storages.

13. The coordination point of claim 1, wherein selecting the remote backup storage of the remote backup storages based on the obtained indirect cache estimate using the gateway pool cache capacities comprises:

identifying a portion of the remote backup storages that have an available cache capacity that is larger than the obtained indirect cache estimate.

14. The coordination point of claim 13, wherein selecting the remote backup storage of the remote backup storages based on the obtained indirect cache estimate using the gateway pool cache capacities further comprises:

identifying a remote backup storage of the portion of the remote backup storages that has a smallest client load; and

using the identified remote backup storage of the portion of the remote backup storages as the selected remote backup storage.

15. The coordination point of claim 1, wherein the client load of the selected remote backup storage is a cardinality of a number of clients assigned to the selected remote backup storage.

16. The coordination point of claim 1, wherein the client load of the selected remote backup storage is a quantity of computing resources utilized by a number of the clients assigned to the selected remote backup storage.

17. A method of operating a coordination point for assigning clients to remote backup storages, comprising:

obtaining a data storage request for data from a client of the clients;

obtaining an indirect cache estimate for servicing the data storage request;

selecting a remote backup storage of the remote backup storages based on the obtained indirect cache estimate using gateway pool cache capacities of the remote backup storages; and

assigning the selected remote backup storage to service the data storage request,

wherein the selected remote backup storage has a higher client load at a time of the selection of the remote backup storage than a second client load of a second remote backup storage of the remote backup storages.

18. The method of claim 17, further comprising:

obtaining a second data storage request for second data from a second client of the clients;

obtaining a second indirect cache estimate for servicing the second data storage request;

making a determination that none of the remote backup storages have sufficient cache based on the obtained second indirect cache estimate using the gateway pool cache capacities;

in response to the determination;

assign a gateway to a third remote data storage;

selecting the third remote backup storage after assigning the gateway; and

assigning the selected third remote backup storage to service the second data storage request.

19. 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 for assigning clients to remote backup storages, the method comprising:

obtaining a data storage request for data from a client of the clients;

obtaining an indirect cache estimate for servicing the data storage request;

selecting a remote backup storage of the remote backup storages based on the obtained indirect cache estimate using gateway pool cache capacities of the remote backup storages; and

assigning the selected remote backup storage to service the data storage request,

wherein the selected remote backup storage has a higher client load at a time of the selection of the remote backup storage than a second client load of a second remote backup storage of the remote backup storages.

20. The non-transitory computer readable medium of claim 19, wherein the method further comprises:

obtaining a second data storage request for second data from a second client of the clients;

obtaining a second indirect cache estimate for servicing the second data storage request;

making a determination that none of the remote backup storages have sufficient cache based on the obtained second indirect cache estimate using the gateway pool cache capacities;

in response to the determination;

assign a gateway to a third remote data storage;

selecting the third remote backup storage after assigning the gateway; and

assigning the selected third remote backup storage to service the second data storage request.