You could probably use CIFS, NFS or sshfs. It wouldn't be as fast, but the
memory requirements should be less.
Sent from my T-Mobile 4G LTE Device
Original message From: John Long
Date:2016/03/25 04:10 (GMT-08:00)
To: rsync@lists.samba.org Cc:
https://bugzilla.samba.org/show_bug.cgi?id=11812
Bug ID: 11812
Summary: rsync without --verbose still writes "(new) backup_dir
is ..." to STDOUT
Product: rsync
Version: 3.1.2
Hardware: All
OS: Linux
Thank you.
On Sun, Mar 27, 2016 at 02:58:49AM -0400, Kevin Korb wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> You will have an old backup dir and a new backup dir. The new one
> will contain all the current stuff. The old one will contain what was
> current the last time you ran
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You will have an old backup dir and a new backup dir. The new one
will contain all the current stuff. The old one will contain what was
current the last time you ran rsync. Just rm -rf the old one. Or
keep a few. Or a few dozen.
On 03/27/2016
Thanks I'll look this up. There is still the issue of how to get the target
box cleaned up since I can no longer run --delete.
/jl
On Sun, Mar 27, 2016 at 02:49:02AM -0400, Kevin Korb wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> You miss-understand the purpose of --link-dest.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You miss-understand the purpose of --link-dest. Yes, it gives you
multiple complete backups, but each only consumes the disk space
needed to store files that are unique to that backup. Files that are
the same in 2 backup runs are actually the same
Hi,
On Fri, Mar 25, 2016 at 11:16:47AM -0400, Kevin Korb wrote:
> If you were using --link-dest to make multiple backups you wouldn't
> need --delete because the target is always a new empty directory (with
> - --link-dest pointing to the previous backup run).
The source is around 200G and the