How Intelligent Downloader Reuses Files During Fileset Upgrades

Summary

FileWave Intelligent Downloader reuses matching files that are already on a device when a Fileset is deployed. This reduces download size during self-healing and Fileset upgrades when content has not changed.

How FileWave decides to reuse a file

Before downloading Fileset content, the FileWave Client checks the device for an existing copy of each file.

A file is reused only when its file name, file size, and CRC all match:

1. The file exists with the same name.
2. The file size matches.
3. The file CRC matches.

When all three checks match, the Client skips that file instead of downloading it again.

Fileset overwrite properties can also keep an existing file:

1. Don't overwrite existing files upon deployment keeps a file that already exists.
2. Overwrite only if existing file is older keeps a device file whose creation date is newer than the server copy.

Symlinks are always replaced.

Plan a Fileset upgrade

Assume Fileset v1 is active and Fileset v2 contains the replacement version. Choose one of these rollout sequences:

1. Immediate: Create the v2 association, delete the v1 association, then run Model Update.
2. Scheduled: Schedule v2 to activate first, for example at 6:00 PM, then schedule v1 to delete after activation, for example at 6:01 PM. Shared files remain available to v2 and do not need to be downloaded again.