azure-docs
azure-docs copied to clipboard
AzCopy
Why does this page mention Robocopy (legacy technology) and not AzCopy? My understanding is that AzCopy is always the preferred method. https://learn.microsoft.com/en-us/azure/storage/common/storage-choose-data-transfer-solution
If that is not the case then I think this page should clarify why robocopy would be preferred
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.
- ID: b27945d1-3a56-32a7-11a6-79f535766a76
- Version Independent ID: ac7de2fe-5feb-cdaa-5ffb-800c099c1a71
- Content: Data migration and protection FAQs for Azure NetApp Files
- Content Source: articles/azure-netapp-files/faq-data-migration-protection.md
- Service: azure-netapp-files
- GitHub Login: @b-hchen
- Microsoft Alias: anfdocs
@thommck
Thanks for your feedback! We will investigate and update as appropriate.
@thommck Thanks for bringing this to our attention. I'm going to assign this to the document author so they can take a look at it accordingly.
@b-hchen Can you please check and add your comments on this doc feedback as applicable.
@thommck - thanks for raising this. As I understand, azcopy does not support an SMB to SMB migration. If I am harboring a misunderstanding, please let me know.
AzCopy can be used to upload, download, sync or copy data from multiple locations. SMB is supported (as are others).
Here is a good link to see more details https://learn.microsoft.com/en-us/azure/storage/common/storage-ref-azcopy-copy
Thanks, Thom
On Fri, 16 Dec 2022, 16:32 Andrew Hibbard, @.***> wrote:
@thommck https://github.com/thommck - thanks for raising this. As I understand, azcopy does not support an SMB to SMB migration. If I am harboring a misunderstanding, please let me know.
— Reply to this email directly, view it on GitHub https://github.com/MicrosoftDocs/azure-docs/issues/102790#issuecomment-1355182455, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHC7URURXBKMY3F4RSPKPX3WNSKQTANCNFSM6AAAAAAS7VZDAA . You are receiving this because you were mentioned.Message ID: @.***>
Hello @thommck, with AzCopy, either the source OR destination must be an Azure storage account. In our FAQ for Azure NetApp Files (ANF), we are making recommendations for migrations from non-Azure storage (typically on-prem SMB servers) in to ANF. In this scenario the source and target are both SMB and therefore AzCopy is not supported.
Ok, I see the note (in the purple box) on the docs now. That is really interesting, I wasn't aware of that limitation. I guess it's something that a lot of people will assume as it is talked about so much in the CAF & storage docs but those docs don't specifically call out that ANF isn't the same as the storage used for Azure Files
Thanks, Thom
On Fri, 16 Dec 2022, 21:00 Sean Luce, @.***> wrote:
Hello @thommck https://github.com/thommck, with AzCopy, either the source OR destination must be an Azure storage account. In our FAQ for Azure NetApp Files (ANF), we are making recommendations for migrations from non-Azure storage (typically on-prem SMB servers) in to ANF. In this scenario the source and target are both SMB and therefore AzCopy is not supported.
— Reply to this email directly, view it on GitHub https://github.com/MicrosoftDocs/azure-docs/issues/102790#issuecomment-1355600906, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHC7URXNOZFVFF7KIABHN7TWNTJ7NANCNFSM6AAAAAAS7VZDAA . You are receiving this because you were mentioned.Message ID: @.***>
Thanks for your input Thom and Sean. #please-close