HP StoreOnce B6000 HP B6200 Backup System Recommended Configuration Guidelines - Page 25

Scenario 2 - Configuring shares and libraries to align with, backup job segmentation

Page 25 highlights

Scenario 2 - Configuring shares and libraries to align with backup job segmentation Once all virtual IP addresses are allocated, the next step is to use each node in a way that best matches the backup environment. Each node in an HP B6200 Backup System is similar to an existing HP D2D4324 Backup System in terms of capacity, throughput and device support. The existing best practices for single-node StoreOnce devices therefore apply. These can be downloaded from the website below http://bizsupport2.austin.hp.com/bc/docs/support/SupportManual/c02511912/c02511912.pdf One important difference to note is that the Ethernet network is used only for NAS shares and replication. Virtual tape libraries are always configured for Fibre Channel. Generic best practices A summary of best practices is included below. Most are common to both single-node D2D Backup Systems and the HP B6200 Backup System. 1. Always use the Sizer tool to size for performance. • The Sizer tool uses mature store performance data and information only available within the sizing tool to size replication and housekeeping. http://www.hp.com/go/d2dsizer 2. Always ensure the HP B6200 Backup System has the latest firmware updates because improvements are continually being integrated. 3. Understand that backup throughput depends on the number of concurrent backup jobs that can be configured to run simultaneously. If only single-stream backup is possible, tape may be faster. Re-educate customers into configuring multiple concurrent backups for best backup throughput. An HP StoreOnce B6200 Backup System device with 12 streams achieves 90% maximum throughput. 4. Make allowances for housekeeping. Every time a tape backup is overwritten or a NAS shares is re-opened, the deduplication store must be scanned and the hash code usage states updated. This is an I/O intensive operation and should be scheduled to occur in periods of low activity. On the HP B6200 there is a Housekeeping option in the Navigator that graphically displays the rate at which housekeeping jobs are being processed. The processing rate should always be higher than the incoming housekeeping job rate. See Scenario 6 - Monitoring the HP B6200 Backup System. 5. Make allowances for replication windows. Backup, replication and housekeeping should all be allocated their own "window" in which to execute and should not overlap. Once these activities overlap performance becomes unpredictable. Replication and housekeeping windows are configurable within the HP B6200 GUI. 6. Understand how to benefit from network bonding and Fibre Channel load balancing. 25

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89

25
Scenario 2 - Configuring shares and libraries to align with
backup job segmentation
Once all virtual IP addresses are allocated, the next step is to use each node in a way that best
matches the backup environment. Each node in an HP B6200 Backup System is similar to an existing
HP D2D4324 Backup System in terms of capacity, throughput and device support. The existing best
practices for single-node StoreOnce devices therefore apply. These can be downloaded from the
website below
One important difference to note is that the Ethernet network is used only for NAS shares and
replication. Virtual tape libraries are always configured for Fibre Channel.
Generic best practices
A summary of best practices is included below. Most are common to both single-node D2D Backup
Systems and the HP B6200 Backup System.
1.
Always use the Sizer tool to size for performance.
The Sizer tool uses mature store performance data and information only available
within the sizing tool to size replication and housekeeping.
2.
Always ensure the HP B6200 Backup System has the latest firmware updates because
improvements are continually being integrated.
3.
Understand that backup throughput depends on the number of concurrent backup jobs that
can be configured to run simultaneously.
If only single-stream backup is possible, tape may be faster.
Re-educate customers into configuring multiple
concurrent backups for best backup
throughput.
An HP StoreOnce B6200 Backup System device with 12 streams achieves 90%
maximum throughput.
4.
Make allowances for housekeeping.
Every time a tape backup is overwritten or a NAS shares is re-opened, the
deduplication store must be scanned and the hash code usage states updated. This is
an I/O intensive operation and should be scheduled to occur in periods of low
activity.
On the HP B6200 there is a
Housekeeping
option in the Navigator that graphically
displays the rate at which housekeeping jobs are being processed. The processing
rate should always be higher than the incoming housekeeping job rate. See
Scenario
6 - Monitoring the HP B6200 Backup System.
5.
Make allowances for replication windows.
Backup, replication
and housekeeping should all be allocated their own “window” in
which to execute and should not overlap. Once these activities overlap performance
becomes unpredictable. Replication and housekeeping windows are configurable
within the HP B6200 GUI.
6.
Understand how to benefit from network bonding and Fibre Channel load balancing.