![]() |
![]() |
[ | | | ]
You can archive your files at any time and retrieve them to your local file systems when you need them. Use the Tivoli Storage Manager backup-archive client to archive and retrieve copies of your migrated or premigrated files in the same manner as you would archive and retrieve copies of files that reside on your local file systems. See IBM Tivoli Storage Manager for UNIX: Backup-Archive Clients Installation and User's Guide for more information about archiving and retrieving files.
If you archive a copy of a migrated file to the same server to which it was migrated, the file is copied from the migration destination to the archive destination. It does not recall the file to your local file system.
If you archive a copy of a premigrated file to the same server to which it was migrated or to a different server, a copy of the file is sent from your local file system to storage.
If you erase a file from your local file system after you archive a copy of the file, the stub file is deleted from your local file system. However, the migrated copy of the file remains in storage until it expires. The number of days that you specify on the migfileexpiration option in your dsm.sys file determines file expiration.
If you do not erase the file from your local file system after you archive a copy, the file remains migrated.
For AIX JFS file systems only: You can archive a copy of a migrated file to a server other than the one to which it migrated. If you do, and you set the recall mode for a file to normal or migrate-on-close, the backup-archive client accesses the file using the migrate-on-close recall mode. The file resides on your local file system until a copy of the file reaches the archive destination.
If you set the recall mode for a file to read-without-recall, the backup-archive client uses that mode during an archive process.
|For Solaris VxFS, HP-UX VxFS, AIX GPFS, and Linux86 GPFS file |systems only: If you archive a copy of a migrated file to a server |other than the one to which it migrated, the backup-archive client accesses |and recalls the file. It resides on your local file system in a |premigrated state until it is migrated again, or until it receives resident |status.
To retrieve an archived copy of a migrated or premigrated file to your local file system, set the restoremigstate option to no in your dsm.opt file. The file is restored to your local file system as a resident file. The migrated copy of your file is removed from storage when it expires.
To retrieve a file to your local file system and maintain a copy of the migrated file in storage, set the restoremigstate option to yes in your dsm.opt file.
For AIX GPFS, Linux86 GPFS, Solaris VxFS, and HP-UX VxFS file systems only: Files with ACLs are restored to a resident state, even when you specify yes on the restoremigstate option in your dsm.opt file.