Skip to content

Commit 55c337c

Browse files
committed
removing proactive recall screenshot
1 parent 12eecdd commit 55c337c

File tree

1 file changed

+0
-2
lines changed

1 file changed

+0
-2
lines changed

articles/storage/file-sync/file-sync-cloud-tiering-overview.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -62,8 +62,6 @@ If files recalled to the server aren't needed locally, then the unnecessary reca
6262

6363
Enabling proactive recalling might also result in increased bandwidth usage on the server and could cause other relatively new content on the local server to be aggressively tiered due to the increase in files being recalled. In turn, tiering too soon might lead to more recalls if the files being tiered are considered hot by servers.
6464

65-
:::image type="content" source="media/storage-sync-files-deployment-guide/proactive-download.png" alt-text="An image showing the Azure file share download behavior for a server endpoint currently in effect and a button to open a menu that allows to change it.":::
66-
6765
For more information on proactive recall, see [Deploy Azure File Sync](file-sync-deployment-guide.md#optional-proactively-recall-new-and-changed-files-from-an-azure-file-share).
6866

6967
## Tiered vs. locally cached file behavior

0 commit comments

Comments
 (0)