SharedGrid Yes, this not help. Ticket created.
Enhance v12.0.0 Released 🎉
AdamM hopefully you get sorted soon.
- Edited
Update: Okay pushing staging site to live seems to work now i guess? Maybe i did something wrong.
But other issue still exist when pushing staging site to live on existing site making a back-up and restoring it doesn't work anymore on that site. This also happens when you delete the existing site and push the staging to a new site.
Normal backup/restore on sites that didn't come from staging stage does still work.
Edit: Made a ticket for this
We tested the new backup system in v12.0.16 today and noticed inconsistencies with how backups are being taken. Specifically, incremental backups don’t always work as expected, it’s hit or miss, and we haven’t been able to identify a clear pattern.
Upon further investigation, we found that the new Enhance backup system is sometimes creating full copies of files instead of using hard links for unchanged files. We checked the inodes of identical files across multiple snapshots for a test WordPress site (with no changes made), and the results showed that most snapshots had different inodes for the same files. This confirms that in many cases, files are being fully copied instead of hard-linked, leading to higher disk usage than expected.
We’ve seen this behavior for both automated and manual backups, though occasionally, a snapshot will correctly use hard links. It seems inconsistent.
It happens to me (in a new installation from scratch) that the backups are saved and I can restore them, but if I try to change to another backup server I get an error and the copies become unusable...
cPFence Yes, I have reported some of this to Enhance via a ticket as well. I'm sure they will sort it out. I am thinking about resetting the backups.. ie set retention to 1 day.. let them all delete and then see if things look better after that.
Side point, now backing up your backups requires copying/syncing etc the 'current' folder... which is a symlink, so needs rsync -L (if using rsync). I'm currently testing the best way to backup my backups to another server.
- Edited
xyzulu I did this, doesn't seem to work any better. (set to 1 day and let them age out)
cPFence
Did you have a separate mail server in your test setup? See my earlier post: https://community.enhance.com/d/2415-enhance-v1200-released/343
This was confirmed by Adam and they are working on a fix.
Yeah, we’ll probably write a new script for backing up the backups and share it with the community since the old BTRFS script we shared earlier is no longer useful for v12 users.
No, we don’t have an email-only server, and we tested it on an ext4 setup, not BTRFS. I’m sure the Enhance team will fix this backup issue soon.
cPFence Yeah, we’ll probably write a new script for backing up the backups and share it with the community since the old BTRFS script we shared earlier is no longer useful for v12 users.
I think you will want to use rsync.. we have the working now on v12 backups. It's a little messy (--include, --exclude etc) but it's working for us now.
- Edited
v12 upgrade note (I have opened a ticket): There are a number of logs/large files in /var/local/enhance that should be removed (in my opinion) after the upgrade. Perhaps this was already planned? In any case, until we can move the control panel role (waiting for documentation) keep an eye on your control server disk space.
Edit: I've had a reply to my ticket.. not as much of a concern as I thought.. but still, there is still logs files in there that are not needed (if space is an issue for you).
It’s a must if you want to handle the hard links properly. Also, no need to bother with excludes, just mirror the full backups folder using the command above, and you’re good to go.
At least there’s a positive side to moving away from Btrfs, backing up the backups is now much easier and more straightforward.
- Edited
cPFence it’s still a bit of a mess (disk usage, leftovers from btrfs etc).. but perhaps once the backup bugs are sorted it will be a little more straightforward.
PS our backup of the backups might be different to your use case. We’re seeing only copying the ‘current’ folder using -L as being suitable to our needs. But, we will continue to explore our options.
Screenshots working for others? They are not working for me. I have reported it as a bug.