Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi AltaVault experts!
We're working in a troubleshooting situation related to migrate cloud-to-cloud from private cloud provider (EMC) to another cloud provider (Azure).
Customer began the migration process but they only coud complete around 75% aprox of data and rest of data couldn't migrate. They want to complete the migration but they're stucked on it.
From the GUI, the list of objects are visible to be prepopulated but the job shows failed.
Is it possible to resume a migration of the objects that first migration job couldn't complete or the migration needs to startover again the complete migration?
I put here some system logs that I catched that might clarify the problem:
<storage-name> [backend/storage/azure.ERR] (43088) Error Detail: :
sw_raid: rrdm tool failed with error [Raid commands are not supported on model AVA400]
<storage-name>batch[49272]: [batch.INFO]: user admin: Executing command: show hardware error-log all
<storage-name>batch[49272]: [batch.INFO]: user admin: Skipping authorization check for show hardware error-log all
<storage-name> cli[33151]: [cli.NOTICE]: user admin: CLI error: Cannot show datastore integrity check status unless service is running.
<storage-name> rfsd[8639]: [replication_mgr.INFO] (13696) File <filename> doesn't exist anymore: No such file or directory
Thanks in advance!
Solved! See The Solution
1 ACCEPTED SOLUTION
tahmad has accepted the solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Leandrosn,
You can use the following command to restart the migration:
CLI (config)# replication migrate-to skip-existing
Replication will be paused and service will be restarted Continue? [y/n]
If you still continue to encounter issues, please open a case with NetApp Technical Support for further assistance on the migration.
Regards,
Team NetApp
Team NetApp
1 REPLY 1
tahmad has accepted the solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Leandrosn,
You can use the following command to restart the migration:
CLI (config)# replication migrate-to skip-existing
Replication will be paused and service will be restarted Continue? [y/n]
If you still continue to encounter issues, please open a case with NetApp Technical Support for further assistance on the migration.
Regards,
Team NetApp
Team NetApp