#!/bin/bash # This script might look like a good idea. Please be aware of these important issues: # # - The backup file is not encrypted and it contains your lightning private keys. # Consider encrypting before uploading or using another backup tool like duplicity. # - Old channel state is toxic and you can loose all your funds, if you or someone # else closes a channel based on the backup with old state - and the state changes # often! If you publish an old state (say from yesterday's backup) on chain, you # WILL LOSE ALL YOUR FUNDS IN A CHANNEL, because the counterparty will publish a # revocation key! if [ "$(id -u)" != "0" ]; then echo "This script must be run as root." echo "Use the command 'sudo su -' (include the trailing hypen) and try again" exit 1 fi (return 2>/dev/null) && sourced=1 || sourced=0 if [ $sourced != 1 ]; then echo "You forgot the leading '.' followed by a space!" echo "Try this format: . ./backup.sh" exit 1 fi if [ -z ${BACKUP_PROVIDER+x} ]; then echo "Set BACKUP_PROVIDER environmental variable and try again." exit 1 elif [ ${BACKUP_PROVIDER="Dropbox"} ]; then if [ -z ${DROPBOX_TOKEN+x} ]; then echo "Set DROPBOX_TOKEN environmental variable and try again." exit 1 fi if [ -z ${1+x} ]; then filename="backup.tar.gz" else filename=$1 fi if [ ! -d /var/lib/docker/volumes/backup_datadir ]; then docker volume create backup_datadir fi btcpay-down.sh tar --exclude='/var/lib/docker/volumes/backup_datadir/*' --exclude='/var/lib/docker/volumes/generated_bitcoin_datadir/*' --exclude='/var/lib/docker/volumes/generated_litecoin_datadir/*' -cvzf /var/lib/docker/volumes/backup_datadir/_data/${filename} /var/lib/docker/volumes btcpay-up.sh echo "Uploading to Dropbox..." docker run --name backup --env DROPBOX_TOKEN=$DROPBOX_TOKEN -v backup_datadir:/data jvandrew/btcpay-dropbox:1.0.5 $filename echo "Deleting local backup..." rm /var/lib/docker/volumes/backup_datadir/_data/${filename} fi