HP 3PAR InForm OS 3.1.1 CLI Administrator's Manual
• testuser1 is a user with updatevv rights for volume test.rw1 See “Setting Administrative
Rights” (page 141) for instructions on setting rights for replacing a read-write snapshots.
• When test.rw1 needs to be restored, testuser1 unmounts the filesystem on the host and
then issues the following InForm OS CLI command to replace test copy test.rw1 with a new
copy:
cli% updatevv test.rw1
This command removes test.rw1 and replaces it with a new snapshot of test.ro1. This new
volume is also called test.rw1.
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 recreate the VLUN with
the new snapshot.
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).
• 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 and then unmount the filesystem
on the host before issuing the following InForm OS 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 snapshot, create the
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.
Replacing Virtual Volume Snapshots 143