3PAR InForm® OS 2.2.4 CLI Administrator's Manual (320-200113 Rev A, March 2009)

16.5
Replacing Virtual Volume Snapshots
InForm OS Version 2.2.4 3PAR InForm OS CLI Administrator’s Manual
After the snapshot is replaced, testuser1 must remount the filesystem on the host.
Note that, 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 the database itself (test).
X To get an up-to-date read-write copy of the original database, testuser1 must have
updatevv privileges for volumes test.rw1 and test.ro1 and then unmount the
filesystem on the host before issuing the following InForm CLI command:
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.
After the snapshot is replaced,
testuser1 must remount the filesystem on the host.
NOTE: In this example, test.rw1 can have VLUNs associated with it. The
command will remember the VLUN, remove the snapshot, create the new
snapshot, and re-create the VLUN with the new snapshot.
cli% updatevv -ro test.rw1
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
snapshot, create the new snapshot, and re-create 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.