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
Existing IDB related notifications
Health Check Failed
Event/notification name HealthCheckFailed
What triggers the notifications?
A non-zero value returned by the
omnihealthcheck command. The
command returns zero if the following is true:
• The Data Protector services (RDS, CRS, MMD, omnitrig, and Inet) are active.
• The Data Protector media management database is consistent.
• At least one backup of the IDB exists.
For more information on this command, refer to the omnihealthcheck
man page. By default, Data Protector starts the Health Check (which runs
the omnihealthcheck command) once a day.
Default message level Critical
Message displayed
Health check message: <healthcheck_command> failed.
IDB Corrupted
Event/notification name IDBCorrupted
What triggers the notification? Corruption of a part of the IDB
Default message level Critical
Message displayed
Corruption in the <IDB_part> part of the Data Protector Internal
Database has been detected (<error_message>).
IDB Filename Conversion Needed
Event/notification name IDBFilenameConversionNeeded
What triggers the notifications?
A need for the IDB filename conversion that may arise during an upgrade
from Data Protector A.05.10 or earlier. If the conversion is not performed,
you may experience problems when browsing old files for restore. For
details, refer to the HP Data Protector Installation and Licensing Guide.
By default, Data Protector checks the IDB Filename Conversion Needed
condition once a day.
Default message level Minor
Message displayed
Filenames in the IDB have not been converted since upgrade to A.05.50.
IDB Purge Needed
Event/notification name IDBPurgeNeeded
What triggers the notifications?
By default, Data Protector checks the IDB Purge Needed condition once a
day as a part of checking and maintenance mechanism and triggers the
notification if:
• The time elapsed since the last IDB filename purge exceeds Days Last
Purge [days] (default, 180 days). At the same time, either the number of
filename records likely to be purged exceeds Num. Estimated Filenames
[mio] (default, 6 millions), or the estimated time needed for the purge
exceeds Estimated Time Purge [min] (default, 120 minutes).
• The number of filenames in the IDB exceeds Num. Filenames [mio]
(default, 100 millions).
Default message level Warning
Message displayed Filename purge should be run for Data Protector Internal Database.
16