- Page 1: Front coverIBM XIV Storage System:C
- Page 7 and 8: 5.4.1 Last consistent snapshot . .
- Page 9 and 10: 8.9.3 Set up the IO group for mirro
- Page 11 and 12: NoticesThis information was develop
- Page 13 and 14: PrefaceThis IBM® Redbooks® public
- Page 15 and 16: Ron Verbeek is a Senior Consulting
- Page 17 and 18: 1Chapter 1.SnapshotsThe XIV Storage
- Page 19 and 20: When a logical volume or LUN is cre
- Page 21 and 22: It is important to note that data o
- Page 23 and 24: For the further discussion we must
- Page 25 and 26: The new snapshot is displayed in Fi
- Page 27 and 28: 1.2.2 Viewing snapshot detailsAfter
- Page 29 and 30: After clicking Change Deletion Prio
- Page 31 and 32: Figure 1-19 illustrates selecting t
- Page 33 and 34: There are two scenarios that you mu
- Page 35 and 36: The locking process completes immed
- Page 37 and 38: 1.2.9 Automatic deletion of a snaps
- Page 39 and 40: To determine the cause of removal,
- Page 41 and 42: In order to obtain details about th
- Page 43 and 44: After selecting the volumes to add,
- Page 45 and 46: In addition to the snapshot functio
- Page 47 and 48: From the Snapshots Group Tree view,
- Page 49 and 50: 1.4 Snapshot with Remote MirrorXIV
- Page 51 and 52: The backup script is simple, and de
- Page 53 and 54: To show that the restore operation
- Page 55 and 56:
You can start the MySQL daemon with
- Page 57 and 58:
2Chapter 2.Tivoli Storage FlashCopy
- Page 59 and 60:
Tivoli Storage FlashCopy Manager (F
- Page 61 and 62:
2.3.1 VSS architecture and componen
- Page 63 and 64:
►Redirect-on-write (differential
- Page 65 and 66:
In the next step you can specify th
- Page 67 and 68:
3. When the validation is successfu
- Page 69 and 70:
The configuration process for Micro
- Page 71 and 72:
4. In this configuration step, the
- Page 73 and 74:
Tip: Any previously taken snapshots
- Page 75 and 76:
DATEformat ........................
- Page 77 and 78:
Writer Status: OnlineSelectable Com
- Page 79 and 80:
FlashCopy Manager for Microsoft Exc
- Page 81 and 82:
3Chapter 3.Volume copyThe XIV Stora
- Page 83 and 84:
Figure 3-1 illustrates making a cop
- Page 85 and 86:
To perform the volume copy:1. Valid
- Page 87 and 88:
4Chapter 4.Remote MirroringThe Remo
- Page 89 and 90:
►►Asynchronous schedule interva
- Page 91 and 92:
4.2 Mirroring schemesMirroring, whe
- Page 93 and 94:
The various mirroring role status o
- Page 95 and 96:
4.2.3 Mirroring statusThe status of
- Page 97 and 98:
The following states or statuses ar
- Page 99 and 100:
►Metro region XIV Remote Mirrorin
- Page 101 and 102:
Like any continuous or near-continu
- Page 103 and 104:
XIV Remote Mirroring copies data fr
- Page 105 and 106:
►XIV target configuration: synchr
- Page 107 and 108:
4.4.3 Connecting XIV mirroring port
- Page 109 and 110:
In Figure 4-26, seven logical volum
- Page 111 and 112:
Dependent writes: normal operationA
- Page 113 and 114:
When a mirror coupling relationship
- Page 115 and 116:
During normal operation, a single X
- Page 117 and 118:
4.4.10 Changing role of master volu
- Page 119 and 120:
4.4.12 Reactivation, resynchronizat
- Page 121 and 122:
To remove a volume mirror from a mi
- Page 123 and 124:
4.5 Best practice usage scenariosTh
- Page 125 and 126:
4.5.3 Using an extra copy for DRThi
- Page 127 and 128:
4.5.7 Communication failureThis sce
- Page 129 and 130:
►►►Snapshots: Snapshots are a
- Page 131 and 132:
Alternatively, a single port can be
- Page 133 and 134:
In the event that a port role does
- Page 135 and 136:
Then define the type of mirroring t
- Page 137 and 138:
Right-click a path and you have opt
- Page 139 and 140:
4.12 Configuring Remote MirroringCo
- Page 141 and 142:
5Chapter 5.Synchronous Remote Mirro
- Page 143 and 144:
The Create Mirror dialogue box is d
- Page 145 and 146:
2. On the primary XIV, to list the
- Page 147 and 148:
To create a mirrored consistency gr
- Page 149 and 150:
The mirror has the following charac
- Page 151 and 152:
Changing the slave peer roleThe rol
- Page 153 and 154:
5.4.2 Last consistent snapshot time
- Page 155 and 156:
5.5.2 Phase 2: disaster at local si
- Page 157 and 158:
Map volumes on standby server and c
- Page 159 and 160:
2. You will be prompted to confirm
- Page 161 and 162:
Reactivating the remote mirror coup
- Page 163 and 164:
Figure 5-28 Switch role to slave vo
- Page 165 and 166:
6Chapter 6.Asynchronous Remote Mirr
- Page 167 and 168:
Using the GUI for volume mirror set
- Page 169 and 170:
When volumes are to be placed in a
- Page 171 and 172:
Activating the remote mirror coupli
- Page 173 and 174:
Adding a mirrored volume to a mirro
- Page 175 and 176:
Figure 6-15 Slave CG statusThe Cons
- Page 177 and 178:
6.1.3 Coupling activation, deactiva
- Page 179 and 180:
Figure 6-19 Change CG intervalUsing
- Page 181 and 182:
Using XCLI commands for deactivatio
- Page 183 and 184:
After this changeover, the followin
- Page 185 and 186:
Using XCLI commands to change roles
- Page 187 and 188:
3. The most_recent data is copied t
- Page 189 and 190:
This mechanism bears the following
- Page 191 and 192:
3. A new last_replicated snapshot i
- Page 193 and 194:
Mirrored volumes have been placed i
- Page 195 and 196:
6.7.3 DR testing scenarioIt is impo
- Page 197 and 198:
Figure 6-45 Slave role restoredAny
- Page 199 and 200:
The XIV system has a sophisticated
- Page 201 and 202:
7Chapter 7.Data migrationThis chapt
- Page 203 and 204:
eceiving read requests from a host,
- Page 205 and 206:
►this technology during data migr
- Page 207 and 208:
Zone or cable the XIV to the non-XI
- Page 209 and 210:
Define non-XIV storage device to XI
- Page 211 and 212:
In Figure 7-7 the connection from m
- Page 213 and 214:
4. Zone the host to XIV. The host m
- Page 215 and 216:
management panels. In Figure 7-8 on
- Page 217 and 218:
3. Bring the host server online.Onc
- Page 219 and 220:
All of the commands given on the ne
- Page 221 and 222:
►►►►If the data migration i
- Page 223 and 224:
xcli -m 10.10.0.10 dm_activate vol=
- Page 225 and 226:
7.6.1 Changing the synchronization
- Page 227 and 228:
ack end copy). They do, however, sh
- Page 229 and 230:
Writing zeros to recover spaceOne w
- Page 231 and 232:
To resize a volume go to the Volume
- Page 233 and 234:
7.9.2 Remote volume LUN is unavaila
- Page 235 and 236:
7.9.6 LUN is out of rangeXIV curren
- Page 237 and 238:
Table 7-1 Physical site setupTable
- Page 239 and 240:
TasknumberCompleted?Where toperform
- Page 241 and 242:
LUN0There is a requirement for the
- Page 243 and 244:
4. Click Present.5. Select the XIV
- Page 245 and 246:
You can now create a host definitio
- Page 247 and 248:
Multipathing with DS8000The DS8000
- Page 249 and 250:
These volumes are currently allocat
- Page 251 and 252:
Finally, we can define the AIX host
- Page 253 and 254:
Now that the migration has been sta
- Page 255 and 256:
Once the sync is complete it is tim
- Page 257 and 258:
We change the number of 512 byte un
- Page 259 and 260:
8Chapter 8.SVC migration with XIVTh
- Page 261 and 262:
The XIV firmware version can also b
- Page 263 and 264:
8.3.2 Determining XIV WWPNsXIV WWPN
- Page 265 and 266:
8.4.1 SCSI queue depth consideratio
- Page 267 and 268:
It also must be clearly understood
- Page 269 and 270:
the data from each extent best util
- Page 271 and 272:
In Example 8-10 the MDisk group has
- Page 273 and 274:
8. Map the volumes to the SVC clust
- Page 275 and 276:
Example 8-24 Rename the MDisks6. Re
- Page 277 and 278:
3. We migrate each VDisk to image m
- Page 279 and 280:
When the lsmigrate command returns
- Page 281 and 282:
emote_copy_free_memory 20.0MBmirror
- Page 283 and 284:
8.9.6 Removing the VDisk copyNow th
- Page 285 and 286:
The XIV GUI volume creation panel i
- Page 287 and 288:
We now use the unmanaged MDisk to c
- Page 289 and 290:
8.11 Future configuration tasksThe
- Page 291 and 292:
product_revision 10.0ctrl_s/nallow_
- Page 293 and 294:
Related publicationsThe publication
- Page 295 and 296:
IndexSymbols_Define_Target_(Legacy
- Page 297 and 298:
actual data 98additional Snapshot 1
- Page 299 and 300:
Storage Pool 6, 10, 21additional al
- Page 301 and 302:
IBM XIV Storage System: CopyService
- Page 304:
Back cover®IBM XIV Storage System: