How to migrate Netapp files volume from one subscription to another using robocopy

Question

I want to migrate azure netapp files from one subscription to another. I was suggested robocopy via ms support engineer. but as the source AD joined, I am not able to create a target volume with the same AD and it is throwing an error. My netapp volume is SMB sand in the target also I want the same.

I want to migrate the data in netapp only, cant understand the response of Q/A assist, in the last line.

please let me know the process or any alternate way.

Answer 1

To migrate Azure NetApp Files from one subscription to another using Robocopy, you can follow these steps:

1. Deploy a Windows virtual machine (VM) in Azure in the same region as your source Azure NetApp Files volume. Keeping the data and networking in Azure will be fast and avoid outbound data transfer charges. For optimal performance, we recommend a multi-core VM type with at least 56 GiB of memory, for example Standard_DS5_v2.
2. Mount both the source and target Azure NetApp Files volumes to the VM. Be sure to mount them using the storage account key to make sure the VM has access to all the files. Don't use a domain identity.
3. Run the following command at the Windows command prompt. Optionally, you can include flags for logging features as a best practice (/NP, /NFL, /NDL, /UNILOG).

robocopy <source> <target> /MIR /COPYALL /MT:16 /R:2 /W:1 /B /IT /DCOPY:DAT

If your source volume was mounted as s:\ and target was t:\ the command looks like this:

robocopy s:\ t:\ /MIR /COPYALL /MT:16 /R:2 /W:1 /B /IT /DCOPY:DAT

4. After the initial run completes, disconnect your application from the existing volume and run the same robocopy command again. This will copy over all the changes that happened since the initial run, skipping any file data that has already copied over.
5. After the command completes for the second time, you can redirect your application to the new volume.

Note: If the source Azure NetApp Files volume is AD-joined, you may not be able to create a target volume with the same AD. In this case, you can create a new volume and use Robocopy to migrate the data to the new volume.

---

References:

• Migrate files between SMB Azure file shares - Migrate using Robocopy

Answer 2

@Pal, Anusree (External) Firstly, Apologies for the delay response!
Welcome to Microsoft Q&A Forum, Thank you for posting your query here!

As I understand you need to migrate data between SMB volumes across the subscriptions within the same region.

There is no direct way or tool from Azure NetApp files end to migrate data between subscriptions. We suggested cx create a separate SMB volume in target subscription and use any file-based copy tool to migrate the data. For windows, widely used common tool is robocopy for file copy.

During the call with MS support, you have mentioned that they were unable to deploy the SMB volume on target location and its failing with “unable to query DNS server”. I was able to check you supported cases.

• Corrected source volume deployment issue as picked wrong network deployment.
• Found there was no peering between ADDC server hosted in source subscription and target subscription ANF network.
• Made peering between AD and ANF networks, after that able to deploy SMB volume without any issue and access them.
• You can use AD connection hosted within same region, same subscription, across regions, across subscriptions and on-prem, but make sure there should be connectivity exist between ADDC/DNS servers and ANF network.
• If you are delete the peering with AD hosted vNET then they will lose the connectivity to ANF volume hosted in target subscription.

Please let us know if you have any further queries. I’m happy to assist you further.    

---

Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.