Previously migrated files

After a file is migrated, it can be migrated again. Whether the file is migrated again depends on how the file was last migrated and how the file is changed.

When a file is recalled, modified, and migrated again, that new version of the file is stored in IBM® Storage Protect storage. More than one version of the file exists in IBM Storage Protect™ storage until the file system is reconciled. Any file operation that requires the file to be recalled yields the most recently migrated version.

If a file was migrated and replaced with a stub, the subsequent migration of the file depends on how the file changes and the type of migration. A threshold migration does not migrate a stub. For migration types other than threshold migration, the subsequent migration of the stub file depends on how the file changes.

The file content changes

When you change the content of a file, the HSM for Windows client recalls the file from IBM Storage Protect storage. The next time that the file is the object of a migration job or a threshold migration, the new version of the file is migrated. The IBM Storage Protect server maintains versions of the migrated file until you run reconciliation. The migrated file is bound to the management class that is specified by the last migration job or threshold migration.

Only the file attributes or times (creation time or last modification time) change

When only file attributes or times (creation time or last modification time) change, the file is not migrated again to IBM Storage Protect storage. Instead, the attributes or file times are updated in the IBM Storage Protect metadata database the next time. The updates are made the next time that the file is the object of a migration job. The management class does not change, even if the migration job specifies a different management class.

Only the file security attributes change

The second migration of the file depends on whether you configured migration of file security attributes.

If you configured migration of file security attributes:

If only the ACL changes, the file is migrated the next time that the file is the object of a migration job or list migration. At the next job or list migration, the file is temporarily recalled, then migrated with the updated ACL. The version number of the file that is tracked by IBM Storage Protect does not change. The previous copy of the file in IBM Storage Protect storage is deleted. The migrated file is bound to the management class that is specified by the last migration job or threshold migration. If the file is targeted by a threshold migration, the file is not migrated again.

If you configured no migration of file security attributes:

If only the ACL changes, the file is not migrated the next time that the file is the object of a migration job or list migration.

Only the Windows alternate data stream (ADS) data changes

The second migration of the file depends on whether you configured migration of ADS data.

If you configured migration of ADS data:

If only the ADS data changes, the file is migrated the next time that the file is the object of a migration job or list migration. At the next job or list migration, the file is temporarily recalled, then migrated with the updated ADS data. The version number of the file that is tracked by IBM Storage Protect does not change. The previous copy of the file in IBM Storage Protect storage is deleted. The migrated file is bound to the management class that is specified by the last migration job or threshold migration. If the file is targeted by a threshold migration, the file is not migrated again.

If you configured no migration of ADS data:

If only the ADS data changes, the file is not migrated the next time that the file is the object of a migration job or list migration.

No changes

Even if a migrated file did not change in any way, it can be migrated again. For example, you can migrate a file; recall the file; and not change the file. When you migrate the file again, the HSM for Windows client replaces the existing file with a stub that points to the existing file copy in IBM Storage Protect storage. The management class does not change, even if the migration job specifies a different management class.

You can configure migration with the keep option. The file is migrated to IBM Storage Protect storage, but the file is not replaced by a stub file. When you change the file, the HSM for Windows client does not automatically recall the file or track the changes to the file on the IBM Storage Protect server. The file remains unchanged on IBM Storage Protect storage. If you migrate the file again, the file is bound to the management class that is specified by the last migration job or list migration.