HP StorageWorks 6000 HP StorageWorks VLS and D2D Solutions Guide (AG306-96028, - Page 96

Mapping Configuration, Add Target Appliance, as if configuring a replication target

Page 96 highlights

of reverse replication is the same as if initializing the device at the remote site and so depends on the link speed and amount of critical data to be reverse replicated. Once the server is recovered and able to perform backups again, configure replication back to the target device in the data center all over again. This option is easy to implement even in many-to-one replication scenarios. Reverse replication is a means whereby the source and target libraries maintain their identity, but where at the point of rebuilding the source using a special "recover first" mode to force the source to go to the target and reverse replicate data from the target back to the source. The basic process takes place entirely from the remote site where the new D2D appliance has been installed: 1. With a new replacement D2D at the remote site set the appropriate network settings. 2. Create an identical virtual library (or libraries if more than one was originally configured). 3. At the source select the Replication tab from the GUI. Then select Mapping Configuration. Begin as if configuring a replication target, but start the recovery wizard instead of the replication wizard. 4. Now create a new target appliance. Select Add Target Appliance. The IP address of the target appliance (which still exists) is entered and when found the target appliance is shown. Then select Next. If there are multiple target libraries within the target appliance select the relevant one that was configured prior to the disaster at remote site C. 96 D2D Systems

  • 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
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218

of reverse replication is the same as if initializing the device at the remote site and so depends on
the link speed and amount of critical data to be reverse replicated. Once the server is recovered and
able to perform backups again, configure replication back to the target device in the data center all
over again. This option is easy to implement even in many-to-one replication scenarios.
Reverse replication is a means whereby the source and target libraries maintain their identity, but
where at the point of rebuilding the source using a special
recover first
mode to force the source to
go to the target and reverse replicate data from the target back to the source. The basic process takes
place entirely from the remote site where the new D2D appliance has been installed:
1.
With a new replacement D2D at the remote site set the appropriate network settings.
2.
Create an identical virtual library (or libraries if more than one was originally configured).
3.
At the source select the Replication tab from the GUI. Then select
Mapping Configuration
. Begin
as if configuring a replication target, but start the recovery wizard instead of the replication
wizard.
4.
Now create a new target appliance. Select
Add Target Appliance
. The IP address of the target
appliance (which still exists) is entered and when found the target appliance is shown. Then select
Next
. If there are multiple target libraries within the target appliance select the relevant one that
was configured prior to the disaster at remote site C.
D2D Systems
96