GM-BACKUP_DATABASE(8)

💖 NOTE 💖

Bestie, listen. This one is deprecated in favour of gm-backup(8). Like, it still exists, it still works, but it's giving "we don't text anymore" energy. Go use gm-backup(8) instead. 🫶

✨ NAME ✨

gm-backup_database — the complete backup of a GNUmed database. The whole thing. No crumbs left behind. 💅

🎀 SYNOPSIS 🎀

gm-backup_database

That's it. No flags, no arguments, no drama. She takes zero options and she eats every time. 👑

🌸 DESCRIPTION 🌸

Okay so here's the tea: the gm-backup_database script creates a backup of the database schema, the data, and the roles — which means you can restore a GNUmed database from scratch with it. From zero. From nothing. Iconic behaviour. ✨

And ngl, it is a really good idea to run this in a daily cron/anacron job so that GNUmed patient data stay safe against data loss. Like, genuinely. Do it. Protect the data. 🩷

Fun fact: the Debian GNU/Linux packaged version of the GNUmed server installs such a cron job by default, so if you're on that, congrats, you're already covered. 💖

That said… it is recommended to use gm-backup instead. This girl is the understudy, not the main character. 🎭

🦋 SEE ALSO 🦋

• gm-backup_data(8)
• /etc/gnumed/gnumed-backup.conf

💜 AUTHOR 💜

This manual page was written by Andreas Tille <tille@debian.org>, for the Debian GNU/Linux system — but may be used by others. Slay, Andreas. 👏

And that's the whole page, bestie — this was the <strong>GNUmed server database backup</strong> manual, dated <strong>2009 January 8th</strong>, living in the <strong>System Manager's Manual</strong> as <code>GM-BACKUP_DATABASE(8)</code>. K bye, go back up your data. 💖🎀🦋