Difference between revisions of "Server maintenence"
Jump to navigation
Jump to search
old>Admin |
old>Admin |
||
| Line 5: | Line 5: | ||
Backups should optimally be done either by dumping the database. Alternatively the database can be stopped (important) and data folders can be backed up normally. | Backups should optimally be done either by dumping the database. Alternatively the database can be stopped (important) and data folders can be backed up normally. | ||
The | The following guide contains directions for setting up incremental backups to remote location, using [http://rsync.samba.org/ rsync] and SSH connections. | ||
http://tempusserva.dk/mediawiki/index.php?title=Backup_and_restore | |||
=== Table naming conventions === | === Table naming conventions === | ||
Revision as of 17:53, 12 February 2013
Backup and restore
TS has inbuilt manual functions on the solution level, but measures have to taken to back the data IN the solutions.
Backups should optimally be done either by dumping the database. Alternatively the database can be stopped (important) and data folders can be backed up normally.
The following guide contains directions for setting up incremental backups to remote location, using rsync and SSH connections. http://tempusserva.dk/mediawiki/index.php?title=Backup_and_restore
Table naming conventions
Every solution has its own table namespace of "data_" followed by the system solution name.
Example for the solution named XXX:
- data_XXX
Other related tables include
- data_XXX_file
- data_XXX_mail
- data_XXX_comment
- data_XXX_contact
- data_XXX_measure
- data_XXX_member
- data_XXX_t_YYY
- data_XXX_accesslog
- data_XXX_statuslog
- data_XXX_revisionlog
Deleted tables are prefixed by a timestamp