Caching Hot Files with Azure File Sync Cloud Tiering

What Local Caching with Cloud Tiering Is

Cloud tiering is an optional feature of Azure File Sync that separates active data from inactive data. Frequently accessed files (known as hot data) are cached directly on the local Windows Server endpoint, while infrequently accessed files (known as cold data) are converted into lightweight pointer files (reparse points) and stored in Azure Files.

How It Meets the Requirements

• Lowest Access Latency: By keeping active, frequently accessed files on the local file server volume, users and applications read data directly from high-speed local storage without incurring network delays.
• Minimized Egress and Transaction Costs: Retaining hot files on-premises prevents frequent file recalls across the network, substantially decreasing cloud egress charges and API transaction fees.
• Optimized Local Capacity: Inactive cold files occupy minimal local disk capacity, freeing up expensive on-premises storage without requiring costly on-premises hardware expansions.

Key Advantages and Capabilities

• Seamless User Experience: Tiered files appear intact in Windows File Explorer; when a user opens a cold file, Azure File Sync transparently recalls it from Azure in the background.
• Policy Flexibility: Supports volume free space policies and optional date policies to automatically determine which files remain cached and which are tiered.
• Predictable Cost Profile: Balances the cost of local disk capacity with Azure cloud storage rates, optimizing the overall total cost of ownership (TCO).
• Bandwidth Optimization: Minimizes WAN bandwidth consumption by avoiding unnecessary data synchronization and recall cycles.

Why This Is Optimal

This strategy provides the ideal balance between on-premises performance metrics and cloud cost implications. Serving active workloads from local disk eliminates latency, while storing bulk cold data in Azure lowers overall physical storage expenditures and operational overhead.