SMART DYNAMIC RESTORE FOR KUBERNETES BASED APPLICATIONS

• US 20200133795A1
• Filed: 10/26/2018
• Published: 04/30/2020
• Est. Priority Date: 10/26/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: Rhodes, Michael, Natanzon, Assaf, Al-Alem, Luay, Bett, Antony
• Granted Patent: US 10,936,444 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 11/1461 Backup scheduling policy
• CPC Class Codes: G06F 11/1464 for networked environments
• CPC Class Codes: G06F 11/1469 Backup restoration techniques
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects
• CPC Class Codes: H04L 41/0894 Policy-based network configuration management
• CPC Class Codes: H04L 41/5025 by proactively reacting to service quality change, e.g. by reconfiguration after service quality degradation or upgrade
• CPC Class Codes: H04L 41/5058 Service discovery by the service manager
• CPC Class Codes: H04L 41/5096 wherein the managed service relates to distributed or central networked applications
• CPC Class Codes: H04L 43/0876 Network utilisation, e.g. volume of load or congestion level
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• 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/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services

Abstract

One example method includes discovering an application topology, discovering relationships between microservices that are elements of the application topology, ranking the microservices, identifying one or more of the microservices as a persistency microservice, selecting one or more persistency microservices for backup, and defining a backup policy based on the microservice relationships, the microservice rankings, and the selected persistent microservices. A backup operation is then performed that includes backing up persistent data and/or persistent metadata generated and/or modified by one or more of the persistency microservices.

Claims

1. A non-transitory storage medium having stored therein computer-executable instructions which, when executed by one or more hardware processors, perform the following operations:

discovering an application topology;

discovering relationships between microservices that comprise elements of the application topology;

ranking the microservices;

identifying one or more of the microservices as a persistency microservice;

selecting one or more persistency microservices for backup; and

defining a backup policy based on the microservice relationships, the microservice rankings, and the selected persistent microservices.

2. The non-transitory storage medium as recited in claim 1, wherein the microservices are ranked according to their importance relative to each other.

3. The non-transitory storage medium as recited in claim 1, wherein, in operation, one of the persistency microservices generates new and/or modified data and/or metadata that is persistently stored.

4. The non-transitory storage medium as recited in claim 1, wherein discovery of the application topology is performed with a platform application program interface (API).

5. The non-transitory storage medium as recited in claim 1, wherein the platform API is a Kubernetes API.

6. The non-transitory storage medium as recited in claim 1, wherein discovering relationships between microservices comprises discovering whether a microservice is dependent upon, or independent of, another microservice.

7. The non-transitory storage medium as recited in claim 1, wherein discovery of relationships between microservices is performed with a service mesh.

8. The non-transitory storage medium as recited in claim 1, wherein the application topology is a topology of a cloud native application.

9. The non-transitory storage medium as recited in claim 1, wherein the operations further comprise performing a backup operation based on the backup policy.

10. The non-transitory storage medium as recited in claim 1, wherein performing the backup operation comprises backing up persistent data and/or persistent metadata generated and/or modified by one or more of the persistency microservices.

11. A non-transitory storage medium having stored therein computer-executable instructions which, when executed by one or more hardware processors, perform the following operations:

detecting respective rankings of each of a plurality of microservices; and

defining a restore policy concerning the microservices, wherein defining the restore policy comprises;

specifying a restore order for the microservices;

identifying microservices that are candidates for restoration; and

specifying timing of a restore for each of the candidates.

12. The non-transitory storage medium as recited in claim 11, wherein the microservices are ranked according to their importance relative to each other, and the operations further comprise restoring the candidates in order of their rank.

13. The non-transitory storage medium as recited in claim 11, wherein each of the restore candidates is a persistency microservice that is associated with respective persistent data and/or persistent metadata.

14. The non-transitory storage medium as recited in claim 11, wherein the operations further comprise restoring the restore candidates according to the restore policy.

15. The non-transitory storage medium as recited in claim 14, wherein restoring the restore candidates comprises restoring a failed persistency microservice before the persistency microservice impairs operation of an application of which that persistency microservice is an element.

16. The non-transitory storage medium as recited in claim 14, wherein restoring the restore candidates comprises restoring multiple microservices together.

17. The non-transitory storage medium as recited in claim 14, wherein restoring the restore candidates comprises restoring one of the restore candidates directly from secondary storage.

18. The non-transitory storage medium as recited in claim 14, wherein as between first and second restore candidates, the first restore candidate is more likely to be used by an application before the second restore candidate is likely to be used by the application, and restoring the restore candidates comprises restoring the first restore candidate before restoring the second restore candidate.

19. The non-transitory storage medium as recited in claim 14, wherein restoring the restore candidates comprises restoring less than all of the microservices.

20. The non-transitory storage medium as recited in claim 14, wherein one of the restore candidates is run from protection storage prior to being restored to primary storage.