https://bugzilla.samba.org/show_bug.cgi?id=2294
--- Comment #41 from Mihnea-Costin Grigore ---
The discussion about file systems like ZFS/BTRFS/etc. and their various
snapshot mechanisms is off-topic relative to this feature request, since they
are very different technologies used for different p
https://bugzilla.samba.org/show_bug.cgi?id=2294
--- Comment #39 from andy ---
> This feature request is so old it has lost relavence because btrfs/zfs/etc
> are more optimal backup solutions than rsync.
Funny I am doing exactly this, but I came to rsync looking for a backup for
when ZFS fails.
echo $? )
After some more tests, the ERR-Code are:
"22 - Error allocating core memory buffers"
(with --delete-before)
But, now there are only ~100.000 Files to delete, in some Tranches.
IMHO:
rsync read the Fileslist without problems, begins with deleting (and on
thi can decrea
shell expands that wildcard giving rsync a list of sources. The
--delete only operates within that list meaning that anything not
currently in that list is immune to deletion.
no, $SOURCE $TARGET are only placeholder here. In real there are normal
path's like: /foo/bar /new/foo/bar
The Rsync does
tains a *
or other wildcard. If there is a wildcard in the source parameter then
the shell expands that wildcard giving rsync a list of sources. The
--delete only operates within that list meaning that anything not
currently in that list is immune to deletion.
no, $SOURCE $TARGET are only placeh
ins a *
or other wildcard. If there is a wildcard in the source parameter then
the shell expands that wildcard giving rsync a list of sources. The
--delete only operates within that list meaning that anything not
currently in that list is immune to deletion.
If that doesn't answer your questi
al post here reproduce the permission
> change?
>
>
>
> PS: In my case the attached script shows (excerpt):
>
> ./setup_cp_al.sh
>
> Tested with
> - rsync version 3.2.7 protocol version 31
> - ext4 file system
> - Ubuntu 22.04
>
> File stats BEFORE rsync
e the permission change?
- Q: Did my script attached to the initial post here reproduce the permission
change?
PS: In my case the attached script shows (excerpt):
./setup_cp_al.sh
Tested with
- rsync version 3.2.7 protocol version 31
- ext4 file system
- Ubuntu 22.04
File stats BEFORE
On Fri 22 Sep 2023, Kevin Korb via rsync wrote:
> 444 {} +' to make read only files for rsync to want to chmod, then used cp
> -al to make several duplicate trees using hard linked files. An rm -rf on
> one such tree took .97 seconds while an rsync deletion took 1.25 seconds.
Be sure to drop the
-09-21 at 20:08 -0400, Kevin Korb via rsync wrote:
I have heard in the past that rsyncing an empty dir over a tree to
delete the tree is faster than an rm -rf but I can't say I have ever
benchmarked it to get any actual numbers.
This **may** indeed be a myth (for a long time now) re-cited
On Thu, 2023-09-21 at 20:08 -0400, Kevin Korb via rsync wrote:
> I have heard in the past that rsyncing an empty dir over a tree to
> delete the tree is faster than an rm -rf but I can't say I have ever
> benchmarked it to get any actual numbers.
This **may** indeed be a myth (f
ginal
poster didn't have access to do an rm while you are trying to get a
performance boost.
I have heard in the past that rsyncing an empty dir over a tree to
delete the tree is faster than an rm -rf but I can't say I have ever
benchmarked it to get any actual numbers. But now that I a
-
When deleting a complete snapshot folder with rsync using an empty source folder
(which is a best practice for faster deletion than "rm -f") the permissions of
hardlinked
files are changed from eg. 444/-r--r--r-- to 644/-rw-r--r-- for all deleted
files
with existing hardlinks:
mkd
I can see very complex ways to do this but I can't see a reasonably
simple way to do it.
I want to copy all *.log files from a directory hierarchy and then
delete them. I want to preserve the hierarchy at the destination so
(if I ever need to) I can associate the log files with the place
https://bugzilla.samba.org/show_bug.cgi?id=2294
--- Comment #38 from Claudius Ellsel ---
This basically is some personal preference. I know that I can do this on btrfs
(which is used on the system I want to back up from), also pretty easy with
tools like snapper. Maybe it would be feasible to do
https://bugzilla.samba.org/show_bug.cgi?id=2294
--- Comment #37 from elatl...@gmail.com ---
The btrfs equivalent is a bit more rough but (link for rename);
#./btrfs-snapshots-diff.py -sb -p /media/btrfs/v_1/s_1 -c /media/btrfs/v_1/s_2
| grep -E path=. | grep -v utimes | tail -n +2
link;path=fileB
https://bugzilla.samba.org/show_bug.cgi?id=2294
--- Comment #36 from elatl...@gmail.com ---
(In reply to Claudius Ellsel from comment #35)
> This is going off-topic
On such an old bug with modern workarouds I think it's worth talking about.
> backup drive is NTFS currently, which would complicat
https://bugzilla.samba.org/show_bug.cgi?id=2294
--- Comment #35 from Claudius Ellsel ---
(In reply to elatllat from comment #34)
>Yes you can easily access files on a COW-FS backup; it's a file system, that's
>>what it's for.
This is going off-topic, but my backup drive is NTFS currently, which
https://bugzilla.samba.org/show_bug.cgi?id=2294
--- Comment #34 from elatl...@gmail.com ---
(In reply to Claudius Ellsel from comment #33)
Yes you can easily access files on a COW-FS backup; it's a file system, that's
what it's for.
If you want to review changes before backup you can just diff or
https://bugzilla.samba.org/show_bug.cgi?id=2294
--- Comment #33 from Claudius Ellsel ---
Hm, those backups won't work on file level, though afaik. Thus I cannot easily
access files on a backup drive for example. Also I want to use this as some
kind of confirm stage a bit like committing with git
On Mon, Nov 23, 2020 at 1:33 PM CRTS via rsync
wrote:
> then the empty directory does end up in bkp.
>
You mean "does not". That is correct, as it only creates backup dirs to
hold backup files. I recall this being specifically chosen as the desired
outcome but not the details of why (since it w
https://bugzilla.samba.org/show_bug.cgi?id=2294
--- Comment #32 from elatl...@gmail.com ---
(In reply to Claudius Ellsel from comment #31)
Yes any COW FS with "send/receive" will have inherent rename handaling, and
will be faster than rsync because the diffs are inherent. With zfs one can even
hav
https://bugzilla.samba.org/show_bug.cgi?id=2294
--- Comment #31 from Claudius Ellsel ---
To me and others it still seems relevant.
I have to admit though that I haven't looked much into other solutions for
backups like btrfs send/receive commands. I suppose that were the ones you
meant? Note tha
https://bugzilla.samba.org/show_bug.cgi?id=2294
--- Comment #30 from elatl...@gmail.com ---
This feature request is so old it has lost relavence because btrfs/zfs/etc are
more optimal backup solutions than rsync.
--
You are receiving this mail because:
You are the QA Contact for the bug.
--
Ple
https://bugzilla.samba.org/show_bug.cgi?id=2294
--- Comment #29 from Claudius Ellsel ---
As another motivation for this, I use rsync for backups and would like to be
able to see whether files have just been renamed or were deleted and some
others newly created (which currently cannot be distingui
https://bugzilla.samba.org/show_bug.cgi?id=2294
Claudius Ellsel changed:
What|Removed |Added
CC||claudius.ell...@live.de
--- Comment #28 f
directory in src will be copied to tgt. However, if thedirectory is removed from srcrmdir src/emptyand rsync is run likersync -r --delete -b --backup-dir=../bkp src/ tgt/then the empty directory does end up in bkp. I am using the --backup-dirand the --delete option to move an outdated snapshot to another
Consider following directory structure:
> mkdir -p src/empty tgt bkp
when making an initial backup with
> rsync -r src/ tgt
then the empty directory in src will be copied to tgt. However, if the
directory is removed from src
> rmdir src/empty
and rsync is run like
> rsync -r
https://bugzilla.samba.org/show_bug.cgi?id=3465
--- Comment #8 from Wayne Davison ---
Jeff: the command you mention already works fine, since --files-from is not
involved.
--
You are receiving this mail because:
You are the QA Contact for the bug.
--
Please use reply-all for most replies to av
ta]
...
> path = /mnt/DATA
...
> Client side:
> # crontab -l
> 0 */3 * * * /path/to/rsync.sh
> # cat /path/to/rsync.sh
> rsync -avPH --chmod=D755,F644 --delete rsync://xxx.xxx.xxx.xxx/data/
> Any idea or suggestion to prevent client's data
e
> transfer will fail when the mount is not there (because the subdir
> is not there).
For a moment, I use validation to make sure server side -NOT- empty
directory. For example:
#!/bin/sh
TEST="$(rsync -n rsync:/xxx.xxx.xxx.xxx/data/ | awk 'END {print NR}')"
if
On Fri, Jun 26, 2020 at 10:24 AM Budi Janto wrote:
> path = /mnt/DATA
> Any idea or suggestion to prevent client's data loss?
>
There are several options:
1. Set the "pre-xfer exec = /script/name" in your daemon module and make
the script check if a /mnt/DATA/known-to-exist-subdir is missi
/path/to/rsync.sh
# cat /path/to/rsync.sh
rsync -avPH --chmod=D755,F644 --delete rsync://xxx.xxx.xxx.xxx/data/
Any idea or suggestion to prevent client's data loss? Thank you.
--
Regards,
Budi Janto
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubs
ing
> data in /mnt/DATA (Just empty directory), so client with rsync running
> periodically with mode --delete it's safety or will remove data on
> client too?
If the rsync source path is /mnt/DATA yes, it will remove data on the
client, but if the source path is a sub-directory of /m
ning
periodically with mode --delete it's safety or will remove data on
client too?
--
Regards,
Budi Janto
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www
https://bugzilla.samba.org/show_bug.cgi?id=13991
Wayne Davison changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
protocol version 31
> Client rsync: rsync version 3.1.3 protocol version 31
>
> Command used:
> rsync --numeric-ids --delete --delete-excluded --delete-after -f "merge
> ${BUFFER}" --stats -e "${SSH_CMD}" root@${BACKUP_HOST}:/ $BACKUPROOT/
>
> Someti
3.1.3 protocol version 31
Command used:
rsync --numeric-ids --delete --delete-excluded --delete-after -f "merge
${BUFFER}" --stats -e "${SSH_CMD}" root@${BACKUP_HOST}:/ $BACKUPROOT/
Sometimes when I run this script from the server it just decides to
delete ALL files what it alre
https://bugzilla.samba.org/show_bug.cgi?id=13920
Wayne Davison changed:
What|Removed |Added
Resolution|--- |WONTFIX
Status|NEW
he source
> tree and on the target tree when calling rsync with -a --delete.
>
> mkdir -pv src/ dst/
> echo file1 > src/file
> echo file2 > dst/file
>
> rsync -navi --delete --exclude file src/ dst/
>
> works as expected. The file is not transferred nor is it d
Hello,
I want to avoid transferring a file which is present both on the source
tree and on the target tree when calling rsync with -a --delete.
mkdir -pv src/ dst/
echo file1 > src/file
echo file2 > dst/file
rsync -navi --delete --exclude file src/ dst/
works as expected. The file
https://bugzilla.samba.org/show_bug.cgi?id=13991
--- Comment #1 from Bruce Arden ---
Created attachment 15235
--> https://bugzilla.samba.org/attachment.cgi?id=15235&action=edit
Commands to demonstrate further problem
set VG to an LVM volumegroup with spare space
On my machine this gives:
...
https://bugzilla.samba.org/show_bug.cgi?id=13991
Bug ID: 13991
Summary: rsync --delete --one-file-system skips deletes after
crossing filesystems on destination.
Product: rsync
Version: 3.1.3
Hardware: All
https://bugzilla.samba.org/show_bug.cgi?id=13920
Bug ID: 13920
Summary: --max-delete and dirs being replaced by symlinks on
source
Product: rsync
Version: 3.1.2
Hardware: All
OS: All
Status: NEW
Merci Francis.
Yes, that would probably be a way to do it, but I guess it needs
correctly escaping the special characters which may appear in file
names. (Yes, there are people who use "*" in file names, etc.)
So what I'm doing now is using neither --delete-missing-arg nor
--
Hi.
On Tue, 23 Apr 2019 16:35:15 +0200 MI via rsync wrote:
> If someone has a good suggestion on how to rsync a list of files and
> delete from the destination any file that is not listed in --files-from,
> that would be welcome.
Assuming you are talking about files in a sa
Thank you Kevin.
It seems that I misunderstood the purpose of this --delete-missing-args
option.
If someone has a good suggestion on how to rsync a list of files and
delete from the destination any file that is not listed in --files-from,
that would be welcome.
Thanks,
MI
--files-from will delete files from the destination that are listed but
not existing in the source. It isn't delete what isn't listed.
On 4/23/19 5:29 AM, MI via rsync wrote:
> I'm generating a list of files to sync, and would like all the files not
> in my list t
I'm generating a list of files to sync, and would like all the files not
in my list to be deleted from the destination. I thought that
--delete-missing-args would do just that, but it doesn't delete anything.
Would someone have an idea of what I'm doing wrong?
This is what I tr
older in my machine with
> the followin|g command:|
> |rsync -avh --delete /source/ /destination|
> |
> |
> |But the extra files that where on "destination" didn't got deleted.
> Where as doing:|
> ||rsync -avh --delete /source/ /destination/||
> ||worked a
Hi, I was trying to make a mirror backup of a folder in my machine with the
following command:
rsync -avh --delete /source/ /destination
But the extra files that where on "destination" didn't got deleted. Where
as doing:
rsync -avh --delete /source/ /destination/
worked as expecte
>You need to switch to filters where you have the additional options
>hide, show, risk, and protect. See the filter rules section of man rsync.
Thanks for the hint. Though I've been using rsync for years this part has
somehow escaped me. I've read up on the filters and they do what I
need. The d
You need to switch to filters where you have the additional options
hide, show, risk, and protect. See the filter rules section of man rsync.
On 12/4/18 8:36 AM, Fabian Cenedese via rsync wrote:
> Hello
>
> I'm looking for a way to exclude and delete some items but not delete
>
>> I'm looking for a way to exclude and delete some items but not delete
>> other items. Use case:
>>
>> I'm on Windows where there are folders like recycle.bin and system
>> volume information on every drive. I can exclude them while backing
>> up
Hi,
On 5/12/18 12:36 am, Fabian Cenedese via rsync wrote:
> I'm looking for a way to exclude and delete some items but not delete
> other items. Use case:
>
> I'm on Windows where there are folders like recycle.bin and system
> volume information on every drive. I can e
Hello
I'm looking for a way to exclude and delete some items but not delete
other items. Use case:
I'm on Windows where there are folders like recycle.bin and system
volume information on every drive. I can exclude them while backing
up my data drive. But I now also have other da
wouldn't
>> get copied and if you had S/else it wouldn't get copied. Maybe you want
>> to add --prune-empty-dirs and an --include='*/' so that rsync will look
>> inside of all dirs for matching files.
> All not working so when when working with the nex
Maybe you want
> to add --prune-empty-dirs and an --include='*/' so that rsync will look
> inside of all dirs for matching files.
All not working so when when working with the next HDD backup:
rsync -vain --prune-empty-dirs --delete \
--include='[T-Z]*' --include='*/&#x
will look
inside of all dirs for matching files.
On 05/03/2018 02:50 PM, Mike Brown via rsync wrote:
> On Thu, May 03, 2018 at 01:09:30AM -0400, Kevin Korb via rsync wrote:
>> --delete only works when you sync a dir not individual files. So...
>> rsync -vai --delete --in
On Thu, May 03, 2018 at 01:09:30AM -0400, Kevin Korb via rsync wrote:
> --delete only works when you sync a dir not individual files. So...
> rsync -vai --delete --include='g*' --include='G*' --exclude='*'
> /share/Public/videos/ /share/Backup-HDD-03
That
--delete only works when you sync a dir not individual files. So...
rsync -vai --delete --include='g*' --include='G*' --exclude='*'
/share/Public/videos/ /share/Backup-HDD-03
On 05/03/2018 12:08 AM, Mike Brown via rsync wrote:
> rsync version 3.1.2 protocol
rsync version 3.1.2 protocol version 31
I've run into an issue using rsync on my QNAP NAS. I've installed Entware-ng
on the NAS so that I can install better versions of programs, rsync being
one of them.
But, I've run into an issue wqith using the --delete option, as it has
https://bugzilla.samba.org/show_bug.cgi?id=13388
Bug ID: 13388
Summary: Feature request: When deleting files only delete files
that are over a certain age.
Product: rsync
Version: 3.1.3
Hardware: All
OS
"rsync --server -vulogDtpre.iLsfxC --timeout=600 --bwlimit=5120
> . dest" ssh-rsa
>
> Tacking on --delete in the appropriate spot fixed the issue.
>
> That's a big whoops on my part. :-) Appreciate the pointer.
>
--
~*-,._.,-*~'`^`'~*-,._.,-*~'
Hi, Kevin. Thank you for the suggestion. It triggered a memory that I
had set some restrictions on this rsync copy a while back. Sure enough,
in ~/.ssh/authorized_keys:
command="rsync --server -vulogDtpre.iLsfxC --timeout=600 --bwlimit=5120
. dest" ssh-rsa
Tacking on --del
meout=600 --bwlimit=5120 -v -e "ssh -i /path/to/key"
> --filter=". /path/to/filter" /path/to/source/ u...@remote.server.com:dest
>
> This works perfectly fine. However, I recently realized that I forgot
> to the --delete option, so there are a great number of stale
u --timeout=600 --bwlimit=5120 -v -e "ssh -i /path/to/key"
--filter=". /path/to/filter" /path/to/source/ u...@remote.server.com:dest
This works perfectly fine. However, I recently realized that I forgot
to the --delete option, so there are a great number of stale files on
the r
--delete means delete from the target what isn't on the source (except
what is excluded). Those look like temp files. Possibly from another
rsync that is running at the same time.
On 05/01/2017 12:36 AM, Chandana De Silva via rsync wrote:
> All,
> I have an rsync based backup process
All,
I have an rsync based backup process which uses rsyncd on the source,
to backup to a directory on the client.
I have rsync version 3.1.2 on the client and 2.6.8 on the source host
(daemon).
The rysnc command I use is;
/usr/bin/rsync -aHzS --partial --numeric-ids --delete --timeout=3600
options to
address this problem: --ignore-missing-args and --delete-missing-args .
The bad news, however, is that even with any of these, when the file
disappears, rsync handles the file transfer properly, but then tries to
set times or attributes on these files nevertheless. That fails with
errno 2
temporary files, a user can still delete something old enough right in
the middle of an rsync.
However, looking at rsync problems that we have more closely, I now
realize that most of them are related to time setting issues -- part of
these similar to bug https://bugzilla.samba.org/show_bug.cgi
>
> Also, sounds like what you really want is --files-from
>
files-from is part of the command.
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~
ago:
>
> https://bugzilla.samba.org/show_bug.cgi?id=12569
>
> Due to this I'm currently not using --ignore-missing-args /
> --delete-missing but rather -exclude=* -include=- and a autocreated
> hierachical filter rule list on stdin.
>
> PS: Yes to simply ignore code 24
With this two options on a very live system you may need to take into
account this bug as well I reported a while ago:
https://bugzilla.samba.org/show_bug.cgi?id=12569
Due to this I'm currently not using --ignore-missing-args /
--delete-missing but rather -exclude=* -include=- and a autocr
small, so one final transfer can later save the day. )
>
> The problem, as one may guess, is that some files may disappear during
> the process, so rsync finishes with an error code 23.
> The good news is that since version 3.1.0 rsync has two options to
> address this problem: --ig
ve the day. )
The problem, as one may guess, is that some files may disappear during
the process, so rsync finishes with an error code 23.
The good news is that since version 3.1.0 rsync has two options to
address this problem: --ignore-missing-args and --delete-missing-args .
The bad news, howeve
https://bugzilla.samba.org/show_bug.cgi?id=2294
--- Comment #27 from Wolfgang Hamann ---
Hi,
I recently ran into the problem that a large file set got renamed and then
re-sent. I tried to fix after the fact, so I went the obvious way of comparing
sizes and modtimes on the destination and calcula
https://bugzilla.samba.org/show_bug.cgi?id=2294
--- Comment #26 from Ben RUBSON ---
### What's the diff between --fuzzy and --detect-renamed ?
If I understand correctly, --fuzzy looks only in destination folder, for either
a file that has an identical size and modified-time, or a similarly-named
several times
>on the Internet and the usual answer is that there's no way
>around it because of the way that rsync works. I don't mind
>that they are created if there's a (rsync-)way to delete them
>again afterwards, something like
>
>rsync -a --delete --prune-em
At 17:57 02.06.2016, Steven Levine wrote:
>>rsync -a --delete empty_local_folder remote_folder_to_delete
>
>>to get rid of the contents. However the folder itself still remains. So
>>after a while I'd have a lot of empty folders.
>
>This comes up on the list ever
In <20160602082722.8F11829233B7@macserver.private>, on 06/02/16
at 10:27 AM, Fabian Cenedese said:
Hi Fabian,
>rsync -a --delete empty_local_folder remote_folder_to_delete
>to get rid of the contents. However the folder itself still remains. So
>after a while I'd have a
At 13:22 02.06.2016, you wrote:
>Content-Transfer-Encoding: 7bit
>
>Fabian Cenedese wrote:
>
>> This script is bash and also uses the "remote shell hacks" using SSH.
>> As I want to run it also from Windows I'm looking for a rsync solution.
>
>Assuming you have control of the server, can you do a
Fabian Cenedese wrote:
> This script is bash and also uses the "remote shell hacks" using SSH.
> As I want to run it also from Windows I'm looking for a rsync solution.
Assuming you have control of the server, can you do a bit of semaphore ?
Eg, do your backup with rsync, then when it's complet
Fabian Cenedese wrote:
> Are there pure rsync ways to solve these two problems?
Short answer - no I don't think there is.
My feeling is that rsync (at least, rsync on it's own) isn't the right tool for
the job.
One think I would comment on though is that, IMO, making backup policies under
the
At 10:52 02.06.2016, Hans-Christian Jehg wrote:
>Content-Transfer-Encoding: 7bit
>
>Try having a look at this, for inspiration.
>
>It does require the capability of hard-links on the remote end though... and
>it does not resolve your "delete target directory" either,
Try having a look at this, for inspiration.
It does require the capability of hard-links on the remote end though...
and it does not resolve your "delete target directory" either, but it
might save you some fiddeling around :-)
https://blog.interlinked.org/tutorials/rsync_time_ma
don't mind
that they are created if there's a (rsync-)way to delete them
again afterwards, something like
rsync -a --delete --prune-empty-dirs dest dest
Unfortunately at least one place has to be local, doing a
remote-remote is not possible.
The second problem is that I want to delete olde
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
emory 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
> that only has 2
last time you ran rsync. Just rm -rf the old one. Or
> keep a few. Or a few dozen.
>
> On 03/27/2016 02:54 AM, John Long wrote:
> > 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.
> &
:54 AM, John Long wrote:
> 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: You
> miss-understand the purpose of --lin
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 purpo
file in multiple
directories requiring only 1 to actually be stored.
On 03/27/2016 02:39 AM, John Long wrote:
> 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
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 aroun
-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 backu
'm mirroring is
> about 200G of files. A minority of subdirectories have many files.
>
> Is there a way to do an incremental backup with --delete option that does
> not use as much memory? Is there a way to tell rsync to use a tempfile
> instead of RAM for keeping tracking of wha
out 200G of files. A minority of subdirectories have many files.
>
> Is there a way to do an incremental backup with --delete option that does
> not use as much memory? Is there a way to tell rsync to use a tempfile
> instead of RAM for keeping tracking of whatever it does?
No to the l
.
Is there a way to do an incremental backup with --delete option that does
not use as much memory? Is there a way to tell rsync to use a tempfile
instead of RAM for keeping tracking of whatever it does?
And would it be useful to add ignores for the subdirectories I know have
many files and back th
On Sun, 06 Mar 2016 22:20:16 +
samba-b...@samba.org wrote:
> https://bugzilla.samba.org/show_bug.cgi?id=2294
>
> --- Comment #23 from dajo...@gmail.com ---
> Looking for this capability prior to entering it as an enhancement request
> myself, I found everything here and basically have the sam
https://bugzilla.samba.org/show_bug.cgi?id=2294
--- Comment #25 from Andrey Gursky ---
On Sun, 06 Mar 2016 22:20:16 +
samba-b...@samba.org wrote:
> https://bugzilla.samba.org/show_bug.cgi?id=2294
>
> --- Comment #23 from dajo...@gmail.com ---
> Looking for this capability prior to entering
1 - 100 of 1095 matches
Mail list logo
