# US 2018/0322019 A1 · Backup and restore framework for distributed computing systems

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2018/0322019 A1
- Document ID: US20180322019A1
- Status: Published application
- Kind: A1
- Application number: 15/588,529
- Filed: 2017-05-05
- Published: 2018-11-08
- Earliest claimed: 2017-05-05
- Assignees: Pivotal Software, Inc.
- Applicants: Pivotal Software, Inc.
- Inventors: Therese Louise Stowell; Kalyan Chakravarthy Dudala; Colin Michael Humphreys; Simon James Jones; Jatin Naik; Alvaro Perez-Shirley; Henry Arthur James Stanley
- Web page: https://patentgrep.com/patent/US20180322019A1

## CPC

- G06F 11/1469: {Backup restoration techniques}
- G06F 9/4843: {by program, e.g. task dispatcher, supervisor, operating system}
- G06F 11/1451: {by selection of backup contents}
- G06F 11/1458: {Management of the backup or restore process}
- G06F 2201/805: Real-time
- G06F 2201/815: Virtual
- G06F 2201/82: Solving problems relating to consistency
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## 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

### Claim 1

A method, comprising:
receiving, from a client device by a backup orchestrator comprising one or more computer processors, a request to backup or restore a deployment including one or more 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 predetermined order, including executing pre-backup or pre-restore scripts for each deployment job, then executing backup or restore scripts for each deployment jobs, then executing post-backup or post-restore scripts for each deployment job, wherein the job-specific scripts back up the one or more deployment jobs or restore the one or more deployment jobs; and
providing, by the backup orchestrator, a status report to the client device as a response to the request, the status report indicating a state of the backup or restore.

### Claim 2 (depends on 1)

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.

### Claim 3 (depends on 1)

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

### Claim 4 (depends on 1)

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.

### Claim 5 (depends on 4)

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

### Claim 6 (depends on 1)

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.

### Claim 7 (depends on 1)

The method of claim 1, wherein executing the job-specific scripts stored at the script location in the predetermined order comprises executing the job-specific scripts serially by script type, wherein second type scripts execute after first type scripts are completed for all deployment jobs.

### Claim 8 (depends on 7)

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

### Claim 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 backup or restore a deployment including one or more 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 predetermined order, including executing pre-backup or pre-restore scripts for each deployment job, then executing backup or restore scripts for each deployment jobs, then executing post-backup or post-restore scripts for each deployment job, wherein the job-specific scripts back up the one or more deployment jobs or restore the one or more deployment jobs; and
providing a status report to the client device as a response to the request, the status report indicating a state of the backup or restore.

### Claim 10 (depends on 9)

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.

### Claim 11 (depends on 9)

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

### Claim 12 (depends on 9)

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.

### Claim 13 (depends on 12)

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

### Claim 14 (depends on 9)

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.

### Claim 15 (depends on 9)

The system of claim 9, wherein executing the job-specific scripts stored at the script location in the predetermined order comprises executing the job-specific scripts serially by script type, wherein second type scripts execute after first type scripts are completed for all deployment jobs.

### Claim 16 (depends on 15)

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

### Claim 17

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, a request to backup or restore a deployment including one or more 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 predetermined order, including executing pre-backup or pre-restore scripts for each deployment job, then executing backup or restore scripts for each deployment jobs, then executing post-backup or post-restore scripts for each deployment job, wherein the job-specific scripts back up the one or more deployment jobs or restore the one or more deployment jobs; and
providing, by the backup orchestrator, a status report to the client device as a response to the request, the status report indicating a state of the backup or restore.

### Claim 18 (depends on 17)

The one or more non-transitory storage devices of claim 17, 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.

### Claim 19 (depends on 17)

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

### Claim 20 (depends on 17)

The one or more non-transitory storage devices of claim 17, 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.
