Forum Discussion
Azure Files hosting fslogix profile containters and now Hot LRS Write Operations costs exploding
In many cases, you will not be establishing a net new file share for your organization, but instead migrating an existing file share from an on-premises file server or NAS device to Azure Files. There are many tools, provided both by Microsoft and 3rd parties, to do a migration to a file share, but they can roughly be divided into two categories:
Tools which maintain file system attributes such as ACLs and timestamps:
Azure File Sync: Azure File Sync can be used as a method to ingest data into an Azure file share, even when the desired end deployment isn't to maintain an on-premises presence. Azure File Sync can be installed in place on existing Windows Server 2012 R2, Windows Server 2016, and Windows Server 2019 deployments. An advantage of using Azure File Sync as an ingest mechanism is that end users can continue to use the existing file share in place; cut-over to the Azure file share can occur after all of the data is finished uploading in the background.
Robocopy: Robocopy is a well-known copy tool that ships with Windows and Windows Server. Robocopy may be used to transfer data into Azure Files by mounting the file share locally and then using the mounting location as the destination in the Robocopy command.
Hi - thanks for the reply, but I am having difficulty understanding its relevance to my situation. Are you advocating that azure files is not the correct location for fslogix profiles given that 'in many cases you will not be establishing a new file share'?
Please elaborate - but thank you for taking the time to respond.