Difference between revisions of "Backup and restore"

From TempusServa wiki
Jump to navigation Jump to search
old>Admin
old>Admin
Line 10: Line 10:


Note: The database should allways be stopped during backups, to ensure integrity of a filesystem 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 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
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

  1. Tempus Serva Server:
    1. Run tsrsyncdump.sh (test run)
    2. Run tsinstallcronjobs.sh (future runs)
  1. Wndows backup machine:
    1. Install Cygwin tools
    2. Edit the serverBackup.sh to fit your environment
    3. Run serverBackup.bat (test run)
    4. Create a scheduled job pointing to serverBackup.bat file

The service will call the tsrsyncdump.sh every 24 hours, making a dump ready for remote synchronization.