Manual reconciliation of file systems

Edit online

If you recall a migrated file, modify it, and selectively migrate it to IBM Storage Protect server storage, two copies of that file reside in storage. The unmodified copy of the file now is obsolete. Manual reconciliation synchronizes your file system and saves space by removing obsolete copies from IBM Storage Protect server storage.

If you set the migfileexpiration option to 0 in your dsm.sys options file, you can run reconciliation immediately to delete the obsolete copies from IBM Storage Protect server storage and create available space for your migrated files.

Important: A value of 0 indicates that an obsolete copy of a migrated or premigrated file is directly deleted from the server during the next reconciliation run. If you delete the file from the local file system and the reconciliation process runs with the migfileexpiration option set to 0, the file cannot be re-created by the dsmmigundelete command.

The migfileexpiration option is also used by the automatic reconciliation process.

You can also use the dsmreconcile command to search for orphan stub files and complete metadata updates on the server. The following example for the /home file system shows how to search for orphan stub files:

  dsmreconcile -o /home

Note:

Reconciliation requires that the scout daemon is running.
If you reconcile several file systems, increase the value on the reconcileinterval option in the dsm.sys file to reduce the impact that the dsmreconcile command might have on system performance.

After you run reconciliation, check the orphan.stubs file in the .SpaceMan directory for each file system that you reconciled. The file lists orphaned stub files.