Skip to main content

Cutover clients and clean up source storage VM after migration to an ASA r2 system

Contributors netapp-aherbin
PDFs

After a storage virtual machine (VM) is migrated from an ASA cluster to an ASA r2 cluster, by default, clients are automatically cut over to the ASA r2 cluster and the storage VM on the ASA cluster is automatically removed. If you chose to disable automatic cutover and removal of the ASA storage VM during the migration, you need to perform these steps manually after the migration is complete.

Manually cut over clients to an ASA r2 system after a storage VM migration

If you disable automatic client cutover during the migration of a storage VM from an ASA cluster to an ASA r2 cluster, after the migration is successfully complete, perform the cutover manually so the ASA r2 storage VM can serve data to clients.

Steps

  1. On the ASA r2 cluster, manually execute client cutover:

    vserver migrate cutover -vserver <storage_VM_name>

  2. Verify that the cutover operation is complete:

    vserver migrate show
Result

Data is being served to your clients from the storage VM on your ASA r2 cluster.

What’s next?

You are now ready to remove the storage VM from the source ASA cluster.

Manually remove an ASA storage VM after migration to an ASA r2 cluster

If you disable automatic source cleanup during the migration of a storage VM from an ASA cluster to an ASA r2 cluster, after the migration is complete, remove the storage VM from the ASA cluster to free the storage space.

Before you begin

Your clients should be serving data from the ASA r2 cluster.

Steps

  1. From the ASA cluster, verify that the status of the ASA storage VM is Ready for source cleanup:

    vserver migrate show

  2. Remove the ASA storage VM:

    vserver migrate source-cleanup -vserver <storage_VM_name>
Result

The storage VM on your ASA cluster is removed.