Backup einer EGroupware
EGroupware should be backed up regularly, at the latest in live operation!
A comprehensive backup consists of three steps:
1. the internal EGroupware data backup should be configured,
2. the data directory be backed up,
3. and the installation itself/the VM are backed up.
To 1.: internal EGroupware database backup.
The database data backup is available under
Admin/Admin/DB Backup and restore
to configure:
Multiple data backup plans can be created. Thus, in larger environments with many data changes, multiple data backups daily are recommended.
Backing up the file manager files via these backups is only recommended if few files are saved in the file manager. Avatar images are also backed up in this way.
This method is not suitable for larger amounts of data. In case of doubt, you have to try it out to see if it works in your specific case.
It is essential to limit the number of data backups created!
Otherwise there is a risk that the hard disk will fill up.
The created data backups can now be exported, restored, deleted or renamed.
Renaming prevents automatic deletion. This allows you to keep certain statuses for longer.
This mask is also available in the setup.
The backup files are stored under
/var/lib/egroupware/default/backup
(for the default instance).
This directory can also be mounted in the virtual file system. This means it is also available there via WebDAV, for example, or you can access the backup files via the EGroupware file manager.
For a migration from EGroupware to another/new server, it is sufficient to copy this directory (via ssh ) and restore the database backup.
Thus, this directory will also be backed up in point 2:
To 2: Back up data directory.
At
/var/lib/egroupware
are all directories with EGroupware data including the database backup files. This directory should be considered externally by a data backup software in the backup plan and thus be backed up.
To 3.: Back up system/VM
EGroupware installations are usually relatively small. An installation with Collabora Online is less than 10GB. Thus, a VM can be kept small and can also be backed up (at night) via snapshot backup during operation. Depending on what the virtualisation solution offers.
For questions, suggestions etc. please create a separate topic in the forum and refer to this article.
