![]() After making all decisions, click on Create.Īfter creating the Storage Account to support the upcoming Azure File Sync, our next step is to replicate the share structure that we have on-premises in the Storage Account/Files. In this article, we will be creating a Storage Account called techgenix and we will use Storage V2 (general purpose v2) account, and Standard performance (magnetic disks, low cost). ![]() From the design perspective, it is highly recommended to use a GRS (Geo-Redundant Storage which uses the three local replicas three additional replicas in another region) to make sure that all data that is being synchronized to the cloud does not have a single point of failure. We added some pictures and a new folder in the share, as depicted in the image below (please note that we are accessing that information through UNC path.)īefore creating the Azure File Sync, we need to prepare a Storage Account that will receive all data from the File Servers on-premises. For this article it is located on C:\home\public (in a production environment it must be located in a different disk other than the operating system volume). To understand better how Azure File Sync works, let’s create a simple scenario where we have a File Server on-premises called TORFS01 and we have a Public shared folder. In this article, we will cover these basic steps and make sure that all data from our file server is in a resilient and redundant cloud storage solution. The process to use Azure File Sync comprises three steps: configure the service in Microsoft Azure, install the agents, and configure the replication. ![]() For the end-user it is a transparent process and no additional tools are required. Last but not least, we can leverage the cloud and use tiering, where unused files on the local file servers can be moved to Azure Files and a local reference of the file stays locally. ![]() One thing in common on all these scenarios is the ability to move your file server data to the cloud and reduce costs on-premises by removing backup requirements, disaster recovery, or eliminating the file server all together.Īzure File Sync can be used as a transition tool to move file server data to the cloud, but also as a synchronization tool to keep more than one server synchronized without the use of DFS or any other replication technology. There are several benefits of using this approach - it could be used for transition between on-premises and cloud, backup, and disaster recovery. Microsoft Azure has an offering called Azure File Sync, which allows the synchronization of on-premises file servers with Azure Files supported by Storage Accounts. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |