evergreen-admin:maintenance:backups
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
evergreen-admin:maintenance:backups [2008/06/28 22:47] – Improve example backup and restore commands dbs | evergreen-admin:maintenance:backups [2012/09/27 14:22] (current) – removed dbs | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ======Backing up your Evergreen system====== | ||
- | To back up your Evergreen system, you have to consider three major categories of volatile data: | ||
- | - Data stored in Evergreen' | ||
- | - Customizations to Evergreen (themes, skins, configuration files, staff client) | ||
- | - The operating system itself | ||
- | |||
- | You should follow the principles of good system administration and ensure that you store your backups on separate machines (ideally with some backups stored offsite), regularly check your backup and restore procedures, ensure that the backups are only accessible by authorized personnel, etc. Such a discussion is beyond the scope of this documentation; | ||
- | |||
- | |||
- | =====Backing up the Evergreen database===== | ||
- | Most of the critical data for an Evergreen system -- patrons, bibliographic records, holdings, transactions, | ||
- | # pg_dump -U < | ||
- | pg_dump -U evergreen -h localhost -f evergreen_db.backup.2008-06-15 evergreen | ||
- | </ | ||
- | To restore the backed up database into a new database, create a new database using the '' | ||
- | createdb -T template0 -E UTF8 -U evergreen -h localhost new_evergreen | ||
- | psql -U evergreen -h localhost -f evergreen_db.backup.2008-06-15 new_evergreen | ||
- | </ | ||
- | Note that this method of backup is only suitable for small Evergreen instances. Larger sites should consider implementing continuous archiving (also known as "log shipping" | ||
- | |||
- | =====Customizations to Evergreen configuration files===== | ||
- | When you deploy Evergreen, you have to customize a number of files: from setting authentication information in '' | ||
- | |||
- | There are a number of ways of tackling this problem. You could create a script that regularly creates a time-stamped tarball of all of these files and copies it to a remote server - but that would build up over time to hundreds of files. You could use '' | ||
- | |||
- | Perhaps one of the best options is to use a version control system like [[http:// | ||
- | |||
- | =====Full system backups===== | ||
- | A full system backup archives every file on the file system. Some basic methods require you to shut down most system processes; other methods can use mirrored RAID setups or SAN storage to take " |
evergreen-admin/maintenance/backups.1214707679.txt.gz · Last modified: 2022/02/10 13:33 (external edit)