Filter
Top Products
Managing the Data Protector Internal Database
Maintaining the IDB
Chapter 9402
Maintaining the IDB
Once you have configured the IDB, you need to perform IDB
maintenance tasks in the following cases:
• the IDB is running out of space
If configured, the Low Database Space notification informs you
about this.
• the IDB needs a file version purge
With the OmniBack II A.03.50/A.03.51 and earlier databases, the
level of the granularity of the purge was at the object level. Now, the
granularity of the purge is the complete medium. This means that the
catalog protection for all object versions on the medium must expire
before the file version records are purged. Then, the related medium
binary file containing the detail catalog is removed. This purges many
file versions in a very short time. This happens automatically on a
daily basis. Obsolete sessions and messages are also purged
automatically.
• the IDB needs a filenames purge
Purging filenames was a regular maintenance task in OmniBack II
A.03.50/A.03.51 and earlier versions. With the OmniBack II A.04.10
release, the frequency is reduced to once per year in an environment
that can generate 100,000 obsolete filenames per day. You will be
notified automatically if the filenames purge is needed. Filenames
purge can be executed selectively on a per host basis. The operation
must run exclusively, so no backups can run concurrently. This purge
takes more time to execute than in the previous version of Data
Protector.
• the dynamics of the client system are high or critical
If configured, the System Dynamics report informs you about this.
• you want to move the IDB to a different Cell Manager
• you want to check the size of the IDB
The Database Size report informs you of the size of the IDB.
• the IDB does not work properly (might be corrupted) and you want to
check its consistency