Checkpoint restart for restore jobs

Checkpoint Restart for restore jobs saves time by providing the mechanism for NetBackup to resume a failed restore job. The job resumes automatically from the start of the file last checkpointed rather than from the beginning of the entire restore job. NetBackup automatically takes checkpoints once every minute during a restore job.

The following two host properties affect Checkpoint Restart for restore jobs:

Limitations to the Checkpoint Restart option for restore jobs include the following:

Suspending and resuming a restore job

A NetBackup administrator can choose to suspend a checkpointed restore job and resume the job at a later time.

For example, while an administrator runs a restore job for several hours, the administrator receives a request for a second restore. The request is of a higher priority and requires the resources in use by the first job. The administrator can suspend the first job, start the second restore job and let it complete. The administrator can then resume the first job from the Activity Monitor and let the job complete.

Note:

If a checkpointed restore that has no end date is suspended, then resumed, and a new backup occurs before the resume is initiated, the files from the new backup are included in the restore. For example, a user makes a restore request of a directory. Then that restore is suspended. The request is resumed the next day after another backup of the directory has been performed. The files that are restored are from the latest backup.

More Information

Suspending and resuming a restore job