similar to: rsync - using a --files-from list to cut out scanning. How to handle deletions? (fwd)

Folks, We use rsync extensively for protecting data by making backups. Thank you to the authors and maintainers. Like many others, we use the --link-dest option to cut down on the space occupied by the backups. Unlike many others, we re-cycle old backup directories. Since most file systems change only slowly (ours average about 0.5% of files and about 1.5% of data being churned each day), a

Paul Wayne, Kevin, Teodor and others, Thanks for your contributions in response to my postings. Paul: I was very imprecise if not plain wrong in my description. :-( Thanks for explaining what really happens. > "Rsync will not update an existing file in-place unless you use the > --inplace option. So --whole-file is irrelevant for this. > Rsync (without --inplace) will always

rsync Folks, The following explanatory text is by me and the patches are by Rowan McKenzie for use by the Advanced Scientific Computing group at CSIRO. This patch builds upon the --link-dest patch by Bryant Hansen (Thanks heaps!). 1. The original patch provided an alternate behaviour for rsync when using the --link-dest option. When there are identical files in the source and link-dest areas,

rsync folks, Henri Shustak <henri.shustak at gmail.com> wrote: > LBackup always starts a new backup snapshot with an empty directory. I > have been looking at extending --link-dest options to scan beyond just > the previous successful backup to (failed backups / older backups). > However, there are all kinds of edge cases which are worth considering > with such a changes. At

Hello, For some time now, our users have been encountering a problem when using scp to overwrite files on our mass-storage system, which uses SGI's DMF product. I don't have any data as to whether or not any other HSMs would be similarly affected. The scenario is that a user is overwriting a file (via scp) that has previously been migrated to tape. The scp opens the file for writing, but

A bit late for Santa, but on my wish-list nevertheless: is there any chance that "scan" and "readLines" could be extended to take a parameter "until" or "EOF.marker", which would be a character string that (if encountered while reading) would cause the reading to stop, just as if an end-of-file had been found? [But leaving a connection open, so that

Folks, Thinking again about the issue of changed attributes for a file in source that is identical in content to a file in destination that is hard linked get propagated to the --link-dest directories I would like to suggest a new flag, (perhaps called something like --preserve-linked-attributes), to allow callers to get the behaviour that is needed to allow the use of recycled

Folks, bugs at stupidkitties.com wrote: " I was wondering if it'd be feasible to add an option (or multiple options, depending on the desired granularity) to cause rsync to treat changes in file attributes the same way it treats changes to the file's contents when it encounters hard links at the destination. Maybe something like --relink-p or something?" One of colleagues has

rsync watchers, I've been using rsync version 3.1.1+, and do like the improved --stats output: e.g. Number of files: 2480403 (reg: 2034290, dir: 233487, link: 212174, special: 452) Number of created files: 356 (reg: 6, dir: 3, link: 347) Number of regular files transferred: 16 ... - thanks to the developers. However, I want to be able to look at the --stats output and make a decision

Peter, I was about to post the below to the rsync mailing list, but wondered whether your code which captures rsync output may have allowed rsync to continue past what I think would normally be a fatal error? Thanks Rob. P.S. Should I put the final backups of the old pearcey /home back into their correct slots - 5 backups were recycled, but nothing was added to them? The .Snapshots area is

Wayne, Thanks for the information - that looks useful for the future, and would replace our option. Rob. > Date: Fri, 24 Aug 2012 23:10:43 -0700 > From: Wayne Davison <wayned at samba.org> > To: Robert Bell <Robert.Bell at csiro.au> > Cc: rsync at lists.samba.org > Subject: Re: [patch] link-dest messages and max-size warnings (fwd) > > On Thu, Aug 23, 2012 at

My apologies for he very short time before things close, but it's not my fault. If necessary get your hat in the ring by Friday and see to the niceties later, may I suggest. This is a vacancy in my group in Cleveland. The work is interesting and the challenges large. Bill Venables. ---------------------------------------------------------------------------- Division of Marine Research

Thanks to Kevin and Paul for responses. We use a modified Tower of Hanoi scheme (on top of rsync and --link-dest and recycling) for deciding which backups to keep. Here is a sample of our holdings for one area: home.20111124.seq.0 set 0 home.20130512.seq.512 set 10 home.20140203.seq.768 set 9 home.20140414.seq.832 set 7 home.20140708.seq.896 set 8 home.20140815.seq.928 set 6

Hi, The following function use to work, but now it doesn't giving the error "> CallSnow(, 100) Using snow package, asking for 2 nodes 2 slaves are spawned successfully. 0 failed. Error in checkForRemoteErrors(val) : 2 nodes produced errors; first error: no applicable method for 'lapply' applied to an object of class "list" ". Where this is the

Folks, Am 20.06.2016 um 22:01 schrieb Larry Irwin (gmail): > The scripts I use analyze the rsync log after it completes and then sftp's a summary to the root of the just completed rsync. > If no summary is found or the summary is that it failed, the folder rotation for that set is skipped and that folder is re-used on the subsequent rsync. > The key here is that the folder

Folks, We faced a similar situation to that which Ken described - we recycle backup directories, for good reason. There is a patch to solve the problem. Our systems administrator provided the following description of the patches we use: ============================================================================ 1. rsync_link_dest improvement by Bryant Hansen Normally, existing files in

While termplot is under discussion, here's another proposal. I'd like to change the default for partial.resid to TRUE, and for smooth to panel.smooth. I'd be surprised if those changes were to break existing code. John Maindonald email: john.maindonald at anu.edu.au phone : +61 2 (6125)3473 fax : +61 2(6125)5549 Centre for Mathematics & Its Applications, Room

Folks, Kevin Korb wrote: > Have you considered more advanced methods such as subvolume snapshots > provided by ZFS and BTRFS? At work we were forced to abandon rsync > - --link-dest because of the amount of time it takes to delete old > backups when the data is primarily many millions of small files > (shared web hosting company). We don't have more advanced methods like

Hi! I hope you can assist me with this one. We are using version Samba 2.0.3 and are having troubles making the "force group" config option work as expected. To make matters more interesting the file system being samba-shared is mounted from another unix server. To explain: Machine "marvin" (Solaris 2.7) exports /mnt/anthias using (/etc/dfs/dfstab): share -F nfs -o

Hi Rask, I installed the GG ls, as you suggested, and some other directory commands (rm, dir, ..) as well, into amitcp:samba/bin. BIN: is assigned to this. My path looks here first before amitcp:bin. I still get no action for mput *, with recurs on, and mask *. Also, lcd prints nothing as well. Can you suggest anything else? Am I missing something else, perhaps? Cheers, Chris. On 15 Dec 97