Dell PowerVault MD3260i CLI Guide - Page 54

Re-creating The Snapshot Virtual Disk, Preparing Host Servers To Re-create A Snapshot Virtual Disk

Get Dell PowerVault MD3260i PDF manuals and user guides View all Dell PowerVault MD3260i manuals
Add to My Manuals
Save this manual to your list of manuals

Page 54 highlights

Re-creating The Snapshot Virtual Disk To restart a copy-on-write operation, use the recreate snapshot virtualDisk command. This command starts a fresh copy-on-write operation using an existing snapshot virtual disk. When you restart a snapshot virtual disk, the snapshot virtual disk must have either an Optimal or a Disabled state. The following conditions then occur: • All copy-on-write data previously on the snapshot repository virtual disk is deleted. • Snapshot virtual disk and snapshot repository virtual disk parameters remain the same as the previously disabled snapshot virtual disk and snapshot repository virtual disk. You can also change the userLabel, warningThresholdPercent, and repositoryFullPolicy parameters when you restart the snapshot virtual disk. • The original names for the snapshot repository virtual disk are retained. Preparing Host Servers To Re-create A Snapshot Virtual Disk CAUTION: Before you create a new point-in-time image of a source virtual disk, stop any data access (I/O) activity or suspend data transfer to the source virtual disk and snapshot virtual disk to ensure that you capture an accurate point-in-time image of the source virtual disk. Close all applications, including Windows Internet Explorer, to make sure all I/O activity has stopped. NOTE: Removing the drive letter of the associated virtual disk in Windows or unmounting the virtual drive in Linux helps to guarantee a stable copy of the drive for the Snapshot. Before re-creating a snapshot virtual disk, both the server and the associated virtual disk you are re‑creating have to be in the proper state. To ensure that the host server is properly prepared to re-create a snapshot virtual disk, you can either use an application to carry out this task, or you can perform the following steps: 1. Stop all I/O activity to the source and snapshot virtual disk (if mounted). 2. Using your Windows system, flush the cache to both the source and the snapshot virtual disk (if mounted). At the host prompt, type SMrepassist ‑f and press . See "SMrepassist Utility" in the Owner's Manual for more information. 3. Remove the drive letter(s) of the source and (if mounted) snapshot virtual disk in Windows or unmount the virtual drive(s) in Linux to help guarantee a stable copy of the drive for the Snapshot. If this is not done, the snapshot operation reports that it has completed successfully, but the snapshot data is not updated properly. 4. Follow any additional instructions for your operating system. Failure to follow these additional instructions can create unusable snapshot virtual disks. NOTE: If your operating system requires additional instructions, you can find those instructions in your operating system documentation. After your server has been prepared, see Re-creating The Snapshot Virtual Disk to re-create the snapshot virtual disk. Re-creating A Snapshot Virtual Disk After first preparing the host server(s) as specified in the preceding procedure, use the following examples to re-create a virtual disk snapshot. Refer to steps 1 through 4 in the preceding section, Preparing Host Servers To Re-create A Snapshot Virtual Disk. The following example shows the command to restart a snapshot virtual disk: client>smcli 123.45.67.89 -c "recreate snapshot virtualDisks [\"Mars_Spirit_4-2\" \"Mars_Spirit_4-3\"];" 54

  • 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
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
Re-creating The Snapshot Virtual Disk
To restart a copy-on-write operation, use the
recreate snapshot virtualDisk
command. This command
starts a fresh copy-on-write operation using an existing snapshot virtual disk. When you restart a snapshot virtual disk,
the snapshot virtual disk must have either an Optimal or a Disabled state. The following conditions then occur:
•
All copy-on-write data previously on the snapshot repository virtual disk is deleted.
•
Snapshot virtual disk and snapshot repository virtual disk parameters remain the same as the previously
disabled snapshot virtual disk and snapshot repository virtual disk. You can also change the
userLabel
,
warningThresholdPercent
, and
repositoryFullPolicy
parameters when you restart the
snapshot virtual disk.
•
The original names for the snapshot repository virtual disk are retained.
Preparing Host Servers To Re-create A Snapshot Virtual Disk
CAUTION: Before you create a new point-in-time image of a source virtual disk, stop any data access (I/O) activity
or suspend data transfer to the source virtual disk and snapshot virtual disk to ensure that you capture an accurate
point-in-time image of the source virtual disk. Close all applications, including Windows Internet Explorer, to make
sure all I/O activity has stopped.
NOTE:
Removing the drive letter of the associated virtual disk in Windows or unmounting the virtual drive in Linux
helps to guarantee a stable copy of the drive for the Snapshot.
Before re-creating a snapshot virtual disk, both the server and the associated virtual disk you are re
‑
creating have to be
in the proper state. To ensure that the host server is properly prepared to re-create a snapshot virtual disk, you can
either use an application to carry out this task, or you can perform the following steps:
1.
Stop all I/O activity to the source and snapshot virtual disk (if mounted).
2.
Using your Windows system, flush the cache to both the source and the snapshot virtual disk (if mounted). At the
host prompt, type
SMrepassist
‑
f <filename-identifier>
and press <Enter>. See "SMrepassist
Utility" in the
Owner’s Manual
for more information.
3.
Remove the drive letter(s) of the source and (if mounted) snapshot virtual disk in Windows or unmount the virtual
drive(s) in Linux to help guarantee a stable copy of the drive for the Snapshot. If this is not done, the snapshot
operation reports that it has completed successfully, but the snapshot data is not updated properly.
4.
Follow any additional instructions for your operating system. Failure to follow these additional instructions can
create unusable snapshot virtual disks.
NOTE:
If your operating system requires additional instructions, you can find those instructions in your
operating system documentation.
After your server has been prepared, see Re-creating The Snapshot Virtual Disk to re-create the snapshot virtual disk.
Re-creating A Snapshot Virtual Disk
After first preparing the host server(s) as specified in the preceding procedure, use the following examples to re-create
a virtual disk snapshot.
Refer to steps 1 through 4 in the preceding section, Preparing Host Servers To Re-create A Snapshot Virtual Disk. The
following example shows the command to restart a snapshot virtual disk:
client>smcli 123.45.67.89 -c "recreate snapshot
virtualDisks [\"Mars_Spirit_4-2\" \"Mars_Spirit_4-3\"];"
54