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
Cell Manager hardware aspects to consider
MS Windows, Red Hat Linux, Suse ES, and Sun Solaris10
Organizations are under growing pressure to support non-stop business operations without increasing
the IT budget. Given their position at the center of the IT infrastructure, servers play a critical role in
determining both the overall availability as well as the total cost of ownership of that infrastructure.
This certainly applies also to an important infrastructure component such as a HP Data Protector Cell
Manager server.
Today’s business requirements demand IT organizations deploy servers that are designed to be
powerful, reliable, and highly available. Leading technologies like redundant Ethernet connections,
network adapter teaming, memory management, and Smart Array controllers enable improved
flexibility and broad software compatibility. These innovations offer IT professionals the tools to
address high-availability platform challenges effectively, both now and in the future.
To enable high availability, a server must proactively respond to failures, both within the server and
the network to which it is attached. High availability requires that a system administrator manage a
server without having to be co-located with that server, and that the server remains available while a
failed component is repaired.
The first choice for a Cell Manager server on MS Windows, Red Hat Linux, Suse ES, and Sun Solaris10
combining all of the above mentioned characteristics is a server from the HP ProLiant server family.
At the time this white paper was compiled a HP ProLiant DL380 G5 (Generation 5) server was
providing all of the necessary features providing enough computing power and high availability.
A non-racked tower version (ML370 G5) of this model also exists.
The features in detail are:
• Intel
®
Xeon
™
Processors
• Advanced Memory Protection
• Redundant Cooling and Power
• RAID Technology
• Redundant Ethernet Connections
• Network Adapter Teaming
• ProLiant Essentials
• Intelligent Networking Pack
• Integrated Lights-Out Technology
QuickSpecs for the HP ProLiant DL380 G5 server can be found at:
http://h18004.www1.hp.com/products/quickspecs/12477_na/12477_na.pdf
Performance pack
The HP ProLiant DL380 G5 performance packs are necessary to configure a HP ProLiant DL380 G5
Performance Model. HP ProLiant DL380 G5 Performance model includes the latest performance
technologies and enterprise class availability features pre-installed for convenience and value. The
performance pack includes a second processor and a redundant power supply.
Processor
It is advisable to equip the Cell Manager server minimum with two Quad-Core Intel
®
Xeon
®
Processors
E5345 (2.33 GHz, 80 Watts, 1333 FSB) providing required processing power at relatively low
power consumption.
28