CasaOS
CasaOS copied to clipboard
IceWhaleTech
[Feedback]CasaOS backup ??? How
Description
What is the best way to do a CasaOS backup ?
Additional Information
- OS: linux
- CasaOS Version: 0.4.3
- Disk Total: 119786
- Disk Used: 3105
- System Info: [Debian GNU/Linux 11 \l Bit:64 Mem:3794M Core:4 Linux raspberrypileo 5.15.84-v8+ #1613 SMP PREEMPT Thu Jan 5 12:03:08 GMT 2023 aarch64 GNU/Linux]
- Remote Version: 0.4.3
- Browser: Safari
- Version: 13.1.2
Hi, please explain concretely what you want.
Do you mean to export all the docker compose of the applications you currently have installed in a single file or do you mean to make a data backup of the application containers.
I am not the author of the OP but I came here looking for the some ideas around backup. In my case I'd like, ideally, a one click restore of my previous installation, a kind of snapshot restore. With incremental backups that then I can store elsewhere, I'm thinking on a local disk and a remote S3, for example. That would be my final, ultimate goal, including CasaOS installation process asking for a backup to restore. That would be very handy and in line with the product's philosophy and target users. The "gray" area of self-hosting is the responsibilities you acquire with your own data, hardware failures, etc. I was thinking on mounting a remote S3 and then raync my DATA folder there,but have many questions regarding space usage and how to compress it, but at least this offer incremental backups. Another open question is of for DBs this will work on restore. Maybe we can start with some existing products recommendation we can deploy for the task.
Originally, I was asking for the best way to clone and-or save my CasaOs install itself ( the content of the RaspBerry Pi boot drive ) As of now, The best way I found is to clone the card itself by doing an image of it on my Mac .
OK not my use case then, sorry for the noice. I'm still interested in the operational backup and potentially a full restore.
There is always the Duplicati app for backups. However, it's not very newbie-friendly
Backing up the entire /DATA directory would be all-encompassing, which Duplicati doesn't have access to by default, so you need to add a volume mount, but then permissions are also an issue, so... I think some easy to use native backup app would be useful.
I have tried to set up Duplicati, and it doesn't copy many of my most important files because they are locked by running system processes. I am also unsure how I would restore the data.
Ideally, CasaOs would allow me to do a full backup of the entire disk in a format that I could then import and restore from when setting up a new CasaOs install.
A snapshot of the installed OS, and a container backup of the app. I need two methods. A snapshot of the OS to make it easier to revert if something goes wrong, I want to be able to backup my apps' containers so I can easily restore them in another docker environment.
Yes, I appreciate the work and effort you guys put into CasaOS and other self hosting solutions, but without a proper backup, what's it all worth? It's looks shiny and nice, but if you plan to make use of this for the next years and start moving a lot of data in there, there needs to be a way to backup and restore all of this.
It would be awesome if the backup runs per container/app on a schedule in the background to some specific local drive or network location. Incremental backups would be nice of course! o) I'm not sure if it's possible to differentiate between container/app data and user specific data (db-contents, pictures e.g., ). Keeping these things apart when doing backup/restore would be nice, but seems almost impossible to me, since every container does its thing and it's probably hard to decide, what data has to go where.
Please don't be offended, I find the backup part of all this self-hosting stuff to be the most difficult. A proper backup solution provides a file/folder history, malware protection (to not store encrypted data e.g.), redundancy (RAID5 e.g.), off-site backup and synchronization, easy expandable storage and maybe even a read-only archive to be able to slim down here and there and to "lock in" the past.
Well, I can dream at least, maybe some of this will end up in CasaOS one day! o)
Thank you for taking the time! o)
Container volumes are most important for me - the app data. The ability to back them up to somewhere remote so that, if needed, I can restore casa OS and deploy the containers with the backed-up volumes.
I would like to use casaos as a production system, unfortunately I miss the function of making a complete backup (fulldd) of the system, as is the case with Omv5. Will this feature be implemented at some point?
I guess in lieu of application/OS backup we would use a full disk image/snapshot
As I see there should be a way to restore a back in time snapshot of an app (active or deleted one); and a way to restore in a new machine if old installation died with all data, so backup should include:
- app configurations
- app data
Some apps could share files data, so we could make use of some tool like https://restic.net/ and tags to identify apps. I would:
- backup config in a local folder and use a specific tag for it.
- backup each app with its own tag with its volumes.
Then to restore it, you could browse them if in same machine, or if new install, when adding the repository it could download "backed configs" first.
