Backing up migrated files

Use the Tivoli® Storage Manager backup-archive client to back up or archive migrated files. The skipmigrated option must not be set to yes.

Before you begin

The skipmigrated option controls whether migrated files are included in a backup or archive operation. If skipmigrated=yes, migrated files are excluded from the backup or archive operation. If skipmigrated=no (the default), the backup-archive client can process stub files during some operations.

Set the skipmigrated option in the backup-archive client options file dsm.opt. Use the preferences editor or directly edit the backup-archive dsm.opt options file. You can also specify the skipmigrated option when you start a command on the command line.

About this task

  • If skipmigrated=no (the default), the type of backup or archive operation determines whether migrated files are backed up.
    Incremental backup or image backup
    Only an incremental backup or image backup can back up a stub. The object that is backed up depends on whether the Tivoli Storage Manager server contains a current backup copy of the complete file.
    If the Tivoli Storage Manager server contains a current backup copy of the complete file:
    An incremental or image backup backs up the stub.
    If the Tivoli Storage Manager server does not contain a current backup copy of the complete file:
    An incremental or image backup backs up the complete file.
    Incremental-by-date backup
    An incremental-by-date backup does not back up the stub or the complete file.
    Selective backup or archive
    Selective backup or archive does not back up a stub. The complete file is backed up regardless of whether a current backup copy exists on the Tivoli Storage Manager server.

The backup-archive client ensures that whenever a stub is backed up, there is a copy of the migrated file in the backup pool. If a migrated file was not backed up before migration, the migrated file is temporarily retrieved and is backed up. After the backup, the temporary file is removed by the backup-archive client. You can control the location to which the backup-archive client retrieves the temporary file by using the stagingdirectory option of the backup-archive client.

Tip: If you have many files that have not been backed up before migration, and the skipmigrated option has the default value no, all of those files are retrieved when they are backed up. The number of files that are retrieved during a backup can be great in these situations:
  • You have many stubs that were backed up with backup-archive client version 5.4 and earlier versions. These files are temporarily retrieved during backups with later versions of the backup-archive client.
  • You renamed or changed the security settings of stubs or directories containing stubs.
  • You changed the backup policies for a volume by including for backup many files that were not previously included.

If the backup-archive client cannot create a backup copy the migrated file, the backup-archive client does not back up the stub file. (The backup of the migrated file can be unsuccessful if the stub is an orphan.)

Restriction: You must not use adaptive subfile backup and HSM. You must back up only the entire migrated file. If you use adaptive subfile backup on migrated files, you might not be able to restore migrated files correctly. The backup-archive client does not report any errors or warnings when you do a subfile backup of a migrated file.

Procedure

Use the backup-archive client archive, backup image, incremental, or selective command.
For more information about these commands, see the Tivoli Storage Manager backup-archive client documentation:
Related reference:
skipmigrated