thveillon wrote at about 22:32:14 +0200 on Tuesday, August 24, 2021:
> Le 24/08/2021 à 15:57, Pascal Legrand a écrit :
>
> Also if you are using rsync as your method, the '--one-file-system'
> default option can cause some pain. If you have anything mounted under
> the root of you backup, you will have to choose between having that
> mount point backed up as a separate root (with '--one-file-system'), or
> under the mount point (without '--one-file-system').
I find '--one-file-system' to be critical as it prevents unintended
backups of:
- Temporary file systems (e.g., /proc, /dev, /tmp)
- Mountable file systems (e.g. dvd/cd, USB sticks)
Of course, you could write 'excludes' but to me it is easier, safer,
and cleaner to *positively* specify the mounts you want rather than
exclude the ones you don't
I backup each non-root filestystem as a separate share.
This is also cleaner (at least philosophically) in aligning shares
with filesystems. That way if a filesystem is down or broken, it just
affects the backup for that share rather than erroring-out the entire
backup.
> Personally I never
> could make a "/home/user/mount" filesystem be backed up separately with
> '--one-file-system', I resorted to remove the option and get everything
> under the same root backup.
>
Shares are dead simple... all you need is:
$Conf{RsyncShareName} = ['/', '/home/user/mount1', '/home/user/mount2',
'/home/user/mount3'];
This is at least as easy as the alternative of trying to do something
like:
$Conf{BackupFilesExclude} = {
'/' => [ '/proc/*', '/sys/*', '/dev/*', '/snap/*', '/run/*',
'/selinux/*', '/home/*/.gvfs/'],
}
Plus figuring out who knows what other loop/fuse/tmpfs/udev etc. filesystems you
may have mounted somewhere on root.
_______________________________________________
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/
