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

Whilst Autonomic failover - configuration manual

Page 7 highlights

19. When HP B6200 Autonomic failover is deployed, IP failover is handled automatically because the device uses VIF (Virtual network interface). But for Fibre Channel failover to work the customer SAN infrastructure MUST support NPIV (N Port virtualization) and the zoning must be done by using World Wide Names (WWN). For more details see Appendix A - FC failover supported configurations. 20. Whilst Autonomic failover is automatic, the "Failback" process (after a node is repaired) is manual and performed from the GUI or the CLI. Once failed over, a single node is handling the load of two nodes and reduced performance may result. An essential part of the best practices is testing the failover and failback scenario to ensure the performance during a failed-over situation is adequate. The customer has a choice at sizing time. Either fully load each node with work; if failover occurs, the customer will see a reduction in throughput because one node is doing all the work. Or oversize the nodes to use only 50% of their throughput; if failover occurs, there will be no perceived reduction in performance. 21. HP Autonomic failover also has some ISV dependencies in the form of scripts that need to be integrated into the post-execution fields of the backup software. Ensure the necessary ISV scripts or utilities are loaded on the media servers or in the backup jobs to ensure B6200 Autonomic failover works successfully. Validation of the particular ISV scripts with the HP B6200 Backup System should be part of the commissioning process. These scripts and utilities can be made selective, so that only the most important backup jobs are required to run on the single remaining node when one node fails. This reduces the overall load on the single remaining node. See Scenario 5 - How to get the best from HP autonomic . 22. Regularly check for software updates at Software Upgrades and use the .rpm package installer process documented in the HP B6200 StoreOnce Backup System user guide to upgrade the software. Always read the release notes before upgrade; these also contain installation instructions as well as information about any hardware firmware component revisions. Sales of all HP B6200 Backup System come with a compulsory Install and Startup service and an optional Configuration service. 7

  • 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

7
19.
When HP B6200 Autonomic failover is deployed, IP failover is handled automatically
because the device uses VIF (Virtual network interface). But for Fibre Channel failover to work
the customer SAN infrastructure MUST support NPIV (N Port virtualization) and the zoning
must be done by using World Wide Names (WWN). For more details see
Appendix A
FC
failover supported configurations
.
20.
Whilst Autonomic failover
is automatic, the “Failback” process (after a node is repaired)
is
manual and performed
from
the GUI or the CLI.
Once failed over, a single node is
handling the load of two nodes and reduced performance may result. An essential part of the
best practices is testing the failover and failback scenario to ensure the performance during a
failed-over situation is adequate.
The customer has a choice at sizing time. Either fully load each node with work; if failover
occurs, the customer will see a reduction in throughput because one node is doing all the
work. Or oversize the node
s
to use only 50% of their throughput; if failover occurs, there will
be no perceived reduction in performance.
21.
HP Autonomic failover also has some ISV dependencies in the form of scripts that need to be
integrated into the post-execution fields of the backup software. Ensure the necessary ISV
scripts or utilities are loaded on the media servers or in the backup jobs to ensure B6200
Autonomic failover works successfully. Validation of the particular ISV scripts with the HP
B6200 Backup System should be part of the commissioning process.
These scripts and utilities can be made selective, so that only the most important backup jobs
are required to run on the single remaining node when one node fails. This reduces the
overall load on the single remaining node. See
Scenario 5 - How to get the best from HP
autonomic
.
22.
Regularly check for software updates at
Software Upgrades
and use the .rpm package
installer process documented in the
HP B6200 StoreOnce Backup System user guide
to
upgrade the software. Always read the release notes before upgrade; these also contain
installation instructions as well as information about any hardware firmware component
revisions.
Sales of all HP B6200 Backup System come with a compulsory Install and Startup service and an
optional Configuration service.