Strangely enough, my /var/lib/backuppc is on a 3-disk ZFS pool.
Primarily for reliability, secondarily to give a larger file system space.
ZFS is pure software (no hardware RAID controller needed) and has many
other advantages too.
On 22/08/2024 15:32, Les Mikesell wrote:
While you are at it, be sure you understand the implications of that
--one-file-system option which also changed with v4. Without it you
will wander into DVDs or network mounts that happen to be present when
backuppc runs even if they are temporary. With it you have to
explicitly all the partitions you want backed up and pay attention if
that ever changes. As for your comments on filesystems, I think you
are better off using a raid system that will remove the bad disk if
errors are detected, rebuilding when you replace it. I always liked
the simplicity of software raid1 (mirrored) because you could recover
from any surviving disk on any computer with a compatible interface or
even a USB adapter and a laptop, but realistically most raid
controllers are good enough. Also having the server on a UPS is a
good idea since files/filesystems can be corrupted if you lose power
when writing. Your comment about rsync failing with OOM mostly
applied to older versions that had to read the entire directory tree
into memory before starting - and that and network errors don't
normally corrupt existing files, so they auto-correct on the next run.
_______________________________________________
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/
