<< Click to Display Table of Contents >> Navigation:  Peer Global File Service Help > Advanced Topics > Edge Caching

 

 

Overview

Edge Caching allows you to save storage space on edge storage devices (for example, storage devices used in branch offices) where only a small subset of files are used on a frequent basis.  Files that are used less frequently are replaced with stub files on the edge storage device so that it appears to have a complete set of files.  When a user accesses a stub file, Edge Caching retrieves the full version of the file from a master storage device.  The benefit of using Edge Caching is that it allows you to efficiently utilize storage capacity on edge devices while preserving fast access performance on files that are used most often.

Edge Caching offers flexible edge storage management with:

•The ability to assign an amount or percentage of available storage to be used on the edge storage device.

•Dynamic adjustments of the time periods used to determine whether to stub or rehydrate a file, allowing Edge Caching to keep the assigned storage space as full as possible (best experience for the end user).

•Direct integration with our file collaboration and file synchronization job types.

•Point-to-point data transfer capability between one edge and one or more masters.

•The flexibility to mix and match master and edge roles across different jobs.

•The ability to pin files or folders to always be local or always be stubbed on the edge storage device.

•Alerting to ensure you stay ahead of potential storage capacity limits.

Fundamental Concepts

A master participant has a complete set of hydrated files and no stub files.  An edge participant contains a subset of the complete, hydrated files on a master participant, while the rest of the files will be stub files that don't take up any space.  Users can retrieve stubbed files directly from a master participant as needed.  The goal of Edge Caching is to keep as much as possible cached locally on edge participants for rapid access.

Every edge participant must have at least one master participant assigned to it.  When a stub file needs to be rehydrated, Edge Caching will retrieve the file from a master participant.

User-defined business rules (volume and utilization policies) manage the storage capacity on edge devices.  Edge Caching scans edge participants on a set basis (typically at least once daily) and uses these policies to determine whether adjustments are needed, i.e., whether to stub files to free up space or to rehydrate files.  This ensures that the storage capacity is being used at optimum efficiency.