Skip to content

v1.0.0

Choose a tag to compare

@github-actions github-actions released this 02 Feb 09:14
· 138 commits to main since this release
2f5d98c

Release Notes

This initial release introduces absctl, the new Aerospike Backup Control command-line tool. Designed to replace legacy asbackup and asrestore, absctl consolidates backup and restore workflows into a single utility featuring native cloud support and improved operational efficiency.

Highlights

Unified CLI

  • Backup and restore consolidated into one tool: absctl backup and absctl restore.
  • YAML configuration file support for scripted and scheduled operations.
  • Structured JSON logging for log aggregation pipelines.

Improved partition-based scanning

Backups use balanced partition-based scans with configurable parallelism (--parallel) for efficient hardware utilization, ensuring minimal and balanced load across all Aerospike cluster nodes:

  • Parallel partition scanning: Configurable parallelism (1-32 workers) with intelligent partition distribution.
  • Partition filtering: Back up specific partition ranges or individual partitions.
  • Minimal cluster impact: Rate limiting (RPS and bandwidth) to prevent backup operations from affecting production workloads.
  • Resumable backups: State file support for continuing interrupted backups from the last checkpoint.

Note
Migrating from asbackup may require performance tuning of some parameters on both the Aerospike cluster and absctl.

Storage backend support

Flexible storage options for backup and restore:

  • Local disk: Direct backup to local filesystem with configurable buffer sizes.
  • Amazon S3: Full support including storage classes (Standard, Glacier, Intelligent-Tiering, etc.), multipart uploads, and MinIO compatibility via endpoint override.
  • Google Cloud Storage (GCS): Native GCP bucket integration.
  • Azure Blob Storage: Complete Azure container support with both account key and Azure Active Directory authentication.
    Cloud backups do not require intermediate local storage.

AZ-aware backup

Backup node selection to optimize network topology and reduce costs:

  • --prefer-racks: Prefer reading from specific rack IDs while backing up the entire namespace (can fall back to other racks).
  • --rack-list: Back up partitions whose master is on a node in the listed racks when the job starts (potentially partial; restore all slices for a full data set).
    --prefer-racks can reduce cross-availability-zone traffic during a full backup. --rack-list supports parallel backup sliced by rack. See Rack-aware backup: prefer-racks vs rack-list.

Additional features

  • TLS/mTLS for cluster connections.
  • AES-128/256 encryption for backup files.
  • ZSTD compression.
  • Aerospike Secret Agent integration for credential management.

Backward compatibility

  • Backup files (.asb) created by asbackup can be restored with absctl.
  • Most CLI flags preserved from legacy tools.

For migration details, see Legacy migration.