HP 3PAR StoreServ 7400 2-node HP 3PAR Command Line Interface Administrator& - Page 172

and a new read/write snapshot

Page 172 highlights

NOTE: In this example, test.rw1 can have VLUNs associated with it. The command will remember the VLUN, remove the old snapshot, create a new snapshot, and recreate the VLUN with the new snapshot. After the snapshot is replaced, testuser1 must remount the filesystem on the host. In the above example, the replaced copy (test.rw1) is a new copy of the database made from the reference copy (test.ro1), and not from the database itself (test). To get an up-to-date read-write copy of the original database, testuser1 must have updatevv rights for volumes test.rw1 and test.ro1. Unmount the filesystem on the host before issuing the following HP 3PAR CLI command: cli% updatevv -ro test.rw1 This command removes test.rw1 and test.ro1, and replaces them with a new read-only snapshot of test called test.ro1 and a new read/write snapshot of test.ro1 called test.rw1. This gives the user an up-to-date read-write copy of the original database by creating a new read-only snapshot of the original in addition to the new read-write copy. NOTE: In this example, only the read-write snapshot (test.rw1) can have a VLUN associated with it. The command will remember the VLUN, remove the old snapshot, create a new snapshot, and recreate the VLUN with the new snapshot. However, the read-only parent cannot have any VLUNs. If the read-only parent (test.ro1) has any associated VLUNs, this command will fail. After the snapshot is replaced, testuser1 must remount the filesystem on the host. 172 Using mySnapshot

  • 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

NOTE:
In this example,
test.rw1
can have VLUNs associated with it. The command will remember the
VLUN, remove the old snapshot, create a new snapshot, and recreate the VLUN with the new
snapshot.
After the snapshot is replaced,
testuser1
must remount the filesystem on the host.
In the above example, the replaced copy (
test.rw1
) is a new copy of the database made from
the reference copy (
test.ro1
), and not from the database itself (
test
).
To get an up-to-date read-write copy of the original database,
testuser1
must have
updatevv
rights for volumes
test.rw1
and
test.ro1
. Unmount the filesystem on the host before issuing
the following HP 3PAR CLI command:
cli% updatevv -ro test.rw1
This command removes
test.rw1
and
test.ro1
, and replaces them with a new read-only
snapshot of
test
called
test.ro1
and a new read/write snapshot of
test.ro1
called
test.rw1
. This gives the user an up-to-date read-write copy of the original database by creating
a new read-only snapshot of the original in addition to the new read-write copy.
NOTE:
In this example, only the read-write snapshot (
test.rw1
) can have a VLUN associated with it.
The command will remember the VLUN, remove the old snapshot, create a new snapshot, and
recreate the VLUN with the new snapshot. However, the read-only parent cannot have any VLUNs.
If the read-only parent (
test.ro1
) has any associated VLUNs, this command will fail.
After the snapshot is replaced,
testuser1
must remount the filesystem on the host.
172
Using mySnapshot