Forum Discussion

Aaron_L_'s avatar
Aaron_L_
15 years ago

Checkpoint restart for windows backup jobs

Question: Does the checkpoint restart work with windows(system state) backup jobs? I'm having an issue with a weekly full backup of a windows 2003 client failing and I want to use this feature to save some time while I investigate the issue since it fails near the end of the backup and it takes 10 hours to start the backup over.

Also, how much does this affect performance/speed? FYI I'm running 6.5.5.

Thanks!


7.1.x and Earlier
Backing Up
Backup and Recovery
NetBackup
  • Marianne's avatar
    Marianne
    15 years ago

    Checkpoint restart is supported for filesystem backups, but does not apply to System State backups.

    Extract from Admin Guide I under the topic Checkpoint restart support:
    p. 102

    ■ On Windows clients:
         ■ System State backups: No checkpoints are taken during the backup of a System State.
  • Marianne's avatar
    Marianne
    Level 6
    15 years ago

    Checkpoint restart is supported for filesystem backups, but does not apply to System State backups.

    Extract from Admin Guide I under the topic Checkpoint restart support:
    p. 102

    ■ On Windows clients:
         ■ System State backups: No checkpoints are taken during the backup of a System State.
  • varunprakash's avatar
    varunprakash
    Level 5
    15 years ago

     File system local and alternate client snapshot backups are supported. However, other off-host backup methods (e.g. Media Server Copy or Third Party Copy) are not supported.

    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 job was resumed, 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.

  • Karthikeyan_Sun's avatar
    Karthikeyan_Sun
    Level 6
    15 years ago

    Checkpoints during a backup are beneficial if a backup fails. Without Take checkpoints every enabled, a failed backup restarts from the beginning of the job. By taking checkpoints periodically during the backup, NetBackup can retry a failed backup from the beginning of the last checkpoint rather than restart the entire job. Note that checkpoints cannot occur while a file is backed up. Checkpoints are saved at file boundaries, and point to the next file in the list.

    Policy types MS-Windows-NT (for Windows clients) and Standard (for UNIX clients) support this policy attribute. To see if this feature is supported for a specific agent or option, refer to the manual for that agent or option

    The checkpoint frequency indicates how often NetBackup takes a checkpoint during a backup. (Default: 15 minutes.) The administrator determines checkpoint frequency on a policy-by-policy basis. Balance more frequent checkpoints with the likelihood of time that is lost when a backup is resumed. If the frequency of checkpoints impacts performance, increase the time between checkpoints.

    Multiple Copies: Checkpoint restart is supported for the policies that are configured to create multiple backup copies.

    Veritas Volume Snapshot Provider (VSP): Checkpoint restart is supported for use with VSP.

    and some more details in this admin guide link.

    http://seer.entsupport.symantec.com/docs/290203.htm - Page no 101