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
Regular IDB backups
An essential part of the Internal Database configuration is configuring the backup of the IDB itself.
Once the IDB backup is performed regularly, the most important preparation for recovery in case of
a disaster is done. The IDB recovery is essential for restore of other backed up data in case of a
Cell Manager crash.
Consider the following when configuring the IDB backup:
• Create a separate backup specification for the IDB backup. This simplifies scheduling and restoring
in case of a disk crash. To create an IDB backup specification, select the IDB object and follow the
standard backup procedure.
• Schedule the IDB backup to be performed once per day. This verifies that you always have an almost
up-to-date backup of the IDB. Schedule it to run when there is low activity on the Cell Manager.
• Perform the IDB backup using a separate media pool, on separate media, on a specific device. Use
a real tape device or file jukebox—no file library. Media from a file library cannot be imported in
case of a Cell Manager crash. Make sure you know which media you use for the IDB backup. You
can configure a Session Media Report to be informed about the media used for the backup. This
greatly simplifies eventual restore. If possible, use a device locally connected to the Cell Manager.
• Set data protection and catalog protection to a few days only. Set these options such that at least
the last two IDB backup versions are protected.
• Always have the Check the Internal Database option enabled (default).
• Do not overwrite the previous IDB backup with the new one (keeping several copies is suggested).
What Happens During the IDB Backup?
During the IDB backup, Data Protector:
• Checks the consistency of the IDB to prevent backing up and later restoring a corrupted IDB
For this to happen, you need to have the Check IDB option enabled (default). The check operation
takes approximately 1.5 hours for a 10-GB database with the fnames.dat file size of 1 GB.
• Backs up the IDB online
Other backup sessions or restore sessions can run during the IDB backup, however, this is not
recommended.
• Backs up all the Data Protector configuration data, including the data on backup devices, backup
specifications, and schedules
This simplifies recovery in case of a disaster.
• The IDB backup process creates an OmniDB entry in the media.log file which allows identifying
what tape was used for last IDB backup
This is extremely useful in case the IDB is lost and needs to be recovered from tape.
Only one IDB backup can run at a time.
Note:
Additional information about IDB backup tasks and IDB recovery methods
can be found in the Data Protector software online help. Start the online
help and search for “IDB, recovery.”
14