---
title: "Legacy Aerospike restore tool (asrestore)"
description: "Learn how to use the legacy Aerospike asrestore tool to recover data from backups created with asbackup."
---

# Legacy Aerospike restore tool (asrestore)

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

`asrestore` is the legacy CLI tool for restoring backups created with `asbackup`.

::: note
`asrestore` is deprecated as of the launch of [Restore (`absctl restore`)](https://aerospike.com/docs/database/tools/backup-and-restore/absctl/restore).
:::

## Overview

`asrestore` restores backups created with `asbackup`. With the `asrestore` tool, you can restore to specific bins or sets, secure connections using username/password credentials or TLS (or both), and use configuration files to automate restore operations.

## Considerations for Aerospike restore

When using `asrestore`, be aware of the following considerations:

-   You can use `asrestore` to restore backups from Aerospike server version 3.0 or later. To restore a backup from earlier releases, contact Aerospike Support.
-   The TTL of restored keys is preserved, but the last-update-time and generation count are reset to the current time.
-   `asrestore` creates records from the backup. If records exist in the namespace on the cluster, you can configure a write policy to determine whether the backup records or the records in the namespace take precedence when using `asrestore`.
-   If a restore transaction fails, you can configure timeout options for retries.
-   Restore is cluster-configuration-agnostic. A backup can be restored to a cluster of any size and configuration. Restored data is evenly distributed among cluster nodes, regardless of cluster configuration.

## Privileges required for `asrestore`

The privileges required to run `asrestore` depend on the type of objects in the namespace.

-   If the namespace does not contain [user-defined functions](https://aerospike.com/docs/database/learn/architecture/udf) or [secondary indexes](https://aerospike.com/docs/database/learn/architecture/data-storage/secondary-index), `read-write` is the minimum necessary privilege.
    
-   If the namespace contains [user-defined functions](https://aerospike.com/docs/database/learn/architecture/udf), `udf-admin` is the minimum necessary privilege to restore UDFs for Database 6.0.0 or newer. Otherwise, use `data-admin`.
    
-   If the namespace contains [secondary indexes](https://aerospike.com/docs/database/learn/architecture/data-storage/secondary-index), `sindex-admin` is the minimum necessary privilege to restore secondary indexes for Database 6.0.0 or newer. Otherwise, use `data-admin`.
    

For more information about Aerospike’s role-based access control system, see [Configuring access control](https://aerospike.com/docs/database/manage/security/rbac/#privileges).

## Related topics

-   [Run Aerospike restore](https://aerospike.com/docs/database/tools/backup-and-restore/asrestore/use)
-   [Estimate resources for Aerospike restore](https://aerospike.com/docs/database/tools/backup-and-restore/asrestore/resources)
-   [Restore data from Amazon S3](https://aerospike.com/docs/database/tools/backup-and-restore/asrestore/s3)
-   [Validate backup files with asrestore](https://aerospike.com/docs/database/tools/backup-and-restore/asrestore/validate)
-   [Secret usage with backup and restore](https://aerospike.com/docs/database/tools/backup-and-restore/asbackup/secrets)