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
Table 2 lists the maximum configurable sizes and limits for the HP Data Protector catalog datafiles.
Table 2: Catalog datafiles and extensions - maximum settings and limits
Data Protector 6.0 ≥ Data Protector 6.1
Size of any IDB datafile
(base file or extension
file)
2 GB 2 GB
Max size of fnames:
(base file and all
extensions)
32 GB 48 GB
Max size of fn1...fn4
(base file and all
extensions)
8 GB
(16 GB with patch)
16 GB
Max size of dirs.dat (base
file and all extensions)
8 GB
(16 GB with patch)
16 GB
CDB (objects and positions) size and growth
The CDB also records object names and media positions. It occupies minor share of space in the IDB.
Space consumption is in range of up to 1 GB for a backup environment.
Prior extending the IDB the backup administrator should check the currently configured tables and
their location and size.
Figure 4 depicts a summary of currently configured tables, their size, and location.
Figure 4: Summary of IDB tablespace location and size
9