Re: Memory consumption for rsync -axv --delete

2016-03-28 Thread John Long
Hi, On Sun, Mar 27, 2016 at 06:39:53PM -0700, drsalists wrote: > > You could probably use CIFS, NFS or sshfs. ??It wouldn't be as fast, but the > memory requirements should be less. Sorry, I don't understand how to sync over NFS or sshfs without rsync. Can you explain this please? I don't want

Re: Memory consumption for rsync -axv --delete

2016-03-27 Thread drsalists
org Cc: Subject: Re: Memory consumption for rsync -axv --delete On Fri, Mar 25, 2016 at 09:54:14AM +, John Long wrote: > Hi, > > I have been using rsync for many years and never had any kind of problem. > Lately I am running out of RAM trying to do an incremental backup to a box > th

Re: Memory consumption for rsync -axv --delete

2016-03-27 Thread John Long
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

Re: Memory consumption for rsync -axv --delete

2016-03-27 Thread Kevin Korb
-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

Re: Memory consumption for rsync -axv --delete

2016-03-27 Thread John Long
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.

Re: Memory consumption for rsync -axv --delete

2016-03-27 Thread Kevin Korb
-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

Re: Memory consumption for rsync -axv --delete

2016-03-27 Thread John Long
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

Re: Memory consumption for rsync -axv --delete

2016-03-25 Thread Kevin Korb
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 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). So, you get the benefit of having multiple backups to

Re: Memory consumption for rsync -axv --delete

2016-03-25 Thread John Long
On Fri, Mar 25, 2016 at 09:54:14AM +, John Long wrote: > Hi, > > I have been using rsync for many years and never had any kind of problem. > Lately I am running out of RAM trying to do an incremental backup to a box > that only has 2G of RAM. The entire directory structure I'm mirroring is >

Re: Memory consumption for rsync -axv --delete

2016-03-25 Thread Paul Slootman
On Fri 25 Mar 2016, John Long wrote: > > I have been using rsync for many years and never had any kind of problem. > Lately I am running out of RAM trying to do an incremental backup to a box > that only has 2G of RAM. The entire directory structure I'm mirroring is > about 200G of files. A

Memory consumption for rsync -axv --delete

2016-03-25 Thread John Long
Hi, I have been using rsync for many years and never had any kind of problem. Lately I am running out of RAM trying to do an incremental backup to a box that only has 2G of RAM. The entire directory structure I'm mirroring is about 200G of files. A minority of subdirectories have many files. Is