https://bugzilla.samba.org/show_bug.cgi?id=5887
Summary: RFE: --link-any-dest option considers contents only,
ignores name
Product: rsync
Version: 3.1.0
Platform: All
OS/Version: All
Status: NEW
Severity:
>LBackup is not intended for large scale deployment, unless used in
>combination with some sort of file system management tool.
If you are backing up up client machines, chances are that their
configuration will be changing in the near future. In addition, there are
may be different operating sys
You could setup the backups of the 200 clients. However, it would be
easier to setup the backup of a couple of file servers? That would
simplify the situation. Then you can say to people that If you file is on
the server then it is backed up.
If you want to backup the data on 200 client machines y
On Mon, 2008-11-10 at 09:57 -0600, Steve Bergman wrote:
> In the 3.0.4 version of the man pagem dated June 29, 2008, it still
> states:
>
> """
> (5) the efficiency of rsync’s delta-transfer algorithm may be reduced if
> some data in the destination file is overwritten before it can be copied
> to
Thomas von Eyben wrote:
Should it be a problem to have it backup 200 clients to a couple of
xraids (perhaps to be changed to an xsan).
If these 200 clients are going to have a lot of file changes between
the backup periods, then I'd say you may run into issues of the backup
never finishin
On Mon, Nov 10, 2008 at 12:25 PM, Henri S <[EMAIL PROTECTED]> wrote:
>>1. delete the oldest backup (.7)
>>2. Increment all the other backups +1
>> (.6 -> .7, .5 -> .6, .4 -> .5, .3 -> .4, and .2 -> .3)
>>3. Create a hard link between .1 -> .2
>>4. Run rsync from the source int
On Mon, 2008-11-10 at 10:59 -0700, Ashley M. Kirchner wrote:
> Matt McCutchen wrote:
> > By the way, if some of your excludes are intended to match only files at
> > the top level of F: (rather than in a subdirectory), consider anchoring
> > them with a leading slash, e.g.:
> Can I assume that
Matt McCutchen wrote:
Not really. The leading slash would require the pattern to match the
entire path of the file starting from the source directory (here
"/cygdrive/f", i.e., "F:\"). For example, your current exclude rule
"- Temporary Items" would match both "F:\Temporary Items" and
"F:\Foo\B
On Sat, Nov 01, 2008 at 08:29:38AM -0400, Matt McCutchen wrote:
> You are right, the combination of -K, --delete and incremental recursion
> is broken.
I've committed Matt's fix for this into the git repository for both
3.0.5 (which is about to get a new pre-release) and 3.1.0 (the
enhancement bra
Matt McCutchen wrote:
(My boss' last name is the same as yours.)
--delete-excluded prevents the --exclude="Network Trash Folder" rule
from protecting the "Network Trash Folder" on the destination from
deletion; that's the whole point of --delete-excluded.
Aha! No wonder ...
To protect
In the 3.0.4 version of the man pagem dated June 29, 2008, it still
states:
"""
(5) the efficiency of rsync’s delta-transfer algorithm may be reduced if
some data in the destination file is overwritten before it can be copied
to a position later in the file
"""
Also, I know I have read somewhere
>1. delete the oldest backup (.7)
>2. Increment all the other backups +1
> (.6 -> .7, .5 -> .6, .4 -> .5, .3 -> .4, and .2 -> .3)
>3. Create a hard link between .1 -> .2
>4. Run rsync from the source into .1
This is esentially what LBackup is doing.
The LBackup project also
12 matches
Mail list logo
