HP 3PAR StoreServ 7400 2-node HP 3PAR Command Line Interface Reference (OS 3.1 - Page 661

NOTES • The updatevv command attempts to use the same VV IDs for new snapshots as the snapshots that they replace so that the new VV have the same World Wide Names (WWNs) as the originals (this might be important for hosts using the VV WWN to identify the VV). However, between the removal of the original snapshot and the creation of the new snapshot it is possible that another VV might have been created with the same ID causing the creation of the new snapshot to fail. If the -anyid option is specified, the command then creates the snapshot with any available ID. Because new VVs, by default, are assigned the lowest ID available, VVs that are updated with the updatevv command should be assigned large IDs (using the -i option to the createaldvv command) to reduce the likelihood that their IDs are taken during the updatevv command operation. • After the updatevv command is executed, all VLUNs associated with the specified VV name are removed. The command then updates the snapshots as follows: ◦ If the -ro option is not specified, or if the specified VV name is a read-only snapshot, the command removes the snapshot, and creates a new snapshot of the same name and of the same parent. ◦ If the -ro option is specified and the specified VV name is a read/write snapshot, the VV is removed and its read-only parent is replaced by a new read-only snapshot of the same name. Then a new read/write snapshot is created of the new read-only snapshot. If the read-only parent has multiple read/write snapshots, the updatevv operation will fail because the read-only parent volume cannot be removed. The command then re-creates all the VLUNs associated with the specified VV name. • Running concurrent updatevv sessions for VV sets or list of VVs which have common VVs can have unpredictable results. updatevv 661