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

14
Figure 8: Client backup statistics using Data Protector
The graph in Figure 8 indicates that for backup operations, system memory is a greater limiting factor
than CPU or storage connectivity type. The rx2600 system with 2 GB of memory was able to achieve
only 106 MB/s of backup data throughput before being limited by memory (memory utilization
reached 98%). Processing power on this two-processor system reached slightly over 80% utilization,
showing that the two processors on this client had plenty of processing capacity to saturate a 1GbE
port for network backup. Note that with an additional 2 GB of memory, the two-processor rx2600
system was more capable of attaining saturation of the 1GbE port limit of 113 MB/s.
For optimal network backup throughput for a client using a 1GbE port, the results suggest using a
minimum of two CPUs and 4 GB of memory for each client.
Client restore performance statistics
The main limiting factor with data restore is writing the restored data to storage through the file
system. The same conclusions from the backup operation are true for restore operation: the more
memory available in the system, the better is performance of the restore operation.
Figure 9 shows the restore throughput results for each of the four client configurations.
0
20
40
60
80
100
120
rx2600/2/2GB rx2600/2/4GB rx3600/4/8GB rx6600/2/4GB
CPU %
Memory %
Backup MB/s