HP D2D .HP D2D Backup System user guide (EH985-90907, March 2011) - Page 98

Bandwidth limiting

Page 98 highlights

Synchronization progress logging An event is always generated each time a mapping goes out of sync and goes back into sync. This field applies to periodic sync progress updates whilst the mapping remains out of sync, which results in emails (if emails are configured), but not SNMP traps. Use these fields to enable progress logging for Library and Share synchronization and to specify the logging interval. While the library or share is out of sync emails are sent periodically indicating how many slots or entries are still out of sync. This information is also logged to the user Event Log. One email is sent for each log entry made for each library or share that is out of sync. Out of Sync Notification Settings Use these fields to specify the amount of time a mapping needs to be out of sync before a sync issue is shown in the Issue tab, and an event is generated, resulting in an entry in the user Event Log, and also an email and/or an SNMP trap if the appliance is configured to send these. These notifications are in addition to a standard notification email sent whenever a mapping first becomes unsynchronized and another when synchronization is achieved. Configure Replication Ports Replication ports should only be changed if replication is blocked by a router on the WAN. They must be the same on both source and target appliances. If in doubt, do NOT change them. IMPORTANT: If replication needs to take place through a firewall, the network administrator will need to open (TCP) ports 9387 (Command protocol) and 9388 (Data protocol) to allow the replication traffic to pass to and from the HP StoreOnce Backup Systems. If necessary and the StoreOnce Backup Systems conflict with another device on the network, these ports can be changed from the defaults in the General Settings. Bandwidth limiting This tab allows you to apply a general bandwidth setting and to configure bandwidth limiting windows. Bandwidth limiting can be used to avoid saturating the WAN with low bandwidth replication, thus freeing up bandwidth for other processes and applications that you may have running. A minimum of 2Mbps per concurrent job is recommended. At least 512kbps per concurrent job is required for reliable operation. A bandwidth usage calculator is provided to generate a recommended bandwidth limit from WAN speed information and percentage usage information, which is provided in the Maximum WAN Usage and WAN Speed fields. These limits apply to all outbound replication jobs from this local appliance. 98 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
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210

An event is always generated each time a mapping goes out of sync and
goes back into sync. This field applies to periodic sync progress updates
whilst the mapping remains out of sync, which results in emails (if emails are
configured), but not SNMP traps. Use these fields to enable progress logging
for Library and Share synchronization and to specify the logging interval.
While the library or share is out of sync emails are sent periodically indicating
how many slots or entries are still out of sync. This information is also logged
to the user Event Log. One email is sent for each log entry made for each
library or share that is out of sync.
Synchronization progress log-
ging
Use these fields to specify the amount of time a mapping needs to be out of
sync before a sync issue is shown in the Issue tab, and an event is generated,
resulting in an entry in the user Event Log, and also an email and/or an
SNMP trap if the appliance is configured to send these. These notifications
are in addition to a standard notification email sent whenever a mapping
first becomes unsynchronized and another when synchronization is achieved.
Out of Sync Notification Settings
Replication ports should only be changed if replication is blocked by a router
on the WAN. They must be the same on both source and target appliances.
If in doubt, do
NOT
change them.
Configure Replication Ports
IMPORTANT:
If replication needs to take place through a firewall, the network administrator will need to open (TCP)
ports 9387 (Command protocol) and 9388 (Data protocol) to allow the replication traffic to pass to
and from the HP StoreOnce Backup Systems. If necessary and the StoreOnce Backup Systems conflict
with another device on the network, these ports can be changed from the defaults in the General
Settings.
Bandwidth limiting
This tab allows you to apply a general bandwidth setting and to configure bandwidth limiting windows.
Bandwidth limiting can be used to avoid saturating the WAN with low bandwidth replication, thus
freeing up bandwidth for other processes and applications that you may have running. A minimum
of 2Mbps per concurrent job is recommended. At least 512kbps per concurrent job is required for
reliable operation. A bandwidth usage calculator is provided to generate a recommended bandwidth
limit from WAN speed information and percentage usage information, which is provided in the
Maximum WAN Usage
and
WAN Speed
fields. These limits apply to all outbound replication jobs
from this local appliance.
Replication
98