Backup Improvements: Restic Backend
-
@girish @necrevistonnezr said in Backup Improvements: Restic Backend:
approx. 30 minutes
that is extremely fast, CIFS + tgz and almost same amount of GB's takes almost 2 hours
-
-
-
-
@girish any plan to improve the backup solution on cloudron maybe with Restic as engine?
-
@MooCloud_Matt we are rewriting the storage backend a bit in https://forum.cloudron.io/topic/6768/what-s-coming-in-7-2 . Part of the reason is to make more backends easier to integrate.
-
Are there any plans to add Restic as an extra backup method? Two of my Cloudrons are in the meanwhile +200GB and the current methods are not sufficient.
-
Not yet but I would like to discuss one thing here. Backups are crucial and loss of data for us implies loss of business and money quite literally. This is why we wrote the backup code ourselves a while ago. Also, why we create our own packages - it's all about data integrity and loss of data === loss of trust in product.
Initially, before we wrote our own backup stuff, I remember we used duplicati and btrfs etc . We faced various issues and there was essentially no help from upstream. Now, restic I am sure is great but if there is some corruption or issue, our customers will look to us to solve this. So, this is a tricky situation for us Maybe we can do some restic integration with lots of warnings? End user also has to know what to do if there is restic corruption and other issues. Keep in mind restic is also not 1.0 yet . They say "Once version 1.0.0 is released, we guarantee backward compatibility of all repositories within one major version; ...".
Any suggestions?
-
-
-
Curious for which settings do you recommend for backups to Storagebox and how much better it can get
-
@imc67 still working through the backups rewrite, will leave a note here once I have something.
-
-
Any update on the backup methodology? I read a lot of issues in the forum about crashing backups due to several reasons. Maybe this can help?
-
@imc67 we have not started working on a restic backend, if that's what you are asking.
I think most of the issues are just because of using a large variety of s3 providers. There's way too many of them. Made worse by people choosing the cheapest/low end providers who don't provide any support either. That and SSHFS/CIFS flakiness. I doubt moving to restic solves any of this because they are not related to backup code itself but infrastructure related. Just my thoughts though.
Now instead of dealing with our backup issues, we would be dealing with issue of another backend like say 1, 2 and 3 - these are just restic issues of last week. It would be worse because we have not much idea on how to deal with restic bugs.
-
FWIW I have a RaspberryPi for 3 years with a Restic daily backup to a Cloudron Minio S3 and 2 weeks ago I needed a restore for the first time. It took me the most time to rediscover how I configured it 3 years ago and how to restore but it worked flawless! I know itβs just n=1 but itβs worth to have a look at it.
-
@robi yes definitely.
I do know that people want urgent fixes when backups and restores are not working, I just don't know how we can take up this responsibility. If my production site is down and it doesn't restore, what now? This will cost us real money because people will ask for a refund.