Update Eav Uzsoft Uz Zip | Offline

A *.uz file is a standard ZIP archive with:

Example structure:

update_v2.3.1.uz
├── manifest.uz
├── db/
│   ├── eav_attributes.sql
│   └── seed_values.json
├── web/
│   ├── app/
│   └── public/
├── hooks/
│   ├── pre_update.sh
│   └── post_update.php
└── update.uzsig

Depending on what was inside the zip file, follow the corresponding method: offline update eav uzsoft uz zip

Method A: If there is an executable (.exe) file

Method B: If there is a folder structure (Manual Mirror Update) If the zip file contains a mirror of the update server (folders with .nup files), you need to point ESET to that folder. Example structure: update_v2

Because EAV lacks a fixed schema, the UZ package includes a eav_diff.json that describes:

The offline tool applies these changes directly to the system’s EAV tables without external validation. Depending on what was inside the zip file,

Before diving into the technical steps, let’s deconstruct the search term:

Understanding this structure is key to a successful offline update.

Because the UZ.zip is applied while the node is in standby, there is zero downtime. The caveat: your cluster must be on the same offline network segment.

uzsoft-cli validate update_v2.3.1.uz

This checks: