Difference between revisions of "Backup and restore"
Jump to navigation
Jump to search
old>Admin |
old>Admin |
||
Line 19: | Line 19: | ||
# Tempus Serva Server: | # Tempus Serva Server: | ||
## Run tsrsyncdump.sh (test run) | ## Run tsrsyncdump.sh (test run) | ||
## Run tsinstallcronjobs.sh (future runs) | ## Run tsinstallcronjobs.sh (future scheduled runs) | ||
# Wndows backup machine: | # Wndows backup machine: | ||
Line 25: | Line 25: | ||
## Edit the serverBackup.sh to fit your environment | ## Edit the serverBackup.sh to fit your environment | ||
## Run serverBackup.bat (test run) | ## Run serverBackup.bat (test run) | ||
## Create a scheduled job pointing to serverBackup.bat file | ## Create a scheduled job pointing to serverBackup.bat file (future scheduled runs) | ||
The service will call the tsrsyncdump.sh every 24 hours, making a dump ready for remote synchronization. | The service will call the tsrsyncdump.sh every 24 hours, making a dump ready for remote synchronization. |
Revision as of 06:54, 19 September 2012
Everything in a TempusServa installation is stored in the underlying database.
A full backup plan will only require frequent snapshots of the database.
The only exception to the all-in-the-database policy is
- Connection string for the database
- Container ressources such as SSL certficates
Depending on the amount of data stored in the database, we usually recommend using af differencial backup.
Note: The database should allways be stopped during backups, to ensure integrity of a filesystem backup.
UNIX server tools
Using the Command line tools you can set up a RSYNC differntial backup easily.
Procedure for a Windows backup server
- Tempus Serva Server:
- Run tsrsyncdump.sh (test run)
- Run tsinstallcronjobs.sh (future scheduled runs)
- Wndows backup machine:
- Install Cygwin tools
- Edit the serverBackup.sh to fit your environment
- Run serverBackup.bat (test run)
- Create a scheduled job pointing to serverBackup.bat file (future scheduled runs)
The service will call the tsrsyncdump.sh every 24 hours, making a dump ready for remote synchronization.