Checkpoint Restart Support

• Multiple Copies: Checkpoint Restart is supported for policies configured to create multiple backup copies. If a copy is configured to allow other copies to continue the job if the copy fails and a subsequent checkpoint occurs, and if Checkpoint Restart is selected for this policy, only the last failed copy that contains a checkpoint can be resumed.
• VERITAS Volume Snapshot Provider (VSP): Checkpoint Restart is supported for use with VSP. See VSP (Volume Snapshot Provider) Properties.
• Advanced Client: Checkpoint Restart is supported for use with local or alternate client backups. However, other types of Advanced Backup Methods (ABM) are not supported: Block Level Incremental Backups, Media Server Copy, Third-Party Copy Device, and Instant Recovery backups.)
• Disk staging storage units: Checkpoint Restart is supported for use in Stage I of disk staging, during which data is backed up to disk. See Disk Staging: Stage I. Checkpoint Restart is unavailable in the Stage II storage unit policy, during which data is relocated to another storage unit.
• On Windows clients:
• System State backups: No checkpoints are taken during the backup of a System State.
• Windows Disk-Image (raw) backups: No checkpoints are taken during a Windows disk-image backup.
• Single-instance Store (SIS): No checkpoints are taken for the remainder of the backup after NetBackup encounters a Single-instance Store.
• When an incremental backup is resumed and then completes successfully, the archive bits are cleared for the files backed up since the resume, but not for the files backed up prior to the resume. This means the files backed up prior to the resume will be backed up again on the next incremental backup.
• Synthetic backups: Checkpoint Restart is not supported for use with synthetic backups in the current NetBackup release.
• Checkpoints are not taken for a user archive schedule. If resumed, the user archive restarts from the beginning.
• The scheduler decides when a new job should be started instead of resuming an incomplete job. The scheduler will start a new job in the following situations:
• If a new job is due to run.
• If the time since the last incomplete backup has been longer than the shortest frequency in any schedule for the policy.
• If the time indicated by the Global parameter, Move Backup Job from Incomplete to Done State, has passed.
• For calendar scheduling, if another run day has arrived.