Pause images optimization upon restore to new instance of server

Product Support
5

Thanks for helping.

Yes but for straightforward restore using web gui and expected procedure you need +4x free size of your backup file.

Here is how:

  1. Upload backup file (or rsync into /var/discourse/shared/standalone/backups/default)
  2. Once when restore is initialized backup file.gz is copied to /var/discourse/shared/standalone/tmp/restores/
  3. During restore backup file in /var/discourse/shared/standalone/tmp/restores/ folder is unpacked
  4. From tmp folder uploads are rsync to native place and sql dump being inserted to pg database.

How I managed to success restore.

During restore process once when discource copied file from restore folder to temp i did delete original backup file uploaded to over ssh.

Once again when discource finished with sql inserts and stat rsync unpacked files from tmp folder to /var/discourse/shared/standalone/uploads/ I manually deleted bakupxxx.tar.gz file in temp folder over ssh without interrupting the process of restore.

Once when my instance was online and rsync finished I did

rm -rf /var/discourse/shared/standalone/tmp/restores/default/*

If you backup large restore process my seems death and instance over web start returning error code 500 (happened to me twice) you can check restore process by entering into app

cd /var/discourse
./launcher enter app

ps aux | grep restore

Also since my db restore was too long

cd /var/discourse
./launcher enter app
watch -n 10 “sudo -u postgres psql discourse -c "SELECT now(), state, query FROM pg_stat_activity WHERE state != ‘idle’;"”

Helped me to monitor db restore progress, to see that is restore is still alive.