Safe to update via update.sh?

ThalesC

Hi, silly quetion, but I’m afraid to update my server even though it’s necessary.

TLDR: Is there any chance that after an update I can’t roll back to a working state if something brakes? Is it safe to update with --no-update-compose?

If something breaks during update, my data is/can be changed in any way? I had a huge problem (no relation to Mailcow) with Nextcloud one day, where the update changed the structure of an internal sql table (columns and data structure i guess…) and I lost all my configuration, had to install and configure everything FROM SCRATCH, and then copy all my files from a backup. Again, no relation to Mailcow, just wondering if something like this could ever happen.

Also, I’m using docker-compose version 1.29.2, is it safe to update with --no-update-compose?

Thanks in advance!

gtrdriver

as in the Documentation i only can say “Make a Backup Copy” bevore updating.
Backup Mailcow - even without hypervisor is realy simple - using the Migration howtodo in the offical Documents
Only a other linux Machine some Space and Rsync is needed ….

But i prefer to install systems like mailcow on a Hypervisor with Restore points or on a Filesystems with Snapshots like ZFS ….

Best REgards

ThalesC

gtrdriver
Yeah, I’m going to backup everything, I’m running on VMWare ESXI so I can take a snapshot of the working state.

In the case I described with Nextcloud, I had my main configuration on one VM (with snapshots), database and files on another (couldn’t snapshot due to my bad management back then ngl), and the way I did my backup didn’t work since my database got corrupted.
With Mailcow the backups will be easier to do!

Thanks for the advice!

ThalesC

Just for future reference, I did a backup on the VM with the script helper-scripts/backup_and_restore.sh, and a snapshot just to be safe, then executed sudo ./update.sh --no-update-compose without any harm, everything is working as intended!