Validating the Catalog

Over time, inconsistencies can develop in the catalog as links are broken, users are deleted, or NFS file system issues are encountered. These inconsistencies can eventually lead to incorrect behavior, such as the inability to edit an agent's recipient list. You can periodically take the production system offline and validate the catalog, to be informed of and to take corrective action on inconsistencies.

Tasks in the Validation Process

The validation process performs the following tasks:

• Ensures that each object in the catalog is larger than zero bytes.
• Ensures that each item in the catalog has a valid corresponding .atr file.
• Ensures that each link in the catalog is valid.
• Ensures that the files in the account cache are valid.
• Ensures that all XML objects in the catalog pass schema validation.
• Attempts to repair object names that were damaged by ftp programs.

 Important Guidelines for Validating the Catalog

Before you validate the catalog, keep the following guidelines in mind:

• You must refresh the user GUIDs before validating the catalog. If you attempt to validate a catalog whose user GUIDs are not synchronized, then the validation process assumes that all accounts have been deleted and effectively removes all account information from the catalog.
• Use care when validating a catalog in a development environment, if that environment has a different security store from the production environment. If the validation is performed with a different security store, then many accounts might be removed from the catalog.
• When you turn on any validation of the catalog, all ACLs (that is, all privileges and every item's permissions) are "scrubbed," which means that dead accounts are removed from them and any changed items are written to disk. Therefore, even if you simply create a report without fixing any broken items automatically, you might find that the catalog is still extensively "changed."
• Before validating the catalog in a clustered environment, do one of the following:
• Shut down the Presentation Services cluster and run the validation directly against the cluster's catalog.
• Make a copy of the cluster's catalog and run the validation against that copy.
• Before using the 7-Zip utility to make a copy of a catalog, first shut down all nodes in the Presentation Services cluster or put all nodes in that cluster into Maintenance Mode (which is the recommended approach).
• Be aware that any changes that are made to the catalog online concurrently to the validation process are not included in the validation.

While backing up the catalog is always good practice, there is no practical difference between running validate against the catalog directly versus running the validation on a backup copy.