On Thu, Jun 2, 2022 at 2:29 AM Libor Klepáč <libor.kle...@bcom.cz> wrote: > > Hi, > we use backuppc in containers (systemd-nspawn), each instance on > separate btrfs drive. > Then we do snapshots of said drives using btrbk. > We pull those snapshots from remote machines, also using btrbk. > > If we need to spin up container in remote location (we have longer > retention in remote location), we just create read-write copy of > snapshot and spin it up to extract files. > > With backuppc4, we also tried to use btrfs compression using zstd, > instead of backuppc internal compression (you don't need compression, > because you don't use checksum-seed anymore). > Seems to work nice too. > > > Libor >
Interesting implementation. How do you manage the configuration files? Is it inside the snapshot as well? You launch a new container on the remote location and it reads the configuration from the snapshot? If you have documented this implementation in some blog or Medium, I'm interested to read more about it. -- Sharuzzaman Ahmat Raslan _______________________________________________ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: https://github.com/backuppc/backuppc/wiki Project: https://backuppc.github.io/backuppc/
