Configuring checkpoint restart
Checkpoint restart is a backup job setting that enables Backup Exec to automatically restart a job that is interrupted. The job restarts from the point where it was interrupted instead of starting over at the beginning. Backup Exec waits two minutes after the job stops and then attempts to restart the interrupted job. If the job cannot be restarted automatically or if checkpoint restart is disabled, you must restart it manually. A manual restart starts the job at the beginning instead of at the point where the job was interrupted.
Note: Checkpoint restart cannot restart a backup job until it has backed up at least 32 MB of data. If a backup job fails before it has backed up at least that much data, you must run it again manually.
You can enable checkpoint restart for any jobs that are configured with the storage option Overwrite media. However, if there is no available media to overwrite and the job is interrupted, it may be placed on hold until overwritable media is available. When the media is available, the job restarts from where it was interrupted.
Backup Exec automatically cancels any jobs that run for too long according to the schedule settings that you selected when you created the job. If Backup Exec automatically cancels a job, it is not eligible to be restarted. If you manually cancel a job, Backup Exec does not automatically try to restart it.
Note: If you use the Central Admin Server feature (CAS), any jobs that are restarted run on the same managed Backup Exec server on which the job failed. If the original Backup Exec server is not available, Backup Exec selects a different Backup Exec server on which to run the restarted job.
You can enable or disable checkpoint restart in the Advanced Open File options when you create backup jobs or in the backup job defaults.
This topic includes the following information:
Technologies supported for checkpoint restart
Checkpoint restart is only supported for NTFS volumes. The only type of snapshot technology that is supported for checkpoint restart is VSS.
Checkpoint restart is not supported for the following:
-
FAT volumes
-
FAT32 volumes
-
UNIX computers
-
Cluster Shared Volumes (CSV)
-
Application agents
-
Incremental or differential backups
-
Jobs that use catalogs to determine if a file has been backed up
Things to consider before you use checkpoint restart
You should consider the following things before you use checkpoint restart:
-
If the failure occurs in the middle of an append job, the media is no longer appendable. The media is not appendable until it is erased or overwritten, or the retention period expires. When the restart occurs, Backup Exec uses new media. You should select an appropriate media overwrite protection level to ensure that the restart does not overwrite the media that was used before the job failure.
-
If the failure occurs during a verify job or a database consistency check job, the job restarts at the beginning.
-
Full backups that were interrupted and resumed from the point of failure do not display in the Simplified Disaster Recovery Recover This Computer Wizard. However, you can restore these backup sets manually after you make the initial recovery by using the Recover This Computer Wizard.
-
You can enable the checkpoint restart option for a full backup job that uses the Delete selected files and folders after successful backup option. If the job fails and is resumed, the files are not deleted from the source volume after the backup completes.
Changing the default checkpoint restart settings
You can change the default checkpoint restart settings in the error-handling rules settings. You can specify the number of times that you want checkpoint restart to retry a failed job, the interval between restart attempts, and the final job disposition for any jobs that cannot be successfully restarted.
To change default checkpoint restart settings
-
Click the Backup Exec button, select Configuration and Settings, and then selectError-Handling Rules.
-
Select Checkpoint Restart, and then clickEdit.
-
Select Enable error-handling rule.
-
Select Retry job.
-
Complete the following fields:
Maximum retries Enter the maximum number of times that you want Backup Exec to retry a job that fails. Retry interval Enter the interval of time in minutes that you want Backup Exec to wait before it attempts to restart a job. -
In the Final job disposition group box, select one of the following options:
Place job on hold until error condition has been manually cleared Select this option to have Backup Exec place the job on hold if the job cannot be completed successfully after the maximum number of retries. The job remains on hold until the error condition has been manually cleared. Reschedule job for its next scheduled service Select this option to have Backup Exec reschedule the job for its next scheduled occurrence if the job cannot be completed successfully after the maximum number of retries. -
(Optional) In the Notes field, type any additional notes about the error-handling rule.
-
Click OK.
Related information