Skip to content

Aerospike Backup Service 3.2.0 release notes

July 8, 2025  |  Download

This release implements a variety of new features and improvements to enhance performance, usability, and reliability. It includes a faster version of the underlying backup library, and two breaking changes.

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

New features

  • A new endpoint GET /v1/restore/jobs has been added to retrieve a list of all restore jobs, with options to filter by time range and status.
  • The min-part-size property, previously available only for S3 storage, is now supported for both Azure and GCP storage. This property allows you to configure the minimum size of individual upload chunks.
  • ABS no longer requires root permissions to run.
  • ABS now automatically masks private keys in the logs.

Breaking changes

  • The namespaces field in a backup routine entry is now mandatory. Previously, omitting this field would default to backing up all namespaces. In this release, to back up all namespaces, you must explicitly provide an empty list (namespaces: []). This change prevents accidental backups of all namespaces if the field is forgotten.

  • The bandwidth field in the restore policy is now specified in MiB/s instead of bytes per second. The minimum value for this property is 8 MiB/s. This aligns its unit with the equivalent property in the backup policy and other Aerospike tools.

  • The partition-list default value is now null instead of 0-4095. Both values have the same effect of backing up all partitions in the cluster.

Prometheus metrics update

New metrics in this release provide enhanced monitoring of backup and restore operations:

  • aerospike_backup_service_backup_events_total: Counter for backup events, labeled by routine, type, and outcome.
  • aerospike_backup_service_backup_duration_seconds: Histogram of backup durations.
  • aerospike_backup_service_last_successful_backup_timestamp: Gauge for the timestamp of the last successful backup.
  • aerospike_backup_service_restore_in_progress: Counter for the number of restore processes currently running.

The aerospike_backup_service_restore_progress_pct metric has been removed as it created a new time series for each restore job, leading to high cardinality issues in Prometheus. You can monitor restore progress with the /v1/restore/status/{jobId} endpoint.

Feedback

Was this page helpful?

What type of feedback are you giving?

What would you like us to know?

+Capture screenshot

Can we reach out to you?