Safe uninstall and data retention

Prerequisites and authority

Local installation authority, a complete approved release package, working Docker and access to the deployment record are required. Preserve existing data before installation/update/removal.

Remove BryanNet while preserving data

Stopping the deployment and permanently purging it are different operations. Start with a data-preserving stop. This release's Control and Linux command wrapper provide service control; this guide does not claim a separate graphical uninstaller with a retention checkbox.

1. Schedule the service interruption and notify affected users.
2. Record the release, storage locations and reason for removal.
3. Create and verify an encrypted backup; store its recovery key separately.
4. Export required operational records through supported functions.
5. On Windows use Stop BryanNet in Control. On Linux use bryannet stop with the required host privileges. These are service-stop operations, not deletion of the installed database or configuration. Review automatic startup/update services separately if the host is being decommissioned.
6. Verify which containers, services, files and volumes remain.
7. Record how the retained data will be protected or restored.

Stopping BryanNet management does not automatically remove configuration or active users from routers. Decide the network handover with Shipped Desired State presets and safe customization and Planned maintenance windows and notifications before removing the host.

Permanent purge

Purge requires a separate explicit choice covering database volumes, configuration, backups, logs and off-site objects. Confirm the retention obligations and recovery consequences first. Do not use a generic volume-deletion command as the default uninstall instruction.

If the purpose is moving to another machine, perform a verified replacement-host recovery before decommissioning the old host. Avoid two active deployments managing the same routers simultaneously. Permanent deletion of containers, volumes, files or remote backups must be a separate administrator decision based on the actual installation paths and recovery obligations; it is not performed by the stop commands above.

Related guides

Related guides: First-deployment walkthrough and success checklist, Deployment verification and first login, Back up BryanNet and validate backups, Restore BryanNet safely, Product updates, compatibility and rollback.