Skip to content

Commit 8a7bb58

Browse files
Stacyrch140Stacyrch140
authored
Merge pull request #277049 from khdownie/kendownie060324-2
free space policy cleanup
2 parents 40af774 + 0146cda commit 8a7bb58

File tree

1 file changed

+27
-27
lines changed

1 file changed

+27
-27
lines changed

‎articles/storage/file-sync/file-sync-cloud-tiering-policy.md

Lines changed: 27 additions & 27 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
22
title: Azure File Sync cloud tiering policies
3-
description: Details on how the date and volume free space policies work together for different scenarios.
3+
description: How the date policy and volume free space policy work together for different cloud tiering scenarios in Azure File Sync.
44
author: khdownie
55
ms.service: azure-file-storage
66
ms.topic: conceptual
7-
ms.date: 06/07/2022
7+
ms.date: 06/03/2024
88
ms.author: kendownie
99
---
1010

@@ -14,55 +14,55 @@ Cloud tiering has two policies that determine which files are tiered to the clou
1414

1515
The **volume free space policy** ensures that a specified percentage of the local volume the server endpoint is located on is always kept free.
1616

17-
The **date policy** tiers files last accessed x days ago or later. The volume free space policy will always take precedence. When there isn't enough free space on the volume to store as many days worth of files as described by the date policy, Azure File Sync will override the date policy and continue tiering the coldest files until the volume free space percentage is met.
17+
The **date policy** tiers files last accessed x days ago or later. The volume free space policy always takes precedence. When there isn't enough free space on the volume to store as many days worth of files as the date policy specifies, Azure File Sync overrides the date policy. It continues tiering the coldest files until meeting the volume free space percentage.
1818

1919
## How both policies work together
2020

21-
We'll use an example to illustrate how these policies work: Let's say you configured Azure File Sync on a 500-GiB local volume, and cloud tiering was never enabled. These are the files in your file share:
21+
Here's an example to illustrate how these policies work. Let's say you configure Azure File Sync on a 500 GiB local volume, and cloud tiering isn't enabled. You have these files in your file share:
2222

2323
|File Name |Last Access Time |File Size |Stored In |
2424
|----------|------------------|-----------|----------|
25-
|File 1 | 2 days ago | 10 GiB | Server and Azure file share
26-
|File 2 | 10 days ago | 30 GiB | Server and Azure file share
27-
|File 3 | 1 year ago | 200 GiB | Server and Azure file share
28-
|File 4 | 1 year, 2 days ago | 120 GiB | Server and Azure file share
29-
|File 5 | 2 years, 1 day ago | 140 GiB | Server and Azure file share
25+
|File A | 2 days ago | 10 GiB | Server and Azure file share
26+
|File B | 10 days ago | 30 GiB | Server and Azure file share
27+
|File C | 1 year ago | 200 GiB | Server and Azure file share
28+
|File D | 1 year, 2 days ago | 120 GiB | Server and Azure file share
29+
|File E | 2 years, 1 day ago | 140 GiB | Server and Azure file share
3030

31-
**Change 1:** You enabled cloud tiering, set a volume free space policy of 20%, and kept the date policy disabled. With that configuration, cloud tiering ensures 20% (in this case 100 GiB) of space is kept free and available on the local machine. As a result, the total capacity of the local cache is 400 GiB. That 400 GiB will store the most recently and frequently accessed files on the local volume.
31+
**Change 1:** You enabled cloud tiering, set a volume free space policy of 20%, and kept the date policy disabled. With that configuration, cloud tiering ensures 20% (in this case 100 GiB) of space is kept free and available on the local machine. As a result, the total capacity of the local cache is 400 GiB. This cache stores the most recently and frequently accessed files on the local volume.
3232

33-
With this configuration, only files 1 through 4 would be stored in the local cache, and file 5 would be tiered. This only accounts for 360 GiB out of the 400 GiB that could be used. File 5 is 140 GiB and would exceed the 400-GiB limit if it was locally cached.
33+
With this configuration, only files A through D would be stored in the local cache, and file E would be tiered. This only accounts for 360 GiB out of the 400 GiB that could be used. File E is 140 GiB and would exceed the limit if it was locally cached.
3434

35-
**Change 2:** Say a user accesses file 5. This makes file 5 the most recently accessed file in the share. As a result, File 5 would be stored in the local cache and to fit under the 400-GiB limit, file 4 would be tiered. The following table shows where the files are stored, with these updates:
35+
**Change 2:** Say a user accesses file E, making file E the most recently accessed file in the share. As a result, file E would be stored in the local cache, and to fit under the limit of 400 GiB, file D would be tiered. The following table shows where the files are stored with these updates:
3636

3737
|File Name |Last Access Time |File Size |Stored In |
3838
|----------|------------------|-----------|----------|
39-
|File 5 | 2 hours ago | 140 GiB | Server and Azure file share
40-
|File 1 | 2 days ago | 10 GiB | Server and Azure file share
41-
|File 2 | 10 days ago | 30 GiB | Server and Azure file share
42-
|File 3 | 1 year ago | 200 GiB | Server and Azure file share
43-
|File 4 | 1 year, 2 days ago | 120 GiB | Azure file share, tiered locally
39+
|File E | 2 hours ago | 140 GiB | Server and Azure file share
40+
|File A | 2 days ago | 10 GiB | Server and Azure file share
41+
|File B | 10 days ago | 30 GiB | Server and Azure file share
42+
|File C | 1 year ago | 200 GiB | Server and Azure file share
43+
|File D | 1 year, 2 days ago | 120 GiB | Azure file share tiered locally
4444

45-
**Change 3:** Imagine you updated the policies so that the date-based tiering policy is 60 days and the volume free space policy is 70%. Now, only up to 150 GiB can be stored in the local cache. Although File 2 has been accessed less than 60 days ago, the volume free space policy will override the date policy, and file 2 is tiered to maintain the 70% local free space.
45+
**Change 3:** Imagine you updated the policies so that the date policy is 60 days and the volume free space policy is 70%. Now, only up to 150 GiB can be stored in the local cache. Although file B was accessed less than 60 days ago, the volume free space policy overrides the date policy, and file B is tiered to maintain the 70% local free space.
4646

4747
**Change 4:** If you changed the volume free space policy to 20% and then used `Invoke-StorageSyncFileRecall` to recall all the files that fit on the local drive while adhering to the cloud tiering policies, the table would look like this:
4848

4949
|File Name |Last Access Time |File Size |Stored In |
5050
|----------|------------------|-----------|----------|
51-
|File 5 | 1 hour ago | 140 GiB | Server and Azure file share
52-
|File 1 | 2 days ago | 10 GiB | Server and Azure file share
53-
|File 2 | 10 days ago | 30 GiB | Server and Azure file share
54-
|File 3 | 1 year ago | 200 GiB | Azure file share, tiered locally
55-
|File 4 | 1 year, 2 days ago | 120 GiB | Azure file share, tiered locally
51+
|File E | 1 hour ago | 140 GiB | Server and Azure file share
52+
|File A | 2 days ago | 10 GiB | Server and Azure file share
53+
|File B | 10 days ago | 30 GiB | Server and Azure file share
54+
|File C | 1 year ago | 200 GiB | Azure file share tiered locally
55+
|File D | 1 year, 2 days ago | 120 GiB | Azure file share tiered locally
5656

57-
In this case, files 1, 2 and 5 would be locally cached and files 3 and 4 would be tiered. Because the date policy is 60 days, files 3 and 4 are tiered, even though the volume free space policy allows for up to 400 GiB locally.
57+
In this case, files A, B, and E would be locally cached and files C and D would be tiered. Because the date policy is 60 days, files C and D are tiered, even though the volume free space policy allows for up to 400 GiB locally.
5858

5959
> [!NOTE]
60-
> Files are not automatically recalled when customers change the volume free space policy to a smaller value (for example, from 20% to 10%) or change the date policy to a larger value (for example, from 20 days to 50 days).
60+
> Files aren't automatically recalled when customers change the volume free space policy to a smaller value (for example, from 20% to 10%) or change the date policy to a larger value (for example, from 20 days to 50 days).
6161
6262
## Multiple server endpoints on a local volume
6363

64-
Cloud tiering can be enabled for multiple server endpoints on a single local volume. For this configuration, you should set the volume free space to the same amount for all the server endpoints on the same volume. If you set different volume free space policies for several server endpoints on the same volume, the largest volume free space percentage will take precedence. This is called the **effective volume free space policy**. For example, if you have three server endpoints on the same local volume, one set to 15%, another set to 20%, and a third set to 30%, they'll all begin to tier the coldest files when they have less than 30% free space available.
64+
You can enable cloud tiering for multiple server endpoints on a single local volume. For this configuration, you should set the volume free space to the same amount for all the server endpoints on the same volume. If you set different volume free space policies for several server endpoints on the same volume, the largest volume free space percentage takes precedence. This is called the **effective volume free space policy**. For example, let's say you have three server endpoints on the same local volume: one set to 15%, another set to 20%, and a third set to 30%. All three will begin to tier the coldest files when they have less than 30% free space available.
6565

66-
## Next steps
66+
## Next step
6767

6868
- [Monitor cloud tiering](file-sync-monitor-cloud-tiering.md)

0 commit comments

Comments
 (0)