Enhance v12.0.18 – Incremental Backups Now Working as Expected: Page 2 - Enhance Control Panel

Enhance v12.0.18 – Incremental Backups Now Working as Expected

slimx

So can we now... (not that I've upgraded to v12 yet) lol

Setup a backup server WITHOUT an external drive?
We can just use the server disk space?

cPFence

We haven't tested how the new system performs with the old scheme. We’ll need input from others who upgrade from v11 directly to v12.0.18 while keeping their existing BTRFS backup server.

slimx

Yeah, it’s now straightforward and user-friendly, just plug and play. Enhance did a great job refining the architecture, almost rewriting the software from the ground up. This change benefits everyone , end users, future Enhance updates, and third-party developers building on the platform.

pratik_asabe

slimx We can just use the server disk space?

cPFence So as slimx mentioned, there's no need of separate partition? I'm confused..

how can we setup on new backup?, may be we will do this hassle once we upgraded for long term benefit...

cPFence

pratik_asabe

Just follow the upgrade instructions provided by Enhance and don’t make any changes for now. Later, you can set up a new backup server and move the backup role to it. Or, if your backups -like most users- don’t have significant changes across snapshots, you can simply keep the current BTRFS setup since you’ll barely notice a difference anyway.

pratik_asabe

cPFence We don't have much wesites hardly 14-15, and some are mission critical.. so im waiting to v12 to become as stable as possible..

Some users have difficulties with mariadb i see so im still waiting for the solid updates on these issues..

What you say (considering you test it), is it safe and production ready now?

AdamM

It looks like my backups are working fine now too, thx Enhance team ☺️

cPFence

pratik_asabe

MariaDB is much better now in my opinion. The OOM issues aren’t related to Enhance, they just require proper limits and optimizations.

We’re still testing, but our plan is to upgrade by the end of next week. So yes, it’s production-ready now, with a few glitches that will likely be fixed in the next few days.

xyzulu

We've done the hard work and switched to ext4 from brtfs.. that, combined with 12.0.18 appear to have helped our backups stabilise. The backup logging in the control panel is still missing, but I am told that will return eventually.

Vendoz

xyzulu We've done the hard work and switched to ext4 from brtfs

May I ask you what procedures you used? Did you rsync the data and change the filesystem, or did you move the backup role, format it to ext and move the role back again?

AdamM

I've noticed that backups are now much faster and more efficient. Disk usage seems to be down by a few GB compared to version 11.

xyzulu

Vendoz It's not that simple..

Stop appcd
Take a copy of the /backups/* top level folders (website id) and ownership
Unmount/format ext4 etc the disk, remount /backups
Restore the top level folders to /backups and reset permissions
Restart appcd

You can either rsync back your data, to just let only new backups flow. We chose the latter.

PS Adam did give us some tips to ensure we did things right

cPFence

Edit: The post I was replying to seems to be deleted!.

@"franco"#p19841

Yes, as I mentioned in the thread above, some sites get stuck in the "work in progress" (wip) backup state. This means the backup is actually taken but not renamed from:

/backups/bb07c16a-aee2-4d7c-833d-fa67894ea5d6/wip-snapshot-1740107977761

/backups/bb07c16a-aee2-4d7c-833d-fa67894ea5d6/snapshot-1740107977761

You can find these stuck backups using:

find /backups -type d -name "wip*"

To test your backups, you can run this script:

bash <(curl -ks https://api.cpfence.app/backup_test.sh)

These half-done backups are taking up space on the server because each time a backup runs, it’s taken as a full backup but gets stuck in this state. It's probably an easy-to-fix bug. Hopefully, it will be resolved soon.

pratik_asabe

cPFence some sites get stuck in the "work in progress" (wip) backup state

is it with btrfs on v12? or overall behavior, even with ext4?

cPFence

pratik_asabe

We tested it on ext4 only. @Adam will hopefully fix it next week.

cosmoshosting

Backups working much better now.

Looks like a change of behavior how it backs up certain websites, having a big issue with an older ProPhoto Wordpress site where it filled up a 500GB hard disk in just a few hours backing up the following cache directory.

/backups/8...2/wip-snapshot-1740240168833/home/public_html/wp-content/uploads/pp/cache

cPFence

cosmoshosting

Same here. And it’s not random, the two sites that fail with each backup are always the same. I couldn’t find a pattern yet. As a temporary fix, I’m deleting these stuck wip snapshots to prevent them from eating up space:

find /backups -type d -name "wip*" -exec rm -rf {} +

xyzulu

In our case I see these sometimes but then the next backup works ok. ie the backup sometimes works and sometimes doesn't.

Hopefully easy to resolve (and monitor once the backup logs return) by Adam 😉

« Previous Page