When a vaulting rule is created, modified, or deleted, the files must be relocated to their new home. This process is called revaulting.

Revaulting is necessary when a vaulting rule is modified to use another file vault or when a vaulting rule is deleted, which is equivalent to designating the object storage to be in a BLOB. Revaulting may also be needed when a change occurs in the domain or life cycle state of an object that holds content files. The revaulting process for such object changes can be done in the background, which is administered by the wt.fv.revaultOnChange property. The default setting for this property is true.

If you are not setting properties through a graphical user interface or in a mapping rules file, you add or edit properties with the xconfmanager utility. For more information, see Using the xconfmanager Utility.

Revaulting can be a resource-intensive activity, and it therefore it needs to be managed. To designate a vault for revaulting, you must create a schedule to specify when it will take place. At the scheduled time, the revaulting process launches and the contents of the vault are automatically relocated to another vault, moved from a vault to BLOB storage, or moved from a BLOB to a vault. Use the Remove unreferenced files option, available from the Vault Configuration window, to clean up the vault storage after the revaulting process.

The task of managing revaulting is primarily the routine of scheduling when the revaulting should occur for each vault and then periodically monitoring its progress.