Aerospike restore (asrestore)
This page describes the features and benefits of the Aerospike restore tool, (asrestore).
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
asrestoreto 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.
asrestorecreates 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 usingasrestore.- 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 or secondary indexes,
read-writeis the minimum necessary privilege.If the namespace contains user-defined functions,
udf-adminis the minimum necessary privilege to restore UDFs for Database 6.0 or newer. Otherwise, usedata-admin.If the namespace contains secondary indexes,
sindex-adminis the minimum necessary privilege to restore secondary indexes for Database 6.0 or newer. Otherwise, usedata-admin.
For more information about Aerospike's role-based access control system, see Configuring Access Control in EE and FE.