Auto LUN Migration in HP XP24000

Auto LUN migration helps to play around with the V-Vols in XP. Auto LUN migration is transparent to the end user and sys admins. The CU:LDEV remains same as it was before the migration.

Create the V-Vol in the desired pool. While creating the V-Vol it should be kept in mind that the block size must be exactly same as the source V-Vol. Check the same by navigating through

GO->Customized Volume. Select the size in blocks.

Once its done then make the new LUN as reserve LUN. Navigate through to make it as a reserved LUN.

AutoLUN -->AutoLUN -->Physical -->Plan -->Attribute --> V-Vol group (V-Vol). Just right click on the LUN and make it as a reserve LUN.

Now we are ready for the migration.

Manual Migration --> Source V-Vol -->Target -->Destination V-Vol -->Set

Once its applied it will show the migration status. (It took around 45 minutes for migrating a 250GB LUN from internal to external pool)

The migration status can also be checked from the History tab.

Once the migration is done it should be kept in mind that the CU:LDEV will not change in host. The xBox will change i.e the source CU:LDEV will be now shown in the new destination xBox that was created for the migration. The same can be also seen from the Migration History tab.

Now we need to delete the source LUN (inside the old xBox). But before that we need to make it as a normal LUN. Navigate through

AutoLUN -->AutoLUN -->Physical -->Plan -->Attribute --> V-Vol group (V-Vol). Just right and make it as a normal LUN.

Then go to Release V-Vol from a pool and select the appropriate Cache partition & pool of the source LUN and just select and do SET.

And finally delete the V-Vol group. Apply it once done.

Now finally before we leave the XP we need to run Discard Zero Data on the LUN (on which we did Auto LUN migration) to reclaim the unused space.