Make an option to provide the volume plugin type/name for all the volumes (to aid backups)

[Bubbelb]

Well, see it as part of a bigger idea: I'm using BTRFS as storage backend for containers. BTRFS in this way is only of benefit for the images and the dynamic data in the container, built of that image.

But I want more: I want to make snapshots, or clones of all the volumes, so that I can make the following process work:

1. Stop all the (Nextcloud all-in-one) containers
2. Snapshot/Clone alle the volumes that are to be backed-up
3. Start all the (Nextcloud all-in-one) containers
4. Run Borgbackup to backup all the snapshots/clones
5. Remove the snapshots/clones
6. rinse-repeat :)

To this end I'm planning to try out the 'buttervolume' Docker volume plugin. See here

The big benefit of this is the absolute minimal downtime for a backup, even when there are big volumes of data being ingested, which obviously require more backup time.

A secondary benefit can be that the snapshots can be used for instant recovery, in stead of the borgbackups. I think this would increase restore times. Though I'd still recommend that the borgbackups remain, so one can also recover from a disk, or filesystem failure, using the borgbackups.

What do you all think of it?

[szaimen]

Hi, this is already possible via https://github.com/nextcloud/all-in-one/tree/main/manual-install. See https://github.com/nextcloud/all-in-one/blob/main/manual-install/latest.yml

[Bubbelb]

Yes, you are right, but that route disables a lot of functionalities I like about AIO, especially all the functions of the management container.

And I'd like to try and make the mentioned backup procedure automated in a community-container. I know this wold require some work in the management container, since it overrides the standard backup.

But that is all future planning for now. So i'll create a test bed with a manual install, and try to create the backup in the way that is mentioned here. I'll get back when I get it working.