You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/storage/file-sync/file-sync-cloud-tiering-overview.md
+10-9Lines changed: 10 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -91,13 +91,13 @@ Disks that have server endpoints can run out of space due to various reasons, ev
91
91
- Slow or delayed sync causing files not to be tiered
92
92
- Excessive recalls of tiered files
93
93
94
-
When the disk space runs out, Azure File Sync might not function correctly and can even become unusable. While it's not possible for Azure File Sync to completely prevent these occurrences, the low disk space mode (available in Azure File Sync agent versions starting from 15.1) is designed to prevent a server endpoint from reaching this situation.
94
+
When the disk space runs out, Azure File Sync might not function correctly and can even become unusable. While it's not possible for Azure File Sync to completely prevent these occurrences, the low disk space mode (available in Azure File Sync agent versions starting from 15.1) is designed to prevent a server endpoint from reaching this situation and also help the server get out of it faster.
95
95
96
-
For server endpoints with cloud tiering enabled and volume free space policy set, if the free space on the volume drops below the calculated threshold, then the volume is in low disk space mode.
96
+
For server endpoints with cloud tiering enabled, if the free space on the volume drops below the calculated threshold, then the volume is in low disk space mode.
97
97
98
98
In low disk space mode, the Azure File Sync agent does two things differently:
99
99
100
-
-**Proactive Tiering**: In this mode, the File Sync agent tiers files proactively to the cloud. The sync agent checks for files to be tiered every minute instead of the normal frequency of every hour. Volume free space policy tiering typically doesn't happen during initial upload sync until the full upload is complete; however, in low disk space mode, tiering is enabled during the initial upload sync, and files will be considered for tiering once the individual file has been uploaded to the Azure file share.
100
+
-**Proactive Tiering**: In this mode, the File Sync agent tiers files more proactively to the cloud. The sync agent checks for files to be tiered every minute instead of the normal frequency of every hour. Volume free space policy tiering typically doesn't happen during initial upload sync until the full upload is complete; however, in low disk space mode, tiering is enabled during the initial upload sync, and files will be considered for tiering once the individual file has been uploaded to the Azure file share.
101
101
102
102
-**Non-Persistent Recalls**: When a user opens a tiered file, files recalled from the Azure file share directly won't be persisted to the disk. Recalls initiated by the `Invoke-StorageSyncFileRecall` cmdlet are an exception to this rule and will be persisted to disk.
103
103
@@ -107,18 +107,18 @@ If a volume has two server endpoints, one with tiering enabled and one without t
107
107
108
108
### How is the threshold for low disk space mode calculated?
109
109
Calculate the threshold by taking the minimum of the following three numbers:
110
-
- 10% of volume free space in GiB
110
+
- 10% of volume size in GiB
111
111
- Volume Free Space Policy in GiB
112
112
- 20 GiB
113
113
114
114
The following table includes some examples of how the threshold is calculated and when the volume will be in low disk space mode.
115
115
116
116
| Volume Size | 10% of Volume Size | Volume Free Space Policy | Threshold = Min(10% of Volume Size, Volume Free Space Policy, 20GB) | Current Volume Free Space | Is Low Disk Space Mode? | Reason |
### How does low disk space mode work with volume free space policy?
@@ -134,7 +134,8 @@ Here are two ways to exit low disk mode on the server endpoint:
134
134
2. You can manually speed up the process by increasing the volume size or freeing up space outside the server endpoint.
135
135
136
136
### How to check if a server is in Low Disk Space mode?
137
-
Event ID 19000 is logged to the Telemetry event log every minute for each server endpoint. Use this event to determine if the server endpoint is in low disk mode (IsLowDiskMode = true). The Telemetry event log is located in Event Viewer under Applications and Services\Microsoft\FileSync\Agent.
137
+
- If a server endpoint is in low disk mode, it is displayed in Azure portal in the cloud tiering health section of Error + troubleshootin tab of the server endpoint.
138
+
- Event ID 19000 is logged to the Telemetry event log every minute for each server endpoint. Use this event to determine if the server endpoint is in low disk mode (IsLowDiskMode = true). The Telemetry event log is located in Event Viewer under Applications and Services\Microsoft\FileSync\Agent.
0 commit comments