Key takeaways

  • Recover with precision by using the new Point-in-Time Recovery (PITR) feature to restore your MariaDB databases to a specific moment, minimizing data loss after accidental changes or outages.
  • Speed up your recovery times with parallelized uploads and downloads that help you meet strict RTO and RPO targets during critical infrastructure incidents.
  • Simplify Azure operations by leveraging native support for Azure Blob Storage, allowing for seamless, automated backup and restore workflows within your existing cloud environment.

Running production databases on Kubernetes means planning for the moments when things go wrong: a bad deployment, accidental data changes, or infrastructure incidents. In MariaDB Enterprise Kubernetes Operator 26.03, we’re focused on strengthening disaster recovery with two major additions: Point-in-time recovery (PITR) for granular restores, and native Microsoft Azure Blob Storage support for reliable backup, restore, and recovery workflows for Azure customers.

These capabilities help teams tighten RPO/RTO targets, reduce downtime, and standardize recovery processes across environments—without adding operational complexity. Let’s take a look at what’s new.

Point-in-Time Recovery

The Enterprise Kubernetes Operator now enables granular database restores to an exact point in time for MariaDB primary/replica topologies. Point-in-time recovery is enabled by combining periodic physical backups made with mariadb-backup or VolumeSnapshot with interval-based binlog archiving to object storage. To restore a database, the Operator restores the latest base backup before a target timestamp and replays archived binlogs from the backup’s GTID position up to the requested moment. Additionally, the Enterprise Kubernetes Operator adds a configurable archiving cadence to control RPO, parallelized upload/download to reduce restore time (RTO), and binlog retention policy to prevent uncontrolled storage growth.

Microsoft Azure Blob Storage Support for Backup and Restore

Azure customers now have a native Azure Blob Storage support as an object storage backend for physical backups (mariadb-backup) and binlog archives. This enables backup/restore, bootstrap, scale-out, and recovery workflows to use Azure Blob Storage with the same experience as with S3 storage.

MariaDB Enterprise Kubernetes Operator 26.03 delivers a meaningful step forward in cloud-native resilience: Point-in-time restore brings precise recovery to a specific moment in time, and native Azure Blob Storage support extends backup and recovery workflows seamlessly to Azure. Together, these enhancements make it easier to meet SLAs, reduce data loss during incidents, and recover faster—while keeping everything Kubernetes-native and automated.

Simplify your operations with the MariaDB Enterprise Kubernetes Operator—available exclusively for Enterprise customers. Get started now or explore our documentation for a technical deep-dive.