What do I have to backup with an EGroupware update?
Before a system update or even just EGroupware update, the EGroupware system should be backed up.
If it is not possible to back up the entire system as images or VM backup, at least the relevant data should be backed up:
/etc/egroupware-collabora-key #when installed
/etc/egroupware-guacamole #when installed
/etc/egroupware-rocketchat #if installed
/var/lib/egroupware #files, EGroupware backups, header.inc.php, system passwords, app data
A current EGroupware backup (incl. database backup) should be created via EGroupware and thus also included in the backup (see above).
In principle, a daily backup should be made. Including the EGroupware data to an external system!
From time to time new configuration files are delivered by the maintainers of a software. This happens for example with web servers, Postfix and others. This is also the case with EGroupware. Package managers ask whether they should replace a configuration file that has been changed by the user. One should have the difference displayed and then decide. In case of doubt, do not overwrite the file for the time being and check again afterwards and manually apply the changes made to the file by the maintainer.
Administration tools like Webmin do not ask when an update is performed, but answer the package manager’s question with Y (overwrite). This can lead to a broken system!
ALWAYS install EGroupware package updates on the console!