restoremigstate

Edit online

The restoremigstate option specifies whether you want to restore or retrieve stub files or backup-archive versions of migrated files during a restore-retrieve operation. Use this option with the backup-archive client restore and retrieve commands.

You can restore or retrieve a stub file for a migrated file only when the following is true:

The file exists in the migration storage pool
The file is backed up or archived and migrated to the same server

When the number of days elapse that you specified with the migfileexpiration option, the migrated file is removed from storage.

If you specify restoremigstate YES, and if the migrated file is not expired, the file is restored or retrieved to a stub file, regardless of whether it is marked for expiration.

On a space-managed file system, you can restore a stub file only during standard-query restore processing. During no-query restore processing to a space-managed file system, you cannot restore stub files.

The restoremigstate option restores a file if it is backed up after migration. If the file is backed up before migration, you cannot restore a stub file because a server stub file copy does not exist.

Files with access control lists (ACLs) are restored in a resident state regardless of the setting for restoremigstate. The restore operation affects files that are restored to a GPFS™ file system with more storage pools than the default system pool.

If you restore a file from the IBM Storage® Protect target server, and the file system is managed by the space management client, you must not restore the file as a stub file. You must restore the complete file. Use the restoremigstate=no option to restore the complete file. If you restore the file as a stub from the target server, the following consequences can occur:

You cannot recall the file from the IBM Storage Protect source server by using the space management client.
A space management client reconciliation process that runs against the IBM Storage Protect source server expires the file. If the file is expired by a reconciliation process, you can restore the complete file with the backup-archive client and the restoremigstate=no option.

Tip: The restoremigstate option does not support hard linked files. If you want to restore or retrieve a stub file for a hard linked file, delete all files from your local file system that are hard linked together. When one file in a set of hard linked files is migrated, all of the hard linked files in the set become stub files. When you enter the restore command with the restoremigstate option to restore a stub file for a hard linked file, the stub file has the same name as the file that was originally migrated. Stub files are not restored for any other files that previously were in the hard linked set of files.

Options File

Place this option in the dsm.opt or dsm.sys file.

Syntax

Parameters

YES: Restores or retrieves migrated files to stub files on your local file system during a restore or retrieve operation. The files remain migrated. This is the default.
Note: A stub file that is created during a restore or retrieve operation contains the information that is necessary to recall the migrated file from storage. It does not contain any leading bytes of data from the file. Any recall mode that was set previously for the migrated file (for example, streaming or partial file recall) is not stored in the stub file. The recall mode is set to normal for all files that are restored or retrieved to stub files.
NO: Restores or retrieves backup-archive versions of migrated files to your local file system during a restore or retrieve operation. The files become resident.

Command line

This option is valid on the command line.