HP MSA 1040 HP MSA 1040 SMU Reference Guide (762784-001, March 2014) - Page 126

Remote replication licensing, Related topics, Using the Replication Setup Wizard

Page 126 highlights

3. Map the new primary volume to hosts, as was the original primary volume. Figure 6 Example of primary-volume failure If the original primary volume becomes accessible, you can set it to be the primary volume again as described in the following process overview: 1. Take a snapshot of the original primary volume. This preserves the volume's current data state for later comparison with the new primary volume. 2. Remove the volume's mappings. 3. Set the original primary volume to be a secondary volume. 4. Replicate any data written to the new primary volume to the original primary volume (now a secondary volume). This can be done as one or more replications. On the final replication, halt host access to the primary volume to ensure that all data has been transferred to the secondary volume. 5. Set the secondary volume (the original primary volume) to be the new primary volume. 6. You can now mount/present/map the snapshot taken in step 1 and compare it with the new primary volume to identify any data discrepancies and try to recover any data from the snapshot that would otherwise be lost. For example, you could use host file-system tools to find any files modified since a certain time, or for a database you could export any differing records from the snapshot and re-enter them into the current database. For details, see the procedure to change the primary volume back to the original primary volume in "Changing the primary volume for a replication set" (page 135). Remote replication licensing The Remote Snap feature and the maximum number of snapshots that can be created are separately licensed. By default, 64 snapshots can be created. Normally, replication snapshots are not accessible to hosts. However, a replication snapshot can be exported for use as a standard snapshot and will count toward the snapshot license limit. Related topics • "Installing a license" (page 39) • Adding (page 53) or deleting (page 54) a remote system • "Checking links to a remote system" (page 90) • "Using the Replication Setup Wizard" (page 127) • Replicating a volume (page 129) or a snapshot (page 131) • Detaching (page 132) and reattaching (page 134) a secondary volume • Stopping (page 133) and restarting (page 134) a vdisk 126 Using Remote Snap to replicate volumes

  • 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

126
Using Remote Snap to replicate volumes
3.
Map the new primary volume to hosts, as was the original primary volume.
Figure 6
Example of primary-volume failure
If the original primary volume becomes accessible, you can set it to be the primary volume again as described in the
following process overview:
1.
Take a snapshot of the original primary volume. This preserves the volume’s current data state for later
comparison with the new primary volume.
2.
Remove the volume’s mappings.
3.
Set the original primary volume to be a secondary volume.
4.
Replicate any data written to the new primary volume to the original primary volume (now a secondary volume).
This can be done as one or more replications. On the final replication, halt host access to the primary volume to
ensure that all data has been transferred to the secondary volume.
5.
Set the secondary volume (the original primary volume) to be the new primary volume.
6.
You can now mount/present/map the snapshot taken in
step 1
and compare it with the new primary volume to
identify any data discrepancies and try to recover any data from the snapshot that would otherwise be lost. For
example, you could use host file-system tools to find any files modified since a certain time, or for a database you
could export any differing records from the snapshot and re-enter them into the current database.
For details, see the procedure to change the primary volume back to the original primary volume in
"Changing the
primary volume for a replication set" (page 135)
.
Remote replication licensing
The Remote Snap feature and the maximum number of snapshots that can be created are separately licensed. By
default, 64 snapshots can be created. Normally, replication snapshots are not accessible to hosts. However, a
replication snapshot can be exported for use as a standard snapshot and will count toward the snapshot license limit.
Related topics
"Installing a license" (page 39)
Adding (
page 53
) or deleting (
page 54
) a remote system
"Checking links to a remote system" (page 90)
"Using the Replication Setup Wizard" (page 127)
Replicating a volume (
page 129
) or a snapshot (
page 131
)
Detaching (
page 132
) and reattaching (
page 134
) a secondary volume
Stopping (
page 133
) and restarting (
page 134
) a vdisk