Binary release upgrade
This scenario covers upgrade/downgrade within the current release line without changing the on-disk format.
Invariants
- The upgrade changes binaries and unit/scripts, but does not touch user data.
- The data directory
/var/lib/angarabaseis not deleted. - The config
/etc/angarabase/angarabase.confis preserved (package noreplace policy).
Upgrade via DEB/RPM
DEB
sudo dpkg -i angarabase-server_<VERSION>_amd64.deb
sudo systemctl status angarabase --no-pager
RPM
sudo rpm -Uvh angarabase-server-<VERSION>-1.x86_64.rpm
sudo systemctl status angarabase --no-pager
Upgrade from tarball
sudo systemctl stop angarabase
sudo install -m 0755 bin/angarabase-server /usr/bin/angarabase-server
sudo install -m 0755 bin/angara-cli /usr/bin/angara-cli
sudo systemctl daemon-reload
sudo systemctl start angarabase
Post-upgrade check
angarabase-server --version
sudo systemctl is-active angarabase
Smoke-check:
- the server starts without panic;
- config and data dir are accessible;
- the basic SQL health check passes.
Rollback
Rollback is performed by installing the previous package/archive.
Important: rollback is allowed only between compatible storage-contract versions.
Next
After a successful upgrade and post-upgrade checklist:
- Crash recovery — what to do if the new version does not start.
- Backup and restore — take a control backup immediately after the upgrade.
- Verify release artifacts — make sure the next version is downloaded and verified the same way.
- Operator deep-dive: Upgrade and migration — full playbook with rollback scenarios.