Removing the detail catalog
When the detail catalog is removed for a specific medium, its DC binary file is removed. The same result is achieved by removing the catalog protection for all object versions and object copies on that medium (the next daily maintenance of DC binary files removes the binary file). All other records stay in the CDB and MMDB and it is possible to run a restore from such media (however, browsing is not possible).
Filenames purge
DC binary files show whether a given file is backed up on a related medium or not, but the filenames are actually stored in the CDB. A filename is considered “used” if it is marked as backed up in at least one DC binary file. Over time, it can happen that a large number of filenames are not used. To remove such filenames, Data Protector scans all DC binary files and then removes unused filenames.
File versions purge
When the catalog protection of all object versions stored on a specific medium expires, automatic daily maintenance of DC binary files removes the respective binary file.
Overview of IDB management
IDB configuration
One of the most important steps in setting up your Data Protector backup environment is to configure the IDB. The initial configuration enables you to set your internal policies regarding IDB size, the location of IDB directories, the IDB backup necessary in case of IDB corruption or a disaster, and the configuration of IDB reports and notifications.
IMPORTANT:
It is highly recommended to schedule an IDB backup to be performed on a daily basis. Creating a backup specification for the IDB backup is part of the IDB configuration.
196 | The Data Protector internal database |