Using a default local volume with side caching

After a file is transferred to the final destination volume, it is prepopulated into the exit cache on the remote FSC group if side caching is enabled. Enable side caching by explicitly defining exit FSCs. Entry FSCs and FSCs not configured in the FMS primary configuration file (fmsmaster_fscid.xml) as exit FSCs do not perform side caching. Normal caching behavior applies in these circumstances. Side caching is performed only for the highest priority exits defined in the primary configuration file. For example, if three exits are defined, two set to priority 0 and one set to priority 1, only the two exits with priority 0 are side cached. The following graphic illustrates a caching configuration designed to support a large number of users. In the example, one remote user uploads a file. Another remote user requests a download of the same file. Without side caching configured, the file is only cached after the initial download. With side caching enabled, after the file is transferred to the final destination volume, it is automatically side cached to the defined exit FSCs in the remote FSC group. In this example, the remote user requesting the download receives the file from Exit FSC 2. Note The transfer to the final destination volume may not occur immediately. Until the transfer occurs, remote users requesting download of the file receive it directly from the default local volume on their LAN.