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

Balancing Many-to-One replication, the four replication target nodes.

Get HP StoreOnce 4430 PDF manuals and user guides View all HP StoreOnce 4430 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 103 highlights

the necessary data is already seeded on the B6200 for Remote Site A and the synchronization process happens very quickly. In some scenarios where a customer has larger remote storage locations the floating StoreOnce process can be used together with the smaller locations seeding over the WAN link. Another consideration is the physical logistics for some customers with 100+ locations, some being international locations. The floating StoreOnce and co-location will be difficult, so the only option is to schedule the use of increased bandwidth connections along with their infrastructure needs. The schedule is used to perform seeding at timed, phased slots. Balancing Many-to-One replication For the many-to-one replication scenario, it is probably better to load balance the number of incoming replication sources across the available nodes as shown in the diagram below. In Figure 25 we show the many-to-one replication scenario where we have grouped remote sites (VTL and NAS) together into bundles and have them replicating into multiple dedicated replication target devices. The current recommendation with the HP B6200 Backup System is to keep the same relationship between remote site VTLs and replication target VTLs, namely a 1:1 mapping. The deployment illustrated has the following benefits: • Load balancing of remote sites: 40 sites are divided by 4 and then presented in bundles of 10 to the replication targets. As more remote sites come on line they are also balanced across the four replication target nodes. • Site B backup devices can be managed and added to easily, and their loading on the node accurately monitored. Similarly, the replication target nodes have a single function (replication targets) which makes their behavior more predictable. • In a failover situation, the performance impact on either backup or replication is likely to be lower because the backup load at Site B nodes and the replication load at Site B nodes are likely to run in separate windows at separate times. Many to One configurations 103

  • 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
the necessary data is already seeded on the B6200 for Remote Site A and the synchronization
process happens very quickly.
In some scenarios where a customer has larger remote storage locations the floating StoreOnce
process can be used together with the smaller locations seeding over the WAN link.
Another consideration is the physical logistics for some customers with 100+ locations, some being
international locations. The floating StoreOnce and co-location will be difficult, so the only option
is to schedule the use of increased bandwidth connections along with their infrastructure needs.
The schedule is used to perform seeding at timed, phased slots.
Balancing Many-to-One replication
For the many-to-one replication scenario, it is probably better to load balance the number of
incoming replication sources across the available nodes as shown in the diagram below.
In Figure 25 we show the many-to-one replication scenario where we have grouped remote sites
(VTL and NAS) together into bundles and have them replicating into multiple dedicated replication
target devices. The current recommendation with the HP B6200 Backup System is to keep the same
relationship between remote site VTLs and replication target VTLs, namely a 1:1 mapping.
The deployment illustrated has the following benefits:
•
Load balancing of remote sites: 40 sites are divided by 4 and then presented in bundles of
10 to the replication targets. As more remote sites come on line they are also balanced across
the four replication target nodes.
•
Site B backup devices can be managed and added to easily, and their loading on the node
accurately monitored. Similarly, the replication target nodes have a single function (replication
targets) which makes their behavior more predictable.
•
In a failover situation, the performance impact on either backup or replication is likely to be
lower because the backup load at Site B nodes and the replication load at Site B nodes are
likely to run in separate windows at separate times.
Many to One configurations
103