EMC ViPR REST API

Search (SHIFT+S)

API Reference


Changes to Change Volumes Virtual Pool

Allows the caller to change the virtual pool for the volumes identified in the request. Currently, the only virtual pool changes that are supported via this method are as follows: Change the virtual pool for a VPLEX virtual volume. This virtual pool change would allow the caller to change the types of drives, for example, used for the backend volume(s) that are used by the virtual volume. Change the virtual pool for a VPLEX virtual volume, such that a local VPLEX virtual volumes becomes a distributed VPLEX virtual volume. Change the virtual pool of a VMAX or VNX Block volume to make the volume a local or distributed VPLEX virtual volume. Essentially, the volume becomes the backend volume for a VPLEX virtual volume. Similar to creating a virtual volume, but instead of creating a new backend volume, using the volume identified in the request. The VMAX or VNX volume cannot currently be exported for this change. Change the virtual pool of a VMAX or VNX Block volume to make the volume a RecoverPoint protected volume. The volume must be able to stay put, and ViPR will build a protection around it. Change the virtual pool of a VMAX or VNX Block volume to allow native continuous copies to be created for it. Change the virtual pool of a volume to increase the export path parameter max_paths. The number of paths will be upgraded if possible for all Export Groups / Export Masks containing this volume. If the volume is not currently exported, max_paths can be decreased or paths_per_initiator can be changed. Note that changing max_paths does not have any effect on the export of BlockSnapshots that were created from this volume. Change the virtual pool of a VMAX and VNX volumes to allow change of Auto-tiering policy associated with it. Note: Operations other than Auto-tiering Policy change will call the internal single volume method (BlockServiceApiImpl) in a loop.


Request Payload Changes

Field Description Type Notes
<volumes_vpool_change>
<volumes>
<volume> URI 0-* Elements
</volumes>
<vpool> ID of the new virtual pool. URI
<protection>    
<continuous_copies>    
<max_native_continuous_copies> The maximum number of continuous copies for a virtual pool. Integer
<protection_mirror_vpool> The virtual pool for protection mirrors. URI
<haMaxMirrors> Integer
<ha_protection_mirror_vpool> The virtual pool for protection mirrors on the High Availability side. URI
</continuous_copies>      
<recoverpoint>    
<copies>
<protection_varray_vpool>     0-* Elements
<varray> The virtual array. URI
<vpool> The virtual pool. URI
<policy>    
<journal_size> The journal size for a protection copy. String
<journal_varray> The journal virtual array for a protection copy. URI
<journal_vpool> The journal virtual pool for a protection copy. URI
</policy>      
</protection_varray_vpool>      
</copies>
<source_policy>    
<journal_size> The journal size for a protection source. String
<journal_varray> The journal virtual array for a protection source/active source. URI
<journal_vpool> The journal virtual pool for a protection source/active source. URI
<standby_journal_varray> The journal virtual array for stand-by source. URI
<standby_journal_vpool> The journal virtual pool for stand-by source. URI
<remote_copy_mode> The remote copy mode, sync or async Valid value: ASYNCHRONOUS = RecoverPoint CG will be in Asynchronous mode (default) SYNCHRONOUS = RecoverPoint CG will be in Synchronous mode String
<rpo_value> RPO value sent to RP Long
<rpo_type> Type of RPO unit Valid values: SECONDS MINUTES HOURS WRITES BYTES KB MB GB TB String
</source_policy>      
</recoverpoint>      
<remote_copies>    
<remote_copy_settings>
<remote_copy_setting>     0-* Elements
<varray> URI
<vpool> URI
<remote_copy_mode> String
</remote_copy_setting>      
</remote_copy_settings>
</remote_copies>      
<snapshots>    
<max_native_snapshots> The maximum snapshots. Integer
</snapshots>      
</protection>      
<transfer_speed> Parameter for Transfer Speed. Optional parameter for virtual volume migration from VPLEX Local to Distributed. String
<consistency_group> The ViPR consistency group to associate the volume with for the creation of the RecoverPoint consistency group. URI
<forceFlag> Boolean
</volumes_vpool_change>