This approach is suggested, if and only if you can accept downtime and absolutely guarantee no data changes on the server shares during the initial onboarding process. The following information can only be used with version 9 or above of the storage sync agent. Versions lower than 9 will not have the StorageSyncSelfService cmdlets.
Previous Versions is a Windows feature that allows you to utilize server-side VSS snapshots of a volume to present restorable versions of a file to an SMB client.
This enables a powerful scenario, commonly referred to as self-service restore, directly for information workers instead of depending on the restore from an IT admin. However, cloud tiering must be set to a compatible mode. Many Azure File Sync server endpoints can exist on the same volume. You have to make the following PowerShell call per volume that has even one server endpoint where you plan to or are using cloud tiering.
VSS snapshots are taken of an entire volume. By default, up to 64 snapshots can exist for a given volume, granted there is enough space to store the snapshots. VSS handles this automatically. The default snapshot schedule takes two snapshots per day, Monday through Friday. That schedule is configurable via a Windows Scheduled Task. The above PowerShell cmdlet does two things:.
In order to see if self-service restore compatibility is enabled, you can run the following cmdlet. It will list all volumes on the server as well as the number of cloud tiering compatible days for each. This number is automatically calculated based on the maximum possible snapshots per volume and the default snapshot schedule. So by default, all previous versions presented to an information worker can be used to restore from.
The same is true if you change the default schedule to take more snapshots. However, if you change the schedule in a way that will result in an available snapshot on the volume that is older than the compatible days value, then users will not be able to use this older snapshot previous version to restore from. Enabling self-service restore can have an impact on your Azure storage consumption and bill. This impact is limited to files currently tiered on the server.
Enabling this feature ensures that there is a file version available in the cloud that can be referenced via a previous versions VSS snapshot entry. If you disable the feature, the Azure storage consumption will slowly decline until the compatible days window has passed. There is no way to speed this up.
The default maximum number of VSS snapshots per volume 64 as well as the default schedule to take them, result in a maximum of 45 days of previous versions an information worker can restore from, depending on how many VSS snapshots you can store on your volume. If a maximum of 64 VSS snapshots per volume is not the correct setting for you, then change that value via a registry key. For the new limit to take effect, you need to re-run the cmdlet to enable previous version compatibility on every volume it was previously enabled, with the -Force flag to take the new maximum number of VSS snapshots per volume into account.
This will result in a newly calculated number of compatible days. Please note that this change will only take effect on newly tiered files and overwrite any customizations on the VSS schedule you might have made.
With agent version 11, a new mode becomes available on a server endpoint. This mode allows globally distributed companies to have the server cache in a remote region pre-populated even before local users are accessing any files. When enabled on a server endpoint, this mode will cause this server to recall files that have been created or changed in the Azure file share. A globally distributed company has branch offices in the US and in India. In the morning US time information workers create a new folder and new files for a brand new project and work all day on it.
Azure File Sync will sync folder and files to the Azure file share cloud endpoint. Information workers in India will continue working on the project in their timezone.
When they arrive in the morning, the local Azure File Sync enabled server in India needs to have these new files available locally, such that the India team can efficiently work off of a local cache. Enabling this mode prevents the initial file access to be slower because of on-demand recall and enables the server to proactively recall the files as soon as they were changed or created in the Azure file share.
It is important to realize that tracking changes in the Azure file share that closely on the server can increase your egress traffic and bill from Azure. If files recalled to the server are not actually needed locally, then unnecessary recall to the server can have negative consequences.
Use this mode when you know pre-populating the cache on a server with recent changes in the cloud will have a positive effect on users or applications using the files on that server. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode.
Is this page helpful? Please rate your experience Yes No. Any additional feedback? For more information, see: Region availability for Azure File Sync. Create a file share for a step-by-step description of how to create a file share. Important If you are installing. Note The Az. Note The Storage Sync Service inherits access permissions from the subscription and resource group it has been deployed into.
On the pane that opens, enter the following information: Name : A unique name per region for the Storage Sync Service. Subscription : The subscription in which you want to create the Storage Sync Service. Depending on your organization's configuration strategy, you might have access to one or more subscriptions.
An Azure subscription is the most basic container for billing for each cloud service such as Azure Files. Resource group : A resource group is a logical group of Azure resources, such as a storage account or a Storage Sync Service.
You can create a new resource group or use an existing resource group for Azure File Sync. We recommend using resource groups as containers to isolate resources logically for your organization, such as grouping HR resources or resources for a specific project. Location : The region in which you want to deploy Azure File Sync.
Only supported regions are available in this list. When you are finished, select Create to deploy the Storage Sync Service. Providers -contains "Microsoft. It combines bulletproof reliability with extremely easy-to-use interface.
Want to synchronize your Mac data with a PC? Free for personal use. Learn more about Sync Gateway ». Allway Sync What is Allway Sync? Meet Allway Sync. Free for moderate personal use It's a free sync software with limitations. Does not contain any spyware, adware, or malware. Keep Offline Data Transfer disabled as this is related to Azure Data Box which is outside of the scope for this tutorial.
The process might take a couple of minutes to complete. You will notice the endpoint is now displayed and the health status is set to pending. While the starts, click on the server shown below as Azure-FileSync.
The cloud endpoint runs a detection job every 24 hours, which means it might take up to 24 hours before files begin to sync. Head over to your Windows Server again and open the File Explorer. At this point, any files you add to any of these directories will be automatically synchronized to the Azure Files storage account. The same sync will also be performed on all files stored in the Azure Files storage account.
Syncing files down from Azure to your server will take some time. Changes made to the Azure file share by using the Azure portal or SMB are not immediately detected and replicated like changes to the server endpoint. This article walked you through setting up Azure File Sync from cloud to on-premises.
To deploy Azure File Sync was quite the exercise. ATA is known for its high-quality written tutorials in the form of blog posts. Why not write on a platform with an existing audience and share your knowledge with the world? Adam the Automator. Twitter Facebook LinkedIn.
Table of Contents. Storage Account Advanced options. Storage Account creation completed. Create New File Share. Directory creation. Deploy Azure File Sync Wizard.
Newly Deployed Storage sync resource. Sync Group Cloud Endpoint setup. Sync Group setup. Cloud Endpoint and Server Endpoints. Open Server Manager. Disable IE Security setting.
0コメント