Following on from a closed topic, I took a look at the referenced repository and did a simple search and replace to reflect the changes between VestaCP and HestiaCP. Following the instructions to step 4 (I skipped myduper) and everythign has been working well. I also performed 2 restores which worked too.
Note, I haven’t done testing beyond this however having read through the entire project I don’t believe issues are likely. For me this was enough to disable the built in backup by disabling the cron job in HestiaCP.
I prefer Borg backups because they allow me to backup more regularly, even hourly and restore any backup without the drive space expense of having 24 additional copies on the filesystem every day - Borg only saves the changes and also de-duplicates.
I’d love this BORG integration, I think @falzo is big fan of Borg too so he can chime in with ideas.
I spent some time earlier trying to setup Borg and Restic but missed on a few logics and then did not really get time to look into it because of the sheer ‘manual’ work it all needs.
I do want to have some kind of reliable ‘incremental’ and ‘differential’ backup mechanism, it helps a lot on bigger sites and on NVMe Servers where storage is premium.
Feel free to connect with me personally, we can try to figure out a few things.
I have read the documentation thoroughly. I think that this feature should substitute Hestia’s backup system in the future and at least it should be supported.
Incremental backups are a must. For now, I have it sorted out with expensive wordpress plugins that make me invest a lot of time everytime I want to restore if the WordPress install is not operative.
I suggest you ask in GitHub for an Hestia integration.
I am the original author of vesta-borg backups scripts. Let me know if i can do something to help. It would be great to see this integrated into hestia core.
As far as I can see - which isn’t very far by the way, I’ve only done a search and replace then fell off my chair when it all worked!!! - I thought the existing backup options can possibly be reused:
The compression (gzip, zstd), maybe add Borg here?
The quantity of backups, maybe Borg could interpret this as the time between full-backups? /usr/local/hestia/data/users/[USERNAME]/user.conf > BACKUPS=‘1’
The location/protocol, I’m thinking these could remain the same. These are here: /usr/local/hestia/conf/hestia.conf > BACKUP_MODE/BACKUP_SYSTEM
Unfortunately shell code is not something I’m good at though so my 2 pence worth is just a hopeful suggestion.
I think that if we want it integrated we need to decide:
Who will merge the scripts?
Who will maintain this Borg feature?
Will we create also an UI in the future?
And what does the development team think about this.
You can’t promise that you will help. I get it. So we will have to create a pull request ourselves.
I was not asking for a promise. I was asking if the development team is willing to support this addition or if it would be unsupported and we have to support it ourselves.
You have already said that you have other priorities.
If we make an acceptable pull request will you maintain this feature, will you partially maintain this addition or you most likely not maintain it.
v-restore-user did not rebuild web and mail domains and dns domains and so on haven’t tested fully why
To allow for use in Web UI at least Listing active backups should be possible
borg list /backup/borg/home/user seem to be working how ever it would be nice to allow restoring a specific domain that is “active” in the backup but not on the Hestia server.
All settings are currently more or less hardcode. We should probally add support to make it more flexible
Even the “Hestia” backup is far from perfect and I totally agree with it allows restoring only a domain or even only one mail account.
So is it useful? Yes, probally
Does it need a lot of work? Yes, for sure.
Just use v-backup-user, and leave hestia panel make backup of all, databases, users etc
So, why break your head, focus just in a problem, and problem big resource, big space and big time used to make backup in large sites, or large mail servers.
So leave hestiacp make a backup of hestia account, databases and just integrate a borg, duplicity or any orther to make diferencial backup of web files and emails.
In anyway you need make mysql databases each day, also mail passwords and any orther information ( information with very few mb and information than not need incremental backup ) and hestia panel just do it well
Just integrate diff backup inside v-backup-user and v-restore-user
I’ve come across this thread and wanted to ask if there’s any recent progress or updates regarding the integration of BorgBackup with HestiaCP. Is the approach still actively maintained or has it been considered obsolete or replaced by something else?
Personally, I’ve had great experiences with BorgBackup – I really love its deduplication feature, which saves an incredible amount of disk space in my environment. It has proven to be extremely reliable for incremental and frequent backups.
That said, I’m curious:
What is currently considered the best or most reliable backup strategy for HestiaCP installations, especially with regard to speed, deduplication, offsite storage, and ease of recovery?
Thanks in advance for your insights and recommendations!
One last question on this topic: I’ve looked through the documentation and saw that backups can be created via CLI.
Is it also possible to back up all users from the web interface?
My goal is to perform regular backups, which are stored on my NAS.
I want to automate this using Restic so that backups are created on a schedule and a defined number of backup versions are retained.
In the event of a system failure, I want to be able to restore everything quickly and easily.
I’m aware that backups are often neglected, and I want to avoid making that mistake.
