Backup and restore framework for distributed computing systems

• US 10,379,968 B2
• Filed: 05/05/2017
• Issued: 08/13/2019
• Est. Priority Date: 05/05/2017
• Status: Active Grant

• Current Assignee: Pivotal Software, Inc. (Broadcom, Inc.)
• Original Assignee: Pivotal Software, Inc. (Broadcom, Inc.)
• Inventors: Stowell, Therese Louise, Dudala, Kalyan Chakravarthy, Humphreys, Colin Michael, Jones, Simon James, Naik, Jatin, Perez-Shirley, Alvaro, Stanley, Henry Arthur James
• Primary Examiner(s): Patel, Kamini B
• Application Number:
  US15/588,529
• Publication Number:
  US 20180322019A1
• Time in Patent Office: 830 Days
• Field of Search: 714 19
• CPC Class Codes: G06F 11/1451 by selection of backup contents
• CPC Class Codes: G06F 11/1458 Management of the backup or restore process
• CPC Class Codes: G06F 11/1469 Backup restoration techniques
• CPC Class Codes: G06F 2201/805 Real-time
• CPC Class Codes: G06F 2201/815 Virtual
• CPC Class Codes: G06F 2201/82 Solving problems relating to consistency
• CPC Class Codes: G06F 9/4843 by program, e.g. task dispatcher, supervisor, operating system

Abstract

Methods, systems, and computer readable media for backing up and restore a deployment on a cloud computing platform are described. A deployment on a cloud computing platform includes a set of virtual machines and corresponding disks. A deployment may include multiple subunits designated as deployment jobs. A respective job specification file specifies respective resources used by each deployment job. The resources include various scripts specifying actions to take before, during, and after a backup. A backup orchestrator, upon receiving a backup request for the deployment, executes the scripts in a pre-specified sequence ordered by script type. When a particular type of scripts executes, the corresponding script for each deployment job, if specified in the specification file to correspond to that type, executes. When all scripts of a particular type finish execution, scripts having a next type execute. Accordingly, the operations of backing up multiple deployment jobs are synchronized and orchestrated.

Claims

1. A method, comprising:

receiving, from a client device by a backup orchestrator comprising one or more computer processors, a request to perform a backup or restore process for a deployment including a plurality of different deployment jobs, the request being associated with a deployment identifier identifying the deployment;

determining, by the backup orchestrator and based on the deployment identifier, a script location storing job-specific scripts, each job-specific script being associated with a respective deployment job according to a specification file that specifies configuration parameters of the deployment;

executing the job-specific scripts stored at the script location in a plurality of stages, including;

executing first stage-specific scripts for a first stage for all of the plurality of deployment jobs, the first stage-specific scripts comprising respective pre-backup or pre-restore scripts for each deployment job of the plurality of different deployment jobs,

after all first stage-specific scripts for the first stage have completed for all of the plurality of different deployment jobs, executing second stage-specific scripts for a second stage for all of the plurality of different deployment jobs, the second stage-specific scripts comprising respective backup or restore scripts for each deployment job of the plurality of different deployment jobs,

after all second stage-specific scripts for the second stage have completed for all of the plurality of different deployment jobs, executing third stage-specific scripts for a third stage for all of the plurality of different deployment jobs, the third stage-specific scripts comprising respective post-backup or post-restore scripts for each deployment job of the plurality of different deployment jobs; and

providing, by the backup orchestrator, a notification to the client device as a response to the request, the notification indicating a state of the backup or restore process.

2. The method of claim 1, wherein:

the deployment is implemented on a collection of virtual machines and a collection of persistent disks,

each deployment job executes in a respective virtual machine, and

each deployment job is defined in the specification file.

3. The method of claim 1, wherein determining the script location comprises identifying the script location as specified in the specification file.

4. The method of claim 1, wherein the specification file defines, for each job, one or more of:

a respective pre-backup script;

a respective backup script;

a respective post-backup script;

a respective pre-restore script;

a respective restore script;

or

a respective post-restore script.

5. The method of claim 4, wherein the specification file defines the respective scripts by specifying respective locations of the respective scripts.

6. The method of claim 1, wherein:

the pre-backup or pre-restore scripts includes scripts for locking one or more jobs, and

the post-backup or post-restore scripts includes scripts for unlocking one or more jobs.

7. The method of claim 1, wherein for each script type, the job-specific scripts having that script type execute serially for each deployment job.

8. The method of claim 1, wherein executing stage-specific scripts for a particular stage for all of the plurality of deployment jobs comprises executing the stage-specific scripts in serial across the plurality of deployment jobs.

