Troubleshooting stages of backup and restore operations
Refer to the following list to determine the source of a backup or restore error:
A backup or restore can be started in either of the following ways:
Manually from the administrator interface on the master server
Automatically by a NetBackup server using a full schedule or incremental schedule
If an error occurs during the start operation, examine the Java reports window for the possible cause of the error.
If the backup or restore starts successfully but eventually fails, one of the following can be the cause:
Server/Client communication problem
Schedule error
Media-related error
VxFS errors
For more information, see the NetBackup Troubleshooting Guide.
There can be insufficient disk space for the VxFS Fulldata Storage Checkpoints to keep track of changed block information. Check the All Log Entries report for errors.
If there is a file system out-of-space condition, increase the size of the file system so it is large enough for Fulldata Storage Checkpoints or use the Nodata Storage Checkpoint Hot backup method. This error does not affect the integrity of the backup images because a full backup of the affected file system occurs after the condition is fixed.
If an incremental backup is intended, but the whole file system is backed up instead, one of the following conditions might be present:
The most common cause of this problem is the file system removed the Storage Checkpoint that keeps track of the block changes. This action might occur if the file system runs out of space, and there are no volumes available to allocate to the file system. The integrity of the backup images is not affected, because a full backup of the file system occurs at the next backup opportunity after NetBackup detects that a Storage Checkpoint is missing.