HP 12000 HP VLS Solutions Guide Design Guidelines for Virtual Library Systems - Page 114

Dividing the Backup Jobs by Priority Level

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

Page 114 highlights

Figure 51 Dividing the Backup Jobs by Priority Level On the target device you also have the ability to limit replication traffic beyond limiting the replication time windows. This can be done by controlling how many concurrent replication jobs are allowed per replication target, and optionally controlling the maximum Mbytes/sec throughput of a single replication job. (This is set as a global configuration value that applies across all replication targets on that device.) In this way, the amount of replication traffic can be controlled to each replication target on a target device. Setting the maximum number of concurrent jobs per replication target needs to take into account various factors such as VLS device hardware limits and the network latency of the replication link: • In order to get maximum replication throughput, you must scale the number of concurrent replication jobs per target depending on the number of nodes used for replication in the target device. For example, if you have a 4-node VLS configured as a single replication target, you should set the maximum number of jobs for the replication target to be 28 (based on four nodes each with a maximum of 7 concurrent replication jobs per node). • There is a hardware limit of seven concurrent replication jobs per VLS node, so if you have multiple replication targets on a VLS (such as many-to-one deployment) you need to ensure that you do not exceed the hardware limit when you configure the "Maximum Simultaneous Transfers" on each replication target. ◦ For example, if you have four replication targets configured on a 2-node VLS, you do not want to set each Target to allow seven concurrent jobs because this would add up to 28 concurrent jobs across all four targets but you only have 14 concurrent jobs capability in the 2-node configuration. So if all the replication windows were the same across the four source devices, you would potentially starve some of the replication targets. (If you had non-overlapping replication windows then there would not be any contention issues.) ◦ Another example would be an active-active configuration where you had a 1-node VLS device, because then you have to share the hardware limit of seven replication jobs across both the outgoing and incoming replication jobs. In this case you could leave the default setting of four concurrent jobs in the target thus leaving at least three jobs for the outgoing replication traffic. • The network latency can affect how many concurrent replication jobs are needed in each replication target. The VLS replication incorporates latency-acceleration technology, but with longer network latencies this still requires some level of concurrent replication jobs to saturate the replication link as shown in Table 22 (page 115). 114 Replication

  • 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
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
Figure 51 Dividing the Backup Jobs by Priority Level
On the target device you also have the ability to limit replication traffic beyond limiting the
replication time windows. This can be done by controlling how many concurrent replication jobs
are allowed per replication target, and optionally controlling the maximum Mbytes/sec throughput
of a single replication job. (This is set as a global configuration value that applies across all
replication targets on that device.) In this way, the amount of replication traffic can be controlled
to each replication target on a target device.
Setting the maximum number of concurrent jobs per replication target needs to take into account
various factors such as VLS device hardware limits and the network latency of the replication link:
•
In order to get maximum replication throughput, you must scale the number of concurrent
replication jobs per target depending on the number of nodes used for replication in the target
device. For example, if you have a 4-node VLS configured as a single replication target, you
should set the maximum number of jobs for the replication target to be 28 (based on four
nodes each with a maximum of 7 concurrent replication jobs per node).
•
There is a hardware limit of seven concurrent replication jobs per VLS node, so if you have
multiple replication targets on a VLS (such as many-to-one deployment) you need to ensure
that you do not exceed the hardware limit when you configure the “Maximum Simultaneous
Transfers” on each replication target.
◦
For example, if you have four replication targets configured on a 2-node VLS, you do not
want to set each Target to allow seven concurrent jobs because this would add up to 28
concurrent jobs across all four targets but you only have 14 concurrent jobs capability
in the 2-node configuration. So if all the replication windows were the same across the
four source devices, you would potentially starve some of the replication targets. (If you
had non-overlapping replication windows then there would not be any contention issues.)
◦
Another example would be an active-active configuration where you had a 1-node VLS
device, because then you have to share the hardware limit of seven replication jobs across
both the outgoing and incoming replication jobs. In this case you could leave the default
setting of four concurrent jobs in the target thus leaving at least three jobs for the outgoing
replication traffic.
•
The network latency can affect how many concurrent replication jobs are needed in each
replication target. The VLS replication incorporates latency-acceleration technology, but with
longer network latencies this still requires some level of concurrent replication jobs to saturate
the replication link as shown in
Table 22 (page 115)
.
114
Replication