9. A system comprising:

a backup orchestrator comprising one or more computers; and

one or more storage devices on which are stored instructions that are operable, when executed by the one or more computers, to cause the one or more computers to perform operations comprising;

receiving, from a client device, a request to perform a backup or restore process for a deployment including a plurality of different deployment jobs, the request being associated with a deployment identifier identifying the deployment;

determining, based on the deployment identifier, a script location storing job-specific scripts, each job-specific script being associated with a respective deployment job according to a specification file that specifies configuration parameters of the deployment;

executing the job-specific scripts stored at the script location in a plurality of stages, including;

executing first stage-specific scripts for a first stage for all of the plurality of deployment jobs, the first stage-specific scripts comprising respective pre-backup or pre-restore scripts for each deployment job of the plurality of different deployment jobs,

after all first stage-specific scripts for the first stage have completed for all of the plurality of different deployment jobs, executing second stage-specific scripts for a second stage for all of the plurality of different deployment jobs, the second stage-specific scripts comprising respective backup or restore scripts for each deployment job of the plurality of different deployment jobs,

after all second stage-specific scripts for the second stage have completed for all of the plurality of different deployment jobs, executing third stage-specific scripts for a third stage for all of the plurality of different deployment jobs, the third stage-specific scripts comprising respective post-backup or post-restore scripts for each deployment job of the plurality of different deployment jobs; and

providing a notification to the client device as a response to the request, the notification indicating a state of the backup or restore process.

10. The system of claim 9, wherein:

the deployment is implemented on a collection of virtual machines and a collection of persistent disks,

each deployment job executes in a respective virtual machine, and

each deployment job is defined in the specification file.

11. The method of claim 9, wherein determining the script location comprises identifying the script location as specified in the specification file.

12. The system of claim 9, wherein the specification file defines, for each job, one or more of:

a respective pre-backup script;

a respective backup script;

a respective post-backup script;

a respective pre-restore script;

a respective restore script;

or

a respective post-restore script.

13. The system of claim 12, wherein the specification file defines the respective scripts by specifying respective locations of the respective scripts.

14. The system of claim 9, wherein:

the pre-backup or pre-restore scripts includes scripts for locking one or more jobs, and

the post-backup or post-restore scripts includes scripts for unlocking one or more jobs.

15. The system of claim 9, wherein for each script type, the job-specific scripts having that script type execute serially for each deployment job.

16. One or more non-transitory storage devices storing instructions that are operable, when executed by one or more computers, to cause the one or more computers to perform operations comprising:

receiving, from a client device by a backup orchestrator comprising one or more computer processors, a request to perform a backup or restore process for a deployment including a plurality of different deployment jobs, the request being associated with a deployment identifier identifying the deployment;

determining, by the backup orchestrator and based on the deployment identifier, a script location storing job-specific scripts, each job-specific script being associated with a respective deployment job according to a specification file that specifies configuration parameters of the deployment;

executing the job-specific scripts stored at the script location in a plurality of stages, including;

executing first stage-specific scripts for a first stage for all of the plurality of deployment jobs, the first stage-specific scripts comprising respective pre-backup or pre-restore scripts for each deployment job of the plurality of different deployment jobs,

after all first stage-specific scripts for the first stage have completed for all of the plurality of different deployment jobs, executing second stage-specific scripts for a second stage for all of the plurality of different deployment jobs, the second stage-specific scripts comprising respective backup or restore scripts for each deployment job of the plurality of different deployment jobs,

after all second stage-specific scripts for the second stage have completed for all of the plurality of different deployment jobs, executing third stage-specific scripts for a third stage for all of the plurality of different deployment jobs, the third stage-specific scripts comprising respective post-backup or post-restore scripts for each deployment job of the plurality of different deployment jobs; and

providing, by the backup orchestrator, a notification to the client device as a response to the request, the notification indicating a state of the backup or restore process.

17. The one or more non-transitory storage devices of claim 16, wherein:

the deployment is implemented on a collection of virtual machines and a collection of persistent disks,

each deployment job executes in a respective virtual machine, and

each deployment job is defined in the specification file.

18. The one or more non-transitory storage devices of claim 16, wherein determining the script location comprises identifying the script location as specified in the specification file.

19. The one or more non-transitory storage devices of claim 16, wherein the specification file defines, for each job, one or more of:

a respective pre-backup script;

a respective backup script;

a respective post-backup script;

a respective pre-restore script;

a respective restore script;

or

a respective post-restore script.