Managing backup performance when stub file encryption changes

You can limit the impact to backup performance that is caused by changing the encryption of stub files. Stage the encryption changes and backup operations.

About this task

If you change the encryption of a stub file, the Tivoli® Storage Manager backup-archive client copies the migrated file to a staging directory during the next incremental backup operation. If you change the encryption of many files, the backup operation can take a long time for the many temporary file copies.

To avoid temporarily copying many files, set the encryption status of files before you back up the resident files.

If you must change the encryption of an HSM-managed volume, you can stage the encryption change and the backup operation.

Tip: Another option is to first change the encryption of all the files. Then, back up migrated files separately from resident files.

Procedure

  1. Change the encryption of the files in one directory of a volume.
  2. Run an incremental backup of the changed files in the directory. Stub files with a modified encryption status are temporarily copied and backed up.
  3. Repeat steps 1 and 2 for each directory in the volume.
Related tasks:
Backing up migrated files separately from resident files