Skip to main content

How Intelligent Downloader Reuses Files During Fileset Upgrades

Summary

ThisFileWave KB article will explain the intelligent downloader and give the best practices to upgrade your self-healed software by benefiting from this feature through Filesets / Payloads.

Intelligent Downloader

Whenreuses matching files that are already on a device when a Fileset / Payload is deployeddeployed. This reduces download size during self-healing and theFileset timeupgrades when content has not changed.

How FileWave decides to downloadreuse hasa come,file

Before downloading Fileset content, the FileWave Client willchecks checkthe device for an existing exact copiescopy of theeach Fileset files before it starts the download.file.

TheA matchfile is metreused only if: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.

TheWhen clientall willthree skipchecks match, the Client skips that file instead of downloading allit filesagain.

that

Fileset matchoverwrite properties can also keep an existing copies on the disk.

The Client will also skip the download in two other cases:file:

  1. The Fileset files are set to never overwrite when the Fileset property "Don't overwrite existing files upon deployment"deployment keeps a file that already exists.
Overwrite only if existing file is checked.older Thekeeps filesa device file whose creation date is newer than the ones in the server and this Fileset property is checked "Overwrite only if existing file is older".copy.

Note: Symlinks willare always be replaced.

UpgradingPlan youra SoftwareFileset upgrade

There are two scenarios to best upgrade your self-healed software (we assumeAssume Fileset v1 is active onand Fileset v2 contains the clients)replacement version. Choose one of these rollout sequences:

  1. Immediate: Create the associationv2 to Fileset v2,association, delete the associationv1 association, then run Model Update.
Scheduled: Schedule v2 to Filesetactivate first, for example at 6:00 PM, then schedule v1 andto updatedelete theafter model.activation, (thisfor willexample startat the6:01 upgradePM. immediately)Shared Createfiles theremain associationavailable to Fileset v2 and setdo itnot need to activatebe atdownloaded some time in the future eg: 06:00PM and then make the Fileset v1 to Delete at 06:01pm (some time after v2 has activated)

Note: If you set the delete time of v1 before activating v2, you end up deleting files that are needed to activate v2 and the missing files will download at verification. So, to best benefit from the intelligent downloader, it is better to go for 2. knowing that deleting Fileset v1 at 06:01PM will not delete common files with v2.again.
Back to top