9.2 Common Backup and Restore Issues

Backup does not include the modifications

Possible Cause: Differential and incremental backups were combined.
Action: Use one or the other of these types in conjunction with full backups.
Possible Cause: The modified date filter for backup was set incorrectly.
Action: Set the modified date filter to the last full or differential backup based on the backup type.
Possible Cause: The modify bit was cleared after the last customized backup, so changed files are not recognized.
Action: Modification are backed up based on the modify bit or modified date filter. Check for applications on the server that could be clearing the bit.

Backup is slow

Possible Cause: Compressed files are being backed up in a decompressed format.
Possible Cause: Migrated files are being backed up by demigrating the data.
Possible Cause: Background file compression and backup are running at the same time.
Action: Schedule background file compression before or after backup is scheduled. Based on how compressed files are backed up (see Backing Up Compressed files) the order of scheduling can be decided.

Files were restored but the error file contains a message specifying the name space formats not restored

Possible Cause: The file attributes and name space formats are not configured on the volume you restored to.
Action: Check to make sure the name space is configured on the required volume.

Restore is slow

Possible Cause: File compression and restore are running at the same time.
Action: Schedule restore and background compression of files at different times.
Possible Cause: Compressed files are being overwritten with decompressed files.
Action: Back up compressed files as compressed in the future, if the restore is going to be to a compressed file system. See Backing Up Compressed files.

Unable to backup open files in NSS Volumes

Possible Cause: TSAFS supports backup of open files on Novell Storage Services (NSS) volumes if the CopyOnWrite feature is enabled. The Supervisor right is required to back up open files
Action: To enable CopyOnWrite on a single NSS volume, see the Backing Up Open Files.

Unable to restore compressed files

Possible Cause: Compression is not supported in some environments such as Novell Storage Services or ReiserFS on OES.
Action: Restore the file to a volume that supports compression.
Possible Cause: The file system that the data is restored to does not have the compression feature enabled.
Action: Enable the compression feature on the file system that data is being restored to.

Unable to set the data set name

Possible Cause: This happens when the TSA is unable to restore a particular name in a name space. The data set is restored, but while restoring names in all name spaces there were name conflicts on the non-primary name spaces. This causes a failure, with an error message similar to the following:
Unable to set the data set name in MACnamespace for sys:/abc/def.txt. Restore will continue processing the data set name 
in other name spaces. 
Action: This is a warning and does not impact the restore process.

Out of disk space

Possible Cause: There is not enough disk space on the volume to which the data is restored.
Action: Increase the volume size and restart the restore.
Possible Cause: A user space restriction is set for certain users and the application is attempting to restore data that exceeds this space restriction.
Action: Increase the user space restriction on the restored volume for users who are affected.
Possible Cause: There are directory quotas set on specific directories that are being restored, and the application is trying to restore data that exceeds the quotas.
Action: Increase the directory quota on the affected directories then restart the restore.
Possible Cause: You might run out of disk space if you restore decompressed files to a volume, because the compression does not begin immediately.
Action: Compress the files before the restore.

DOS namespace based restores fail for certain files

Possible Cause: DOS names are usually name mangled forms of their LONG or other namespace formats. These names are often auto-generated by the file system. There could be a name clash because of existing files or directories on the system having similar mangled DOS names as that of the data sets being restored.
Action: Restore using non-DOS name spaces.

Backed up filenames display characters of the form [xxxx]

Possible Cause: When converting characters from Unicode to MBCS for display or to return to the backup application it is possible to have characters that do not map to any valid MBCS character on the server locale. Such unmappable characters are displayed in the square bracket notation.
Action: This does not impact the backup process. File names are stored in Unicode* and MBCS formats during backup and hence on restoring such files the restored files will have the correct name convention.