Orphaned stub files

An orphaned stub file is a stub file for which a corresponding migrated file in IBM Storage® Protect server storage is not located. If orphaned stub files exist in your file systems, the space management client records information about these files in the orphan.stubs file during reconciliation.

If you set the errorprog option in your dsm.sys file, a message is sent to the program that you specified with this option during automatic reconciliation.

To check for orphaned files, specify YES on the checkfororphans option in the dsm.sys file. When orphaned files are located, their names are recorded in the .SpaceMan/orphan.stubs file. If you specify YES, the dsmreconcile process queries the scout daemon for all migrated and premigrated files and checks that corresponding objects exist on the server.

Stub files might become orphaned include the following situations:

• You modified your dsm.sys file so your client node now contacts a different server for space management services other than the one to which files were migrated.
  • To resolve this problem, modify your dsm.sys file so your client node contacts the server to which the files migrated.
• Your IBM Storage Protect administrator uses the delete filespace administrator command to delete any migrated files from a specific file system.
  • To resolve this problem, if files are no longer needed, an administrator can delete some or all of the files from IBM Storage Protect server storage. The stub files are no longer valid and you can erase them.
• A media failure occurs that corrupts or loses your migrated files. Storage pool backup and recovery provides protection against media failures. However, if you cannot restore a migrated file from a migration storage pool, you can restore a backup version of the file if you used the backup-archive client.
  • When you set the restoremigstate option to NO in your dsm.opt file, and you then restore a backup version of a migrated file, the file becomes a normal, resident file.