Yes, you can use Windows Server Standard on the local machine as a caching system for Azure File Sync without being limited by the 2TB replication limit. The 2TB limit applies specifically to the data that is replicated to Azure using Azure File Sync.
With Azure File Sync, you can create a synchronization relationship between your local file server and an Azure file share. The primary purpose of Azure File Sync is to synchronize files between the local file server and Azure, providing cloud-based redundancy and offloading of less frequently accessed files to the cloud.
When using Azure File Sync, your local file server acts as a caching system for performance, allowing fast access to frequently used files. The local server will retain a copy of the most frequently accessed files while less frequently accessed files are stored in the Azure file share.
The caching system on the local server allows the CAD-focused client to achieve better performance by having the data readily available on the local network while still benefiting from the cloud redundancy provided by Azure.
Therefore, the 2TB replication limit does not technically apply to the local caching server because it is not replicating the entire dataset to Azure. Instead, it synchronizes and caches the most frequently used files while keeping less frequently accessed files in the Azure file share.
Please note that when setting up Azure File Sync, you need to ensure that the capacity of your local server's storage is sufficient to accommodate the files that need to be cached. Additionally, consider the bandwidth and latency between your local server and Azure for optimal performance.