Filter
Top Products
Managing the Data Protector Internal Database
The IDB Architecture
Chapter 9386
• Backup sessions and restore sessions. This is the
copy of the information sent to the Data Protector
Monitor window.
• Backed up objects and their versions.
• Pathnames of backed up files (filenames) together
with client system names. Filenames are stored
only once per client system. The filenames created
between backups are added to the CDB.
• Positions of backed up objects on media. For each
backed up object, Data Protector stores information
about the media and data segments used for the
backup.
DCBF The Detail Catalog Binary Files part stores file version
information. This is information about backed up files,
such as file size, modification time,
attributes/protection, and so on.
One DC (Detail Catalog) binary file is created for each
Data Protector medium used for backup. When the
medium is overwritten, the old binary file is removed
and a new one is created.
SMBF The Session Messages Binary Files part stores session
messages generated during backup sessions and
restore sessions. One binary file is created per session.
The files are grouped by year and month.
SIBF The Serverless Integrations Binary Files part stores
raw NDMP restore data. This data is necessary for
restore of NDMP objects.
The MMDB and CDB parts are implemented using an embedded
database consisting of tablespaces. This database is controlled by the rds
database server process. All changes to the MMDB and CDB are updated
using transaction logs. CDB (objects and positions) and MMDB present
the core part of IDB.
The DCBF, SMBF, and SIBF parts of the IDB consist of binary files.
Updates are direct (no transactions).
In the Manager-of-Managers (MoM) environment, the MMDB can be
moved to a central system to create the Central Media Management
Database (CMMDB).