Automatic reconciliation

Edit online

The space management client automatically reconciles each file system for which space management is active. For example, when you modify or delete a migrated or premigrated file from your local file system, an obsolete copy of the file remains in storage. During automatic reconciliation, any obsolete copies of your migrated or premigrated files are marked for expiration.

To specify how often reconciliation runs, modify the setting on the reconcileinterval option in your dsm.sys options file. The default is every 24 hours.

You can specify how many days a migrated or premigrated file remains in IBM Storage® Protect server storage after you recall and modify or erase it from your local file system. Modify the setting on the migfileexpiration option in your dsm.sys options file. The default is 7 days. When the copies expire, they are removed from the server.

Table 1 describes the tasks that automatic reconciliation completes for files and file systems.

Table 1. Automatic reconciliation tasks
File type	Reconciliation Tasks
Migrated files	Verifies that a stub file exists on your local file system for each migrated file in storage Marks a migrated file for expiration in the following cases: You deleted the stub file from your local file system You recalled the file and modified it Removes a migrated file from IBM Storage Protect server storage if it expired Updates the status file
Premigrated files	Verifies that premigrated files are still valid Marks a premigrated file for expiration in the following cases: You deleted the file from your local file system You accessed the file and modified it Removes a copy of a premigrated file from IBM Storage Protect server storage if it expired. Updates the status file
Stub files	Records the name of any file for which a stub file exists on your local file system, but a migrated file does not exist in storage. The names are recorded in the orphan.stubs file.
Status file	Updates the following information in the status file: Number of premigrated files Number of premigrated blocks Number of migrated files Number of migrated blocks Note: Migration and recall processes update status information dynamically. If any other process changes the state of a file, the status file does not reflect the change until reconciliation is run.