HP StoreOnce 4430 HP StoreOnce Backup System Concepts and Configuration Guidel - Page 47

Configuring FC to support failover in a StoreOnce B6200 Backup system environment

Page 47 highlights

7 Configuring FC to support failover in a StoreOnce B6200 Backup system environment Autonomic failover Autonomic failover is a unique enterprise class feature of the HP B6200 StoreOnce Backup system. When integrated with various backup applications it makes it possible for the backup process to continue even if a node within a B6200 couplet fails. ISV scripts are usually required to complete this process. The failover process is best visualized by watching the video on: http:// www.youtube.com/watch?v=p9A3Ql1-BBs What happens during autonomic failover? At a logical level, all the virtual devices (VTL, NAS and replication) associated with the failing node are transferred by the B6200 operating system onto the paired healthy node of the couplet. The use of Virtual IP addresses for Ethernet and NPIV virtualization on the Fibre Channel ports are the key technology enablers that allow this to happen without manual intervention. • NAS target failover is via the Virtual IP system used in the HP B6200 Backup System - the service set simply presents the failed node Virtual IP address on the remaining node. • FC (VTL device) failover relies on the customer's fabric switches supporting NPIV, and NPIV being enabled and the zones set up correctly. Here the situation is more complex as several permutations are possible. NOTE: To prevent data corruption, the system must confirm that the failing node is shutdown before the other node starts writing to disk. This can be seen in the video where the "service set" is stopping. At a hardware level the active cluster manager is sending a shutdown command via the dedicated iLO3 port on the failing node. Email alerts and SNMP traps are also sent on node failure. The HP B6200 Backup System failover process can take 15 minutes or more to complete. The total time for failover is dependent on the system integrity checks, which are an integral part of the failover process, and the need to validate the deduplicated data stored.The following figure illustrates the failover timeline. Figure 24 Failover timeline Autonomic failover 47

  • 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
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122

7 Configuring FC to support failover in a StoreOnce B6200
Backup system environment
Autonomic failover
Autonomic failover is a unique enterprise class feature of the HP B6200 StoreOnce Backup system.
When integrated with various backup applications it makes it possible for the backup process to
continue even if a node within a B6200 couplet fails. ISV scripts are usually required to complete
this process. The failover process is best visualized by watching the video on:
h
t
tp://
w
w
w
.y
o
u
tu
be
.co
m/w
at
c
h?v=p9A3Ql1
-BB
s
What happens during autonomic failover?
At a logical level, all the virtual devices (VTL, NAS and replication) associated with the failing
node are transferred by the B6200 operating system onto the paired healthy node of the couplet.
The use of Virtual IP addresses for Ethernet and NPIV virtualization on the Fibre Channel ports are
the key technology enablers that allow this to happen without manual intervention.
NAS target failover is via the Virtual IP system used in the HP B6200 Backup System – the
service set simply presents the failed node Virtual IP address on the remaining node.
FC (VTL device) failover relies on the customer’s fabric switches supporting NPIV, and NPIV
being enabled and the zones set up correctly. Here the situation is more complex as several
permutations are possible.
NOTE:
To prevent data corruption, the system must confirm that the failing node is shutdown
before the other node starts writing to disk. This can be seen in the video where the “service set”
is stopping. At a hardware level the active cluster manager is sending a shutdown command via
the dedicated iLO3 port on the failing node. Email alerts and SNMP traps are also sent on node
failure.
The HP B6200 Backup System failover process can take 15 minutes or more to complete. The total
time for failover is dependent on the system integrity checks, which are an integral part of the
failover process, and the need to validate the deduplicated data stored.The following figure
illustrates the failover timeline.
Figure 24 Failover timeline
Autonomic failover
47