HP Data Protector Software Cell Manager Planning and Sizing
Table Of Contents
- Executive summary
- Solution description
- Cell Manager software topology
- IDB architecture
- Why should you configure the IDB?
- Regular IDB backups
- IDB notifications
- Limitations
- IDB Growth and Performance
- IDB key growth factors
- IDB key performance factors
- IDB key growth and performance parameters
- Influence of logging level on IDB
- Example: Changing of logging level for filesystem backup
- Influence of catalog protection on IDB
- Example: Changing of catalog protection of a backup
- Recommended usage of logging level and catalog protection
- Use different logging levels in the same cell
- Different logging levels for ObjectCopies
- Specifics for small cells
- Specifics for large cells
- Maintenance of DCBF directories
- Cell Manager hardware aspects to consider
- Cluster support for Data Protector software Cell Manager
- Security
- IDB space consumption example
- Cell Manager requirements
- For more information
The internal database consists of the following parts:
• MMDB (Media Management Database)
• CDB (Catalog Database)
• DCBF (Detail Catalog Binary Files)
• SMBF (Session Messages Binary Files)
• SIBF (Server-less Integrations Binary Files)
Each of the IDB parts stores certain specific Data Protector information (records), influences the IDB
size and growth in different ways, and is located in a separate directory on the Cell Manager.
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 local MMDB can be merged to a central Cell
Manager system to create the Central Media Management Database (CMMDB).
Media Management Database (MMDB)
MMDB records
The Media Management Database stores information about the following:
• Configured devices, libraries, library drives, and slots
• Data Protector media
• Configured media pools and media magazines
MMDB size and growth
The MMDB does not grow very big in size. The largest part of the MMDB is typically occupied by
information about the Data Protector media. Space consumption is in range of 30 MB.
Using a large amount of media can result in high memory consumption of IDB and cause a backup to
fail. You can calculate the memory usage on HP-UX using the following formula:
RDSSize=2048 KB + n*(0.7KB*m+1.5KB*a)
Where:
• n is the minimum value of the number of parallel strings or the number of RPC threads set in
rdmserver.ini. Default is 3.
• m is the number of media in a selected pool,
• a is the number of media in IDB.
The average sizes are the following:
• 0.7 KB is the size of a medium record in IDB (per pool)
• 1.5 KB is the size of a medium record in a binary file (all media)
MMDB location
Information about configured backup devices is stored in the devices.dat file in the
<Data_Protector_program_data>\db40\datafiles\mmdb directory (on Windows Server 2008),
<Data_Protector_home>\db40\datafiles\mmdb directory (on other Windows systems) or
/var/opt/omni/server/db40/datafiles/mmdb (on UNIX systems).
7