If volume free space policy is configured, files will be recalled until the volume free space policy setting is reached.-Order CloudTieringPolicy will recall the most recently modified or accessed files first and is allowed by the current tiering policy.When a file is fully recalled, Azure File Sync removes this attribute. Indicates that some or all of the file's content is not stored on disk. When a file is fully recalled, Azure File Sync removes the reparse point from the file.
Users won't need to know that Azure File Sync is being used or how to get access to the file in your Azure file share. Azure File Sync uses reparse points to define to the Azure File Sync file system filter (StorageSync.sys) the cloud location where the file is stored. A reparse point is a special pointer for use by a file system filter. Indicates that the file has a reparse point.
This attribute is only set on Windows Server 2019. Reading the file will cause at least some of the file content to be fetched from an Azure file share to which the server endpoint is connected. Indicates that the file's data is not fully present on local storage. This attribute is only set on Windows Server 2016 and older. If a file is fully recalled to disk, Azure File Sync converts it from a sparse file to a regular file. In a partially recalled file, that part of the file is already on disk. In a fully tiered file, the file stream is stored in the cloud. Azure File Sync uses sparse files because a file is either fully tiered or partially recalled. A sparse file is a specialized type of file that NTFS offers for efficient use when the file on the disk stream is mostly empty. Indicates that the file is a sparse file. This attribute is always set, regardless of whether the file is tiered or stored fully on disk. Indicates that the file should be backed up by backup software. A tiered file has the following attributes set: Attribute letter How can I tell whether a file has been tiered?Ĭheck the file attributes on the file.Right-click on a file, go to Details, and then scroll down to the Attributes property. Only as many files will be recalled as fit within the volume free space policy and the optional date policy.
If you choose to download the namespace and recall content during initial download to your server, then after the namespace comes down, files will be recalled based on the last modified timestamp. Whether that is for a second server or during a disaster recovery situation. When you add a new server endpoint, it is possible that you connect an empty server location to an Azure file share with your data in it.
The one-hour interval applies here as well. However, the optional date policy will begin to work on an individual file basis, as soon as a file has been uploaded. The volume free space policy will not begin its work until initial upload of all files has finished. They need to be uploaded first, before cloud tiering can begin.
In the absence of a last access time, the last modified time is used to evaluate the relative position in the heatmap.
However, when a new server endpoint is created, with cloud tiering enabled, then initially not enough time has passed to observe file access. Typically, last access time is tracked and available. To determine the relative position of an individual file in that heatmap, the system uses the maximum of either of the following timestamps, in that order: MAX(Last Access Time, Last Modified Time, Creation Time). The cloud tiering heatmap is essentially an ordered list of all the files that are syncing and are in a location that has cloud tiering enabled.