Aerospike Backup Service 3.5.0 release notes

March 6, 2026 | Download

This release delivers improved backup resilience and job immutability, simplified restore-by-timestamp requests, and expanded TLS configuration options.

New features

The /version endpoint now returns a JSON object that includes the service version, build time, and commit hash.
Restore-by-timestamp requests have been simplified: only the routine name and timestamp are required. Storage is resolved from the routine configuration, and destination/destination-name plus policy remain optional.
Added min-part-size to LocalStorage configuration to align it with cloud storage backends. This parameter specifies the minimum size of individual storage chunks in bytes.
Added on-demand backup trigger endpoints:
- POST /v1/backups/full/{name} for full backups.
- POST /v1/backups/incremental/{name} for incremental backups. Both endpoints accept an optional delay query parameter (for example, ?delay=1000) for safer, more controlled deployment workflows with minimal backup overhead. The legacy POST /v1/backups/schedule/{name} endpoint remains supported but is deprecated.
Secret Agent now supports TLS configuration via ca-file, cert-file, and key-file.

Improvements

Improved resilience of long-running backup and restore jobs during cluster reconfiguration.
Added type label (full/incremental) to aerospike_backup_service_last_successful_backup_timestamp metric to distinguish last successful backups by backup type.
Added canceled outcome to aerospike_backup_service_backup_events_total metric. The metric increments for explicit user cancellations (Cancel backup endpoint or routine disable), while graceful shutdown cancellations may appear in logs without a guaranteed scrape before shutdown completes.
Added fast-fail behavior for invalid storage configuration: asynchronous backup and restore jobs now fail immediately if the storage configuration is invalid.
Routine configurations are now immutable for the duration of a backup or restore job. Changes made during long-running operations no longer affect already running jobs.

For additional details about fixes, improvements, and maintenance in this release, see the release page on GitHub.