Skip to content

Latest commit

 

History

History
110 lines (75 loc) · 3.43 KB

how-restore-backup.md

File metadata and controls

110 lines (75 loc) · 3.43 KB
Raw

How restore a Talkyard backup

If your server suddenly disappears, then, to restore a backup on a new server, you can do as follows.

Start installing Talkyard on that new server, following the instructions in https://github.com/debiki/talkyard-prod-one/blob/master/README.md — but stop at step 8: "Edit config values". Instead, we'll copy config files from the backup:

On the new server, as root, run the commands below:

Replace BACKUP_ARCHIVES_DIR and DB_BACKUP_FILE etcetera below, with the actual path and file names.

sudo -i # become root
cd /opt/talkyard

echo "$(date -I): Restoring backup ..." >> talkyard-maint.log


# Restore config files and HTTPS certs
# ------------------------------

# First, let's "backup" the new conf, in case you'd like to diff old vs default.
mkdir -p default-conf/data
mv  conf  docker-compose.*  .env  default-conf/
mv  data/certbot  data/sites-enabled-auto-gen  default-conf/data/

# Then restore the old config.
mkdir old-conf
mkdir data
tar xf /BACKUP_ARCHIVES_DIR/CONFIG_BACKUP_FILE.tar.gz -C old-conf
mv old-conf/.env                        ./
mv old-conf/docker-compose.*            ./
mv old-conf/conf                        ./conf
mv old-conf/data/certbot                data/certbot
mv old-conf/data/sites-enabled-auto-gen data/sites-enabled-auto-gen


# Stop any App server
# ------------------------------

# This shouldn't be needed — you didn't start the Talkyard server yet?
# You stopped at step 8 as mentioned above?
# Anyway, if the Talkyard app server is running, stop it:
# (Otherwise the restore will fail because of active database connections.)
docker-compose stop app


# Restore the database, PostgreSQL
# ------------------------------

# First, start PostgreSQL.
docker-compose up -d rdb

# NOTE: Overwrites any existing database (!).
zcat /BACKUP_ARCHIVES_DIR/DB_BACKUP_FILE.sql.gz \
    | docker exec -i $(docker-compose ps -q rdb) psql postgres postgres \
    | tee -a talkyard-maint.log


# Restore Redis?
# ------------------------------

# Not needed, it's a cache. (Maybe write something about Redis later.)


# Restore uploaded files
# ------------------------------

rsync -a  /BACKUP_ARCHIVES_DIR/UPLOADS_BACKUP_DIR.d/  /opt/talkyard/data/uploads/

Memory

Next, configure memory: Run free -m to find out how many megabytes memory your machine has. Look at docker-compose.override.yml to see how much memory Talkyard has been configure to use — and optionally, replace that file with another more suitable one from ./mem/*, e.g.: cp mem/2g.yml docker-compose.override.yml.

Start Talkyard

Now, time to start everything:

docker-compose up -d
docker-compose logs -f --tail 999

Also, think about if you need to 1) update your DNS server with the IP address to your new Talkyard server. Or maybe 2) change the hostname of the Talkyard server — you'd then edit Nginx config in conf/play-framework.conf, and conf/sites-enabled-manual/ or data/sites-enabled-auto-gen/, plus generate a LetsEncrypt cert (see: https://github.com/debiki/talkyard-prod-one/blob/master/docs/setup-https.md).

Backups and automatic upgrades

Continue with step 9 in the installation instructions in README.md, https://github.com/debiki/talkyard-prod-one/blob/master/README.md, that is, this step: "Schedule deletion of old log files, daily backups and deletion old backups, and automatic upgrades".

Also, look at the Next steps just below, in README.md — you'll want to configure off-site backups?