![]() |
![]() |
Attention: A transparent recall process waits for a tape drive to become available. If you migrate and back up your data to tape, use separate tape drives for both migrated data and backed up data. Otherwise, you cannot back up migrated files. To improve performance, migrate your data to disk storage instead of to tape. Performance requirements for migrated data might be more strict than for backed up data.
Transparent recall automatically returns a migrated file to its originating local file system when you access it. When you recall a file, the HSM client leaves a copy of your recalled file in storage. The file becomes premigrated because an identical copy exists both on your local file system and in storage. If you do not modify the file, it remains premigrated until it once again becomes eligible for migration.
If you modify a recalled file, it becomes a resident file. The next time your file system is reconciled, the space monitor daemon marks the stored copy for expiration.