Managing the Data Protector Internal Database

Maintaining the IDB

Purging Obsolete Filenames

During the purge process, Data Protector automatically checks for and purges obsolete filenames from the IDB to free up space for new information. A filename becomes obsolete when there are no file versions for the filename in the IDB.

Use the Internal Database Purge Preview Report and Internal Database Purge Report to get more information about the purge. Refer to “Configuring the Database Reports and Notifications” on page 400.

How to Purge Purge the IDB when no other backups are running on the Cell Manager.

Obsolete IDB Run the following command:

Filenames

omnidbutil -purge -filenames

You can limit the purge to one or more clients by running the following command:

omnidbutil -purge -filenames <host_1 ... host_n>

Data Protector skips purging filenames on the clients that have fewer than 1,000,000 obsolete filenames. In order to purge filenames on these clients as well, use the -forcesubcommand.

Extending the Database Size

It is required to extend the IDB size for the following reasons:

•The space for the filenames is consumed and another fnames.dat file is needed.

•More disk space is needed for the detail part of the IDB (file versions and attributes)

You can extend the size of the IDB in either of two ways:

•By creating new DC (Detail Catalog) directories and, possibly, locating them on different disks.

•By creating additional fnames.dat files.

Creating New DC Directories

You create a new DC directory using the Internal Database context in the Data Protector Manager. See Figure 9-3 on page 396. For detailed steps, refer to the online Help index keyword “creating DC directories”.

408

Chapter 9