DATABASES Signal 160
Autobase 2.11 released
↗
Illustration only Photo by Zoshua Colah on Unsplash
Autobase 2.11 completes the platform’s roadmap by enabling UI-managed scaling, upgrades, backup and point-in-time recovery for PostgreSQL clusters, plus new Ansible playbooks for backup operations.
Engineers can now provision read replicas, perform minor and major version upgrades, and manage backups and restores without leaving the Autobase Console UI. This consolidates cluster lifecycle tasks that previously required separate tools or manual scripts. The addition of Ansible playbooks lets teams automate backup and recovery workflows within existing infrastructure automation.
Written by elseif from the cluster below · every claim links back to a sourceThe three things worth knowing
UI-managed scaling lets operators specify a desired node count to automatically provision PostgreSQL read replicas on cloud, bare-metal or virtual machines.
UI-supported upgrades handle minor version updates with ~5-10 seconds write downtime and major version updates with ~30-60 seconds downtime, using existing cloud configuration.
UI-managed backup and PITR configure backup method, storage, retention and schedule, and provide restore options for latest, point-in-time or specific backups, complemented by new Ansible playbooks for backup and recovery.
THE READ
What the cluster adds up to.
The release shifts scaling, upgrades, backup and point-in-time recovery from external tools or scripts into the Autobase Platform UI. Previously, operators had to use separate consoles, CLI tools or custom automation for these tasks. Now the UI provides a single interface for specifying replica counts, initiating upgrades and configuring backup policies. This change reduces the need to context-switch between multiple systems.
Adopting the UI-managed features does not require additional infrastructure beyond the existing cloud or bare-metal setup, as the Platform uses the current cloud configuration to provision servers and related resources. Operators continue to use their existing provisioning credentials and networking setup. The shift mainly involves using the Platform UI for tasks that were previously performed elsewhere.
Certain limitations remain: in-place major version upgrades still incur an expected downtime of roughly 30-60 seconds, and a near-zero-downtime blue-green upgrade workflow is planned for a future release but is not yet available. Scaling depends on having a valid cloud configuration or accessible bare-metal/virtual-machine hosts. Backup functionality relies on underlying tools such as pgBackRest or WAL-G, which must be enabled via the new Ansible playbooks or manual setup.
Overall, engineers gain the ability to manage the complete PostgreSQL cluster lifecycle, from provisioning replicas to upgrading versions and restoring data, from a single console. The new Ansible playbooks enable integration of backup and recovery steps into existing infrastructure-as-code pipelines, reducing manual effort. This consolidation can improve operational consistency and lower the risk of errors caused by using disjointed tooling.
Written by elseif from the cluster below · checked for specifics the sources never containedTHE CLUSTER