Skip to content

Commit a656528

Browse files
committed
fix broken links
1 parent 107d910 commit a656528

2 files changed

Lines changed: 3 additions & 3 deletions

File tree

articles/storage/file-sync/file-sync-how-to-manage-tiered-files.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -100,7 +100,7 @@ When you exclude a file type or pattern, it won't be tiered from that server any
100100

101101
For example, if you exclude PDF files, the PDF files that you create directly on the server won't be tiered. However, any PDF files that you create on a different endpoint, such as another server endpoint or the Azure file share, will still download as tiered files. These excluded tiered files will be fully recalled within the next 3-4 days.
102102

103-
If you don't want any files to be in a tiered state, enable [proactive recalling](file-sync-cloud-tiering-overview.md#proactive-recalling). This feature will prevent tiered download of all files and stop background tiering.
103+
If you don't want any files to be in a tiered state, enable [proactive recall](file-sync-cloud-tiering-overview.md#proactive-recall). This feature will prevent tiered download of all files and stop background tiering.
104104

105105
### More information
106106

articles/storage/file-sync/file-sync-server-endpoint-create.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -99,9 +99,9 @@ After you select an initial download option, you can't change it after you confi
9999
100100
### File download behavior once initial download completes
101101

102-
How files appear on the server after initial download finishes depends on your use of the cloud tiering feature and whether or not you opted to [proactively recall changes in the cloud](file-sync-cloud-tiering-overview.md#proactive-recalling). The latter is a feature useful for sync groups with multiple server endpoints in different geographic locations.
102+
How files appear on the server after initial download finishes depends on your use of the cloud tiering feature and whether or not you opted to [proactively recall changes in the cloud](file-sync-cloud-tiering-overview.md#proactive-recall). The latter is a feature useful for sync groups with multiple server endpoints in different geographic locations.
103103

104-
* **Cloud tiering is enabled** </br> New and changed files from other server endpoints will appear as tiered files on this server endpoint. These changes will only come down as full files if you opted for [proactive recall](file-sync-cloud-tiering-overview.md#proactive-recalling) of changes in the Azure file share by other server endpoints.
104+
* **Cloud tiering is enabled** </br> New and changed files from other server endpoints will appear as tiered files on this server endpoint. These changes will only come down as full files if you opted for [proactive recall](file-sync-cloud-tiering-overview.md#proactive-recall) of changes in the Azure file share by other server endpoints.
105105
* **Cloud tiering is disabled** </br> New and changed files from other server endpoints will appear as full files on this server endpoint. They won't appear as tiered files first and then recalled. Tiered files with cloud tiering off are a fast disaster recovery feature and appear only during initial provisioning.
106106

107107
### Provisioning steps

0 commit comments

Comments
 (0)