Backing up and Restoring a Node Database

The following procedure describes how to back up and restore the entire Redis database of a node, which includes node users, their access keys, and transfer history. If your transfer server is an Aspera on Cloud node, migrate Aspera on Cloud data from one node to another by backing up the Redis database on the original node and restoring the database on a new node.

If you only need to back up and restore node usernames and passwords (the node user database), use asnodeadmin commands; see Backing up and Restoring the Node User Database Records. If you also want to back up and restore access keys, see Backing up and Restoring Access Keys (Tenant Data).

These instructions assume that the node is using the default port for the Redis database, port 31415. If your deployment uses a different port for Redis, substitute it in the commands accordingly.

Verify that the original node and new node are running the same version of Aspera software.
Run ascp -A on a command line to view the Aspera product and version.
On the original node, back up the database.
Stop the Aspera NodeD service and create the backup file by running the following commands:
```
# systemctl stop asperanoded
# /opt/aspera/bin/asredis -p 31415 BGREWRITEAOF
```
The backup is stored as appendonly.aof in the following location:
```
/opt/aspera/var/appendonly.aof
```
If migrating the database, move the appendonly.aof to the same location on the new node.
On the new node, stop the Aspera NodeD service.
Stop the Aspera NodeD service by running the following command:
```
# systemctl stop asperanoded
```
Flush existing data from the Redis database on the new node.
```
#/opt/aspera/bin/asredis -p 31415 FLUSHALL
```

Load the backup database file into the new node database.

# cat appendonly.aof | /opt/aspera/bin/asredis --pipe -p 31415

On both nodes, restart the Aspera NodeD service.
Start the Aspera NodeD service by running the following command:
```
# systemctl start asperanoded
```
In Files, confirm that the hostname matches the DNS entry for the new node.
To view the node URL, go to Admin View > Nodes & Storage.
Confirm the database restoration succeeded.
Run the following command to the original and new nodes. If the database restoration succeeded, the output from each is identical.
```
# curl -ki -u {node_username:node_password} http[s]://{hostname}:{http_port}access_keys
```
Note: Curl is included in many Unix-based operating systems. To check if it is installed, enter curl on the command line. If it is not installed, download it from the Curl website: https://curl.haxx.se/download.html.