How to achieve over 2 TB/hr network backup with Integrity entry-class servers running HP-UX 11i v3

25
 Single, Persistent DSFs per device (SAN agility of Device Special Files using binding
of LUN WWIDs)
 Interrupt Control (management of interrupt configuration and handing with the intctl
command)
o When using a network link aggregation such as HP Auto Port Aggregation (APA), initially
monitor the network traffic on the physical links to ensure the network traffic is being
balanced as expected. Once initial setup and configuration is completed, occasionally
monitor the network link loads to ensure continued optimal network load balancing and
throughput.
o Backup performance testing shows only a minor difference between auto-balancing and
manual balancing of data streams for optimal backup throughput.
o To ensure optimal recovery of data, manually segment and balance the client backup data
streams across multiple backup devices, rather than relying on auto-balancing.
o Make background copies of each client’s backup data, storing them on a single storage
device for collocation of client data, enabling a less complex recovery when required. This is
especially important for the most business-critical application servers, as recovery of these
servers must happen as quickly as possible.
Given that each backup/restore environment is unique, to determine the best settings and
configuration for your environment, HP recommends that you perform tuning analyses and
optimization tests similar to those performed in this characterization effort.
Conclusion
This characterization effort confirms that the HP rx3600 and rx6600 Integrity servers, running HP-UX
11i v3, make ideal, robust, and highly reliable network backup servers. In our testing environment,
using commonly-used technologies, the smaller rx3600 delivers an amazing 517 MB/s (1.77 TB/hr)
of network backup throughput, while the rx6600 delivers 643 MB/s (2.2 TB/hr) of network backup
throughput. The rx6600 has plenty of processing power and system resources to scale further or to
perform additional business-critical services. If hardware footprint space is a concern, two rx3600
servers could be configured for network backup in place of an rx6600, occupying almost the same
footprint while delivering an astounding total network backup throughput of 1034 MB/s (over 3.5
TB/hr). What is more, when the two rx3600 servers are configured as part of an HP Serviceguard
cluster, they can provide highly-available data protection services.
Table 3 summarizes the differences between an rx3600 and rx6600 server.
Table 3: Network Backup Throughput for rx3600 and rx6600 servers
Backup
Server
CPUs Memory Server
Height
Network
Backup
Throughput
MB/s
Network
Backup
Throughput
TB/hr
Integrity
rx3600 server
2 dual-core
9140M
processors
16 GB DDR2 4 EIA
units
517 MB/s
1.77 TB/hr
Integrity
rx6600 server
4 dual-core
9140N
processors
32 GB DDR2 7 EIA
units
643 MB/s
2.2 TB/hr