NetApp AltaVault Cloud Integrated Storage Administration Guide 167
Canceling cloud-to-cloud migration Migrating data to a new cloud
CLI (config)# replication migrate-to proxy hostname <hostname> [port <port number>] [username
<username>] [password <password>]
CLI (config)# replication migrate-to proxy enable
4. Start cloud migration specifying the number of processes (threads) AltaVault uses to complete the transfer. The
default is 128 threads:
CLI (config)# replication migrate-to enable [num-threads <value-1-to-128>]
5. Monitor cloud migration status. Enter the following command to show the estimated time until migration
completes:
CLI (config)# show replication migrate-to estimate
Upon completion, AltaVault displays a message indicating the migration was successful along with the number of
bytes transferred.
6. If migration fails for any reason, you can try continuing the migration from where it left off, or deleting the data
in the new cloud and start over.
To restart migration from where it left off, enter the following command:
CLI (config)# replication migrate-to skip-existing
Replication will be paused and service will be restarted
Continue? [y/n]
To delete the data in the new cloud and start the migration over again, enter the following command:
CLI (config)# replication migrate-to format
Data in new cloud will be deleted. Do you want to continue? (y/N)
Canceling cloud-to-cloud migration
Use the following commands to cancel a migration that is already in progress.
1. Cancel the migration:
CLI (config)# replication migrate-to cancel
AltaVault displays a message prompting you to confirm cancellation of the job.
2. Select Y or N at the prompt. Select N to continue the migration. Select Y to end an in-progress migration. AltaVault
displays messages describing possible next steps:
To format the new cloud bucket, use "replication migrate-to format" CLI command
To resume migration, use "replication migrate-to enable skip-existing" CLI command
If you decide to continue the migration again, enter the replication migrate-to enable skip-existing
command to pick up where you left off, skipping data already transferred to the new bucket.
To wipe out any data transferred to the new bucket, enter the
replication migrate-to format command.
Amazon S3 or S3-IA to Glacier migration
If you are migrating from Amazon S3 or S3-infrequent access storage classes to Amazon Glacier, perform the
following steps:
To Next Page
Loading...
