Isn’t just 1 backup a day too risky? If something happens to the server and the last backup happened yesterday, what do I do? Users registered between yesterday and today, are they no longer registered? I think it is better to make backups more frequent, perhaps every hour. But in case, you have to …

[이미지] yhh9xdq7d: The backup that is done daily through the settings, does the backup only of the database? Settings live in the database. [이미지] yhh9xdq7d: The database is the only thing you need to restore everything right? Technically you also want to backup the uploads folder and th…

+1 for this, again. Discourse is the only dynamic system where one can automatize backup of database only once a day.

I don’t expect this to change in core anytime soon. The I have had conversations about changing the default to more than once a week and that’s not happening. I think what might be good is a plugin that would add a site setting to make database-only backups in some number of hours (there is no reas…

If you need a better disaster recovery, I recommend following Running Discourse with a separate PostgreSQL server and running PostgreSQL on your own where you can control the exact high availability you need, like live sync replicas, point-in-time recovery and more frequent backups.

May I ask reason for this policy, is it techinal or more class wanting? 24 hours gap between backups is quite critical issue on high traffic forums. Or is this something you offer only to paying customers?

Does running Discourse with a separate PostgreSQL server reduce speed by being on a different server?

[이미지] Falco: running PostgreSQL on your own Sure, that is one solution. Quite rare solution among apps, though. In PHP/MySQL-world backuping database using cron would be really easy to do, but again - in that world every app can do it by themselves, with or without some plugin. Yes, I’m a li…

[이미지] Jagster: In PHP/MySQL-world backuping database using cron would be really easy to do You can setup PostgreSQL backups with cron too. Nothing different here. [이미지] yhh9xdq7d: Does running Discourse with a separate PostgreSQL server reduce speed by being on a different server? Not…

I only ask you two questions to understand better. The database is the only thing you need to restore everything right? The backup that is done daily through the settings, does the backup only of the database? Should the forum be in read-only mode when making the backup to the database? Or can it …

So assuming I have the database on a separate server and do backups to that database every hour. If I also backup, from the settings in the admin panel, only the files including the app.yml file and the uploads folder would be included in the backup, but not the database right? @Falco

The backup will include the database and the uploads (if they are not on S3). app.yml is not in the backup, as Discourse cannot read it. What I recommend for most people is having the backups on S3 and app.yml somewhere that you can get it if there is an emergency. Then you can build a new containe…

하루 여러 번 백업

지원

Jagster (Jakke Flemming) 12월 13, 2021, 1:45오후 2

다시 한번 이 의견에 동의합니다. Discourse는 하루에 한 번만 데이터베이스 백업을 자동화할 수 있는 유일한 동적 시스템입니다.

글		댓글	조회수
Backup and Restoration Planning Support backups	7	296	1월 20, 2025
Multiple backup schedules Feature	14	1332	4월 13, 2022
Can I backup multiple times a day, and are they safe if the server goes down Self-hosting backups	16	667	3월 13, 2024
Is daily backups enough? Support backups	8	328	12월 29, 2025
How to take backup of Discourse hourly in a day Self-hosting backups	12	2693	9월 10, 2018

하루 여러 번 백업

Related topics