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
