While there are not currently snapshots available for the node db, you can move your casper-node to another machine (physical or cloud-based like AWS). There are two primary methods of moving your node to a new machine:

Method One

1. Stop the node.
2. Copy all data.
3. Change the mountpoint.
4. Start the node.

Method Two

1. Create another node in parallel.
2. Once it is up to date, stop the nodes.
3. Swap the associated keys.
4. Restart the new node.

Note: Use the following command to copy your node's data:

rsync -av --inplace --sparse  /var/lib/casper/ /new_mount

Method Two is the safer option, limiting downtime and enabling a smooth transition from old to new nodes, as the node stays in sync with the tip of the chain, vs having to pause to download any blocks generated after the node was stopped.

Set-up/Preparation

Create two nodes and key sets. We will call these val and backup .

Copy both keys to /etc/casper/validator_keys/ under val or backup directories.

/etc/casper/validator_keys/
├── public_key.pem
├── public_key_hex
├── secret_key.pem
├── backup
│   ├── public_key.pem
│   ├── public_key_hex
│   └── secret_key.pem
└── val
|   ├── public_key.pem
|   ├── public_key_hex
|   └── secret_key.pem

This allows going into val or backup and doing a sudo -u casper cp * ../ to "enable" that node to be that key.

Sync both nodes to tip. Keep actively validating node running with the original/validator keyset.

Swapping the nodes

On the current validator (future backup):

sudo systemctl stop casper-node-launcher
cd /etc/casper/validator_keys/backup
sudo -u casper cp * ../

On the current backup (future validator):

sudo systemctl stop casper-node-launcher
cd /etc/casper/validator_keys/val
sudo -u casper cp * ../
sudo systemctl start casper-node-launcher

Back on the old validator (new backup):

sudo systemctl start casper-node-launcher