HP B6960-96035 manual IDB operation, Serverless Integrations Binary Files Sibf, During backup

Serverless Integrations Binary Files (SIBF)

SIBF records

The Serverless Integrations Binary Files stores raw NDMP restore data. This data is necessary for restore NDMP objects.

SIBF size and growth

The SIBF does not grow very big in size. For more details, see “IDB size estimation

”on page 203. For NDMP backups, the SMBF grows proportionally to the number of objects backed up. Approximately 3 KB are used for each backed up object.

SIBF location

The SIBF is located in the following directory:

•On Windows Server 2008: Data_Protector_program_data\db40\meta

•On other Windows systems: Data_Protector_home\db40\meta

•On UNIX systems: /var/opt/omni/server/db40/meta

IDB operation

During backup

When a backup session is started, a session record is created in the IDB. Also, for each object and each object mirror in the session, an object version record is created. All these records are stored in the CDB and have several attributes. The Backup Session Manager updates media during a backup. All media records are stored in the MMDB and are allocated for a backup depending on policies.

When a data segment is written to the tape and then to a catalog segment, then for each object version that was part of this data segment, a media position record is stored in the CDB. In addition, the catalog is stored in the DC (Detail Catalog) binary file. One DC binary file is maintained per Data Protector medium. A DC binary file is named MediumID_TimeStamp.dat. If a medium is overwritten during a backup, its old DC binary file is removed and a new one is created.

All session messages generated during backups are stored in session messages binary files (the SMBF part).

194 The Data Protector internal database