Use pull tasks to update your Main Repository with DAT and Engine update packages from the source site.
DAT and Engine files must be updated often. Trellix releases new DAT files daily, and Engine files less frequently. Deploy these packages to managed systems as soon as possible to protect them against the latest threats.
You can specify which packages are copied from the source site to the Main Repository.
Note
Extra.DAT files must be checked in to the Main Repository manually. They are available from the Trellix website.
A scheduled repository pull server task runs automatically and regularly at the times and days you specify. For example, you can schedule a weekly repository pull task at 5:00 a.m. every Thursday.
You can also use the Pull Now task to check updates into the Main Repository immediately. For example, when Trellix alerts you to a fast-spreading virus and releases a new DAT file to protect against it.
If a pull task fails, you must check the packages into the Main Repository manually.
Once you have updated your Main Repository, you can distribute these updates to your systems automatically with global updating or with replication tasks.
Considerations when scheduling a pull task
Consider these variables when scheduling pull tasks:
Bandwidth and network usage — If you are using global updating, as recommended, schedule a pull task to run when bandwidth usage by other resources is low. With global updating, the update files are distributed automatically after the pull task finishes.
Frequency of the task — DAT files are released daily, but you might not want to use your resources daily for updating.
Replication and update tasks — Schedule replication tasks and client update tasks to ensure that the update files are distributed throughout your environment.