Man page - gm-backup_database(8)
Packages contas this manual
- gm-restore(8)
- gm-backup(8)
- gm-set_gm-dbo_password(8)
- gm-fingerprint_db(8)
- gm-remove_person(1)
- gm-fixup_server(8)
- gm-restore_database(8)
- gm-upgrade_server(8)
- gm-dump_schema(8)
- gm-adjust_db_settings(8)
- gm-bootstrap_server(8)
- gm-backup_database(8)
- gm-restore_data(8)
- gm-backup_data(8)
- gm-zip+sign_backups(8)
- gm-move_backups_offsite(8)
Package: gnumed-server
apt-get install gnumed-server
apt-get install gnumed-server
Manuals in package:
Documentations in package:
Manual
| GM-BACKUP_DATABASE(8) | System Manager's Manual | GM-BACKUP_DATABASE(8) |
NOTE
Deprecated in favour of gm-backup(8).
NAME
gm-backup_database - complete backup of GNUmed database
SYNOPSIS
gm-backup_database
DESCRIPTION
The gm-backup_database script creates a backup of the database schema, data, and roles which can be used to restore a GNUmed database from scratch.
It is a really good idea to use it in a daily cron/anacron job to ensure that GNUmed patient data are safe against data loss. The Debian GNU/Linux packaged version of the GNUmed server installs such a cron job by default.
It is recommended to use gm-backup instead.
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).
| 2009 January 8th | GNUmed server database backup |