When syncing one backup system (running dirvish, but that's not really
relevant) to a second long-term backup system which uses btrfs
snapshots, I get the following output:
rsync: link
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
If you are switching to btrfs subvolume snapshots then you don't want
to do all the rsync hard linking. You want to copy each backup onto a
separate subvolume. Something like this (psuedo code):
Assuming you have /backup/rsync/oldest as the oldest
On Thu 01 Dec 2011, Kevin Korb wrote:
If you are switching to btrfs subvolume snapshots then you don't want
to do all the rsync hard linking. You want to copy each backup onto a
separate subvolume. Something like this (psuedo code):
If you look carefully at the output, these are files that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Right, I was assuming they were linked in the source because you were
using rsync --link-dest to do your incremental backups.
On 12/01/11 09:48, Kevin Korb wrote:
If you are switching to btrfs subvolume snapshots then you don't
want to do all the
On Thu 01 Dec 2011, Kevin Korb wrote:
Right, I was assuming they were linked in the source because you were
using rsync --link-dest to do your incremental backups.
Good point, that's probably a remnant from an older version of the
script :-) I'll remove that.
Thanks.
Paul
--
Please use
https://bugzilla.samba.org/show_bug.cgi?id=8566
--- Comment #1 from Stefan Nowak p@gmx.at 2011-12-01 21:31:18 UTC ---
1) Could someone please answer how to successfully sync Spotlight comments?
Thanks!
2) As of 3.0.9 this functionality seems not to be integrated in the main
distribution, as
https://bugzilla.samba.org/show_bug.cgi?id=8566
--- Comment #2 from Stefan Nowak p@gmx.at 2011-12-01 21:58:28 UTC ---
I downloaded 3.0.9 source + patches, patched in the 2 patches:
patch -p1 patches/fileflags.diff
patch -p1 patches/crtimes.diff
And although running with the appropriate
