Method and system for a data protection policy generator

Patent metadata

Field	Value
Publication number	US-9805075-B1
Application number	US-201213729249-A
Country	US
Kind code	B1
Filing date	Dec 28, 2012
Priority date	Dec 28, 2012
Publication date	Oct 31, 2017
Grant date	Oct 31, 2017

Abstract

A data protection policy generator is described. A first set of selections is received to generate a first task. The first set of selections includes selections of a first source, a first data set, a first destination, and a first execution schedule. A second set of selections is received to generate a second task. The tasks may be any of a backup copy task, a clone task, a backup verification task, a snapshot creation task, a snapshot backup task, a snapshot clone task, a backup delete task, a backup query task, or a restore task. The second set of selections includes selections of a second source, a second data set, a second destination, and a second execution schedule. The first data destination includes the second data source. Execution of the first task and the second task is enabled based on at least the first execution schedule and the second execution schedule.

First claim

What is claimed is:

1. A system for a data protection policy generator, the system comprising:
a processor-based application, which when executed on a computer, will cause the computer to:
generate, by a first client computer, a first task to be executed according to a first execution schedule, the first task causing a first data set residing on a second client computer to be stored as a second data set on a first destination server different from the the second client computer, the second data set being a backup copy of the first data set;
generate, by the first client computer, a second task to be executed according to a second execution schedule, the second task causing the second data set stored on the first destination server to be stored as a third data set on a second destination server different from the second client computer and the first destination server, the third data set being a clone copy of the second data set;
cause, by the first client computer, a communication between the first task and the second task, the communication indicating a dependency of the clone copy on the backup copy; and
enable, by the first client computer, execution of the first task and the second task based on the first execution schedule and the second execution schedule such that the first task is executed according to the first execution schedule before execution of the second task according to the second execution schedule in response to the communication indicating the dependency of the clone copy on the backup copy.

2. The system of claim 1 , wherein the first task comprises a task selected from a group comprising a first backup copy task, a first clone task, a first backup verification task, a first snapshot creation task, a first snapshot backup task, a first snapshot clone task, a first backup delete task, a first backup query task, and a first restore task.

3. The system of claim 2 , wherein the second task comprises a task selected from a group comprising a second backup copy task, a second clone task, a second backup verification task, a second snapshot creation task, a second snapshot backup task, a second snapshot clone task, a second backup delete task, a second backup query task, and a second restore task.

4. The system of claim 1 , wherein the first and second tasks are generated to execute concurrently in response to the inter-task pipe communicating the clone copy not being dependent on the backup copy, and wherein a maximum number of concurrent tasks to be executed concurrently is designated by the first client computer.

5. The system of claim 1 , wherein at least one of a retention policy that specifies a duration for data retention, a browse policy that specifies a duration for browsing specified data, a number of copies to be created, and a number of retries to attempt before halting further attempts following a failed task is designated by the first client computer.

6. The system of claim 1 , wherein the second client comprises multiple source nodes, wherein the multiple source nodes comprise at least one of a disk source node, a tape source node, and a source node comprising a combination of disks and tapes, and wherein the first destination server comprises multiple destination nodes, wherein the multiple destination nodes comprise at least one of a disk destination node, a tape destination node, and a destination node comprising a combination of disks and tapes.

7. The system of claim 1 , wherein the first destination server comprises multiple source nodes, wherein the multiple source nodes comprise at least one of a disk source node, a tape source node, and a source node comprising a combination of disks and tapes, and wherein the second destination comprises server multiple destination nodes, wherein the multiple destination nodes comprise at least one of a disk destination node, a tape destination node, and a destination node comprising a combination of disks and tapes.

8. The system of claim 1 , wherein the processor-based application, when executed, will cause the computer to generate, by the first client computer, a third task to be executed according to a third execution schedule, the third task causing the third data set stored on the second destination server to be stored as a fourth data set on a third destination server different from the second client computer, the first destination server, and the second destination server, wherein the third task comprises one of a third backup copy task, a third clone task, a third backup verification task, a third snapshot creation task, a third snapshot backup task, a third snapshot clone task, a third backup delete task, a third backup query task, and a third restore task, and wherein enabling execution of the first task and the second task further comprises enabling execution of the third task further based on the third execution schedule.

9. The system of claim 1 , wherein the processor-based application, when executed, will cause the computer to enable communication of data between tasks, and persist communication of data between tasks beyond at least one of an application crash, a system outage, and a network failure.

10. The system of claim 1 , wherein enabling execution of the first task and the second task comprises a policy engine executing a policy which comprises the first task and the second task, and wherein the policy engine executes remote procedure calls to execute the first task and the second task.

11. The system of claim 10 , wherein the processor-based application, when executed, will cause the computer to execute the policy based on a policy schedule to at least one of monitor task failure, log task output, suspend a task, and resume execution of a suspended task.

12. The system of claim 1 , wherein enabling execution of the first task and the second task comprises executing a copy task for a duration of a copy window and executing the copy task for a duration of a catch up window when executing the copy task for the duration of the copy window is insufficient to complete execution of the copy task.

13. A computer-implemented method for a data protection policy generator, the method comprising:
generating a first task to be executed according to a first execution schedule, the first task causing a first data set residing on a second client computer to be stored as a second data set on a first destination server different from the second client computer, the second data set being a backup copy of the first data set;
generating a second task to be executed according to a second execution schedule, the second task causing the second data set stored on the first destination server to be stored as a third data set on a second destination server different from the second client computer and the first destination server, the third data set being a clone copy of the second data set;
causing a communication between the first task and the second task, the communication indicating a dependency of the clone copy on the backup copy; and
enabling execution of the first task and the second task based on the first execution schedule and the second execution schedule such that the first task is executed according to the first execution schedule before execution of the second task according to the second execution schedule in response to the communication indicating the dependency of the clone copy on the backup copy.

14. The method of claim 13 , wherein the first task comprises a task selected from a group comprising a first backup copy task, a first clone task, a first backup verification task, a first snapshot creation task, a first snapshot backup task, a first snapshot clone

Assignees

• Emc Corp
• Emc Ip Holding Co Llc

Inventors

• Bachu Kiran K
• Mandic Vladimir
• Popelka Paul

Classifications

• G06F11/1461

  Backup scheduling policy · CPC title

• G06F11/1451

  by selection of backup contents · CPC title

• G06F9/4843 Primary

  by program, e.g. task dispatcher, supervisor, operating system · CPC title

• G06F2201/84

  Using snapshots, i.e. a logical point-in-time copy of the data · CPC title

• G06F17/30312 Primary

  Physics · mapped topic