Removing an agent: uninstall and backups
Remove on the Agents page now opens a page with two choices (with four-eyes approval on, a second user approves them):
- Uninstall the agent from the computer — an online agent (from this version) reports to the console, uninstalls itself (Windows: its MSI; Linux: the deb or rpm package) and is then removed from the console with its jobs and history. An offline agent is removed from the console only.
- Its backups — the page lists the storage, jobs and number of backups:
- Keep all backups (default) — they stay on the storage and can still be restored.
- Keep only the newest backup of each job — each backup is complete (deduplicated), so the newest one still restores everything as of its date; database jobs keep the logs that belong to it. The space of the others is freed.
- Delete all backups of this agent — the repository files and folders are deleted.
Deleting needs the computer's name typed in. The console deletes in the background and writes the result to the audit log. Immutable storage (S3 Object Lock, hardened repository) keeps locked data until the lock expires; backups on a disk of the computer itself and copies made by copy jobs are not deleted. The page warns when the agent also backs up other systems (Proxmox, VMware, Hyper-V, Microsoft 365, NAS).
Tested in the lab: a Linux agent uninstalled itself and was removed, its three backups were reduced to the newest; another agent's repository on SFTP was deleted completely; on Windows the agent finds its MSI installation.
The user guide (Agents → Removing an agent) describes it in all 14 languages.
Update the console and then the agents (Agents → Update all) — agents need this version to uninstall themselves.
Releases are signed with the BackupZit release key; consoles verify them before installing.
