How to backup Discourse when The backup has failed?

[neounix (Dark Matter)]

@pauln

Yes, I will be moving to NEW VPS but I am trying to make a backup first before moving to new host.

Yes, I know. You are doing the right thing and a good job.

Let’s try a different strategy.

Can you make a backup successfully without including the uploads?

If so, we can simply take(1) that backup and (2) a separate tar of the uploads directory and accomplish what you want.

So, please try to just do a backup without the uploads (the middle button below); by selecting that option in the backup window; and post back.

If that fails, we will try to do the database backup manually from the command line which is easy enough and will work, I’m fairly certain (we do this all the time and rarely restore from the UX).

Reference:

Advanced, manual method of manually creating and restoring Discourse backups

As discussed below, a warning for newbies: this is an advanced method! there is an automated, web UI way to restore from backups at /admin/backups which is so much easier. with the method below, no automatic backup is kept of the /var/discourse/containers/app.yml file which contains essential SMTP credentials and SSL customizations. Keep a copy of this offsite whenever you change it. If you are using digital ocean, keep frequent snapshots of your droplets - preferably before each time you run .…

---

Note:

Whatever you decide to do @pauln, please do not destroy your existing VPS running Debian 7.5 and Discourse until you have successfully installed another instance of Discourse (and restored and tested) on your new VPS.