Difference between revisions of "Backup and restore"
Jump to navigation
Jump to search
old>Admin (Created page with 'Everything in a TempusServa installation is stored in the underlying database. A full backup plan will only require frequent snapshots of the database. Depending on the amount o…') |
old>Admin |
||
| Line 1: | Line 1: | ||
Everything in a TempusServa installation is stored in the underlying database. | Everything in a TempusServa installation is stored in the underlying database. | ||
A full backup plan will only require frequent snapshots of the database. Depending on the amount of data stored in the database, we usually recommend using af differencial backup. | 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. | Note: The database should allways be stopped during backups, to ensure integrity of a filesystem backup. | ||
Revision as of 17:28, 18 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.