---
title: "Aerospike Backup Service 3.4.0 release notes"
description: "Aerospike Backup Service 3.4.0 release notes featuring rack-aware backups and configuration updates."
---

# Aerospike Backup Service 3.4.0 release notes

> For the complete documentation index see: [llms.txt](https://aerospike.com/docs/llms.txt)
> 
> All documentation pages available in markdown.

November 5, 2025  |  **[Download](https://aerospike.com/download/backupservice/backup_service)**

This release delivers bug fixes and incremental improvements based on customer feedback. The primary addition is rack‑aware backups.

## Breaking changes

-   The `prefer-racks` configuration field has moved from the [`backup-routines`](https://aerospike.com/docs/database/tools/backup-and-restore/backup-service/config-examples#backup-routines) section to the [`aerospike-clusters`](https://aerospike.com/docs/database/tools/backup-and-restore/backup-service/config-examples#aerospike-clusters) section of the configuration file.

## New features

-   A new `rack-list` field has been added to [`backup-routines`](https://aerospike.com/docs/database/tools/backup-and-restore/backup-service/config-examples#rack-list). It backs up partitions whose master is on a node in the listed racks when the job starts. This field is mutually exclusive with `node-list` and `partition-list`, and with cluster-level `prefer-racks`. `prefer-racks` still backs up the entire namespace and only affects which replica is read per partition. See [Rack-aware backup: prefer-racks vs rack-list](https://aerospike.com/docs/database/tools/backup-and-restore/backup-service/config-examples#rack-aware-backup-prefer-racks-vs-rack-list).
    
-   A new optional `timestamp-format` field is available in the [`service.backup`](https://aerospike.com/docs/database/tools/backup-and-restore/backup-service/config#service.backup) configuration section.
    
-   The [`backup-policies`](https://aerospike.com/docs/database/tools/backup-and-restore/backup-service/config-examples#backup-policies) section adds two optional fields:
    
    -   `max-concurrent-nodes` — Maximum number of concurrent requests to server nodes. Default: issue requests to all nodes in parallel.
    -   `use-scan-compression` — Enables built‑in compression during scan operations (Aerospike Server Enterprise Edition only). Both fields are optional; they do not change functionality but may affect performance.

For additional details about fixes, improvements, and maintenance in this release, see the [release page on GitHub](https://github.com/aerospike/aerospike-backup-service/releases/tag/v3.4.0).