![]() |
![]() |
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 and AIX 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.