Automatic backup before migration
To protect your data completely, you must back up your data. The backup-before-migrate feature ensures that there exists a backup copy for every file that you migrate.
You can select whether the backup-before-migrate feature is used as the default option for all new migration jobs and threshold migrations. Use the Backup before migration window in the HSM for Windows client configuration wizard. In each job or threshold migration, you can accept that default or you can specify another option. For every job and threshold migration, you can choose whether to back up files before migration, and which options file to use for the backup. The backup-archive client automatically backs up the necessary files before migration. If the backup is successful, the file is migrated.
By default, the backup-archive client changes the access time stamp of a file when the backup-archive client backs up a file. If a migration job or threshold migration is configured to check a file's access time (-minagetype access), the file might not be migrated after a recent backup operation. Use the preservelastaccessdate option of the backup-archive client to specify whether a backup operation changes the access time stamp.
Even if you schedule regular backups, a file can change and be migrated before a backup operation runs. At the next backup operation, the backup-archive client gets a copy of the migrated file. The migrated file is copied to the staging directory and is backed up. To avoid the file copies during a backup operation, use the backup-before-migrate feature and use the same backup options that are used for the scheduled backup.
- The HSM for Windows client does not back up stub files.
- The HSM for Windows client does not back up files that do not meet the migration criteria.
- The HSM for Windows client does not back up a file if there exists a current backup copy of the file.