Release notes
Migrate an SVM
Suggest changes
-
PDF of this doc site
-
Cluster administration
-
Volume administration
-
Logical storage management with the CLI
-
-
NAS storage management
-
Configure NFS with the CLI
-
Manage NFS with the CLI
-
Manage SMB with the CLI
-
Manage file access using SMB
-
-
-
Security and data encryption
-
Data protection and disaster recovery
-
Collection of separate PDF docs
Creating your file...
After an SVM migration has completed, clients are cut over to the destination cluster automatically and the unnecessary SVM is removed from the source cluster. Automatic cutover and automatic source cleanup are enabled by default. If necessary, you can disable client auto-cutover to suspend the migration before cutover occurs and you can also disable automatic source SVM cleanup.
-
You can use the
-auto-cutover falseoption to suspend the migration when automatic client cutover normally occurs and then manually perform the cutover later. -
You can use the advance privilege
-auto-source-cleanup falseoption to disable the removal of the source SVM after cutover and then trigger source cleanup manually later, after cutover.
Migrate an SVM with automatic cutover enabled
By default, clients are cut over to the destination cluster automatically when the migration is complete, and the unnecessary SVM is removed from the source cluster.
-
From the destination cluster, run the migration prechecks:
dest_cluster> vserver migrate start -vserver SVM_name -source-cluster cluster_name -check-only true -
From the destination cluster, start the SVM migration:
dest_cluster> vserver migrate start -vserver SVM_name -source-cluster cluster_name -
Check the migration status:
dest_cluster> vserver migrate showThe status displays migrate-complete when the SVM migration is finished.
Migrate an SVM with automatic client cutover disabled
You can use the -auto-cutover false option to suspend the migration when automatic client cutover normally occurs and then manually perform the cutover later. See Manually cutover clients after SVM migration.
-
From the destination cluster, run the migration prechecks:
dest_cluster> vserver migrate start -vserver SVM_name -source-cluster cluster_name -check-only true -
From the destination cluster, start the SVM migration:
dest_cluster> vserver migrate start -vserver SVM_name -source-cluster cluster_name -auto-cutover false -
Check the migration status:
dest_cluster> vserver migrate showThe status displays ready-for-cutover when SVM migration completes the asynchronous data transfers, and it is ready for cutover operation.
Migrate an SVM with source cleanup disabled
You can use the advance privilege -auto-source-cleanup false option to disable the removal of the source SVM after cutover and then trigger source cleanup manually later, after cutover. See Manually remove source SVM.
-
From the destination cluster, run the migration prechecks:
dest_cluster*> vserver migrate start -vserver SVM_name -source-cluster cluster_name -check-only true -
From the destination cluster, start the SVM migration:
dest_cluster*> vserver migrate start -vserver SVM_name -source-cluster cluster_name -auto-source-cleanup false -
Check the migration status:
dest_cluster*> vserver migrate showThe status displays ready-for-source-cleanup when SVM migration cutover is complete, and it is ready to remove the SVM on the source cluster.