|
Windows clients
|
The following items pertain to the use of
checkpoint restart with Windows clients:
-
Checkpoint restart is not supported for backup
selections indicated by a UNC path.
-
No checkpoints are taken during a System State
backup.
-
No checkpoints are taken during a Windows Disk
Image (raw) backup.
-
No checkpoints are taken for the remainder of the
backup after NetBackup encounters Single-instance Store
(SIS).
-
When an incremental backup resumes and completes
successfully, the archive bits are cleared for the files that were
backed up after the job resumed. However, the archive bits are not
cleared for the files that were backed up before the resume. Since
the archive bits remain, the files that were backed up before the
resume are backed up again during the next incremental backup.
|
|
Multiple copies
|
Checkpoint
restart is supported for the policies that are configured to create
multiple backup copies.
See Multiple copies schedule
attribute.
The last failed copy that contains a checkpoint
can be resumed if all of the following items are true:
|
|
Synthetic backups
|
Checkpoint restart is not supported for use with
synthetic backups in the current NetBackup release.
|
|
Snapshot Client
|
Checkpoint restart is
supported for use with local or alternate client backups. However,
the following methods are not supported: Block Level Incremental
Backups, Media Server Copy, Third-Party Copy Device, and Instant
Recovery backups.
|
|
Basic disk staging
|
Checkpoint
restart is supported for use in Stage I of basic disk staging,
during which data is backed up to disk.
Checkpoint restart is
unavailable in the Stage II storage unit policy of basic disk
staging, during which data is relocated to another storage
unit.
|
|
NearStore storage units
|
NearStore storage units
do not support checkpoint restart.
|
|
NetWare clients
|
Although NetWare clients
can use the Standard policy type, checkpoint restart for backups is
not supported on NetWare clients.
|
