ViPR & VSP Protected by SRDF

All fields in the virtual storage pool are available for update, as long as no volumes have been provisioned from that virtual storage pool at the time of the update.

In general, if the virtual storage pool already has volumes assigned to it, the fields that can be updated are limited to only those fields that will not:

• degrade or change the quality of service to existing volumes in the virtual storage pool.
• misalign or force a migration of existing volumes in the virtual storage pool.

For instance, ViPR does not allow changing the RAID levels for the virtual storage pool after a volume is created because it may require moving an existing volume from one RAID type to another, which may result in a disruptive migration.

Fields such as name and description can be changed at any time.  Fields such as SRDF, RP, VPLEX may not be changed after volumes have been provisioned.  Other such fields may not be changed:

• Number of paths (minimum, max, paths per initiator)
• Raid Level
• Drive Type
• Thin Volume Preallocation Percentage

These are the fields we are actively checking at the time of update.  There may be additional restrictions based on the current volumes in the virtual pool and the updates submitted.  ViPR reserves the right to add additional restrictions if the virtual storage pool attribute's change compromises the integrity or standing of the existing volumes in the virtual storage pool.