IDB maintenance

Once you configure the IDB, its maintenance is reduced to a minimum, mainly acting on notifications and reports.

IDB recovery

An IDB recovery is needed if some of the IDB files are missing or corrupted. The recovery procedure depends on the level of corruption.

For detailed information, see the online Help index: “IDB, recovery“.

IDB growth and performance

For proper IDB configuration and maintenance it is necessary to understand the key factors that influence the IDB growth and performance, as well as the key tunable parameters that you can adapt to your needs, and thus handle the growth and performance of the IDB as efficiently as possible.

Key IDB growth and performance factors

The key factors for IDB growth and performance are the following:

Logging level settings Logging level defines the amount of detail written to the IDB during backup. The more detailed logging level you use, the greater influence it has on the IDB. For details, see IDB growth and performance: key tunable parameters” on page 198.

Catalog protection settings Catalog protection determines how long the information about backed up data is available in the IDB. The longer period of catalog protection you set, the greater influence it has on the IDB. For details, see IDB growth and performance: key tunable parameters” on page 198.

Number of backed up files Data Protector keeps track of each file and each version of that file. Different backup types impact the IDB differently. For information on backup types, see Full and incremental backups” on page 71.

Number of backups

The more often you perform a backup, the more information is stored in the IDB.

Filesystem dynamics The number of files created and removed between backups can have a significant impact on the growth of the filenames part of the IDB. The Report on System Dynamics gives you information about the system dynamics. You can avoid the IDB growth due to filesystem dynamics by using the

Log Directories logging level.

Concepts guide

197