Behavior:
When you MySQL database grows quite large (10-20 GB or more), you want to schedule the backups to be as efficient as possible in the case of needing to restore.
The most common method of dumping the MySQL databases with the MySQL Administrator tool is to combine all DocuWare databases in to one dump file. This can create problems with very large dump files as it not only takes a very long time to restore, but if the file becomes corrupt it may be impossible to restore anything from the file
.
Solution:
The recommended method is to backup each DocuWare database in to its own dump file. Since this can be sheduled the set up only needs to be done once. With extremely large DWDATA databases it may also be beneficial to split that database in to 2 or more backups as well.
Consider backing up DWSYSTEM, DWWORKFLOWENGINE, and DWDATA databases as individual backups.
The other DocuWare databases can be combined in to one backup.
Don't forget to periodically analyse the backups to ensure their integrity.
Vistas:
Este artículo es válido para las versiones de DocuWare: 6 6.1 6.5 6.6 6.7 6.8 6.9 6.10 6.11 6.12 7 | database mysql mysqlbackup backup #FAQID_4905