I'm using rsync 2.63 on a NetWare 6.5 server backing up various volumes to a
SLES 9 server.
My script that I'm using on the NW server is:
# Rsync synchronisation of APPS
rsync -rRutzvP --volume=apps: ./ 192.168.1.252::SCA/apps
# Rsync synchronisation of DATA
rsync -rRutzvP --volume=Data: ./ 192.1
On Fri, 2006-03-03 at 16:11 +0800, Denis Solovyov wrote:
> Not completely sure, but it seems that making huge rsync'ed
> partitions "noatime" (/etc/fstab) slightly helps as well.
That may help by reducing the amount of atime hits while rsync is
scanning for files and reading files. For reference
Carson Gaspar wrote:
--On Friday, March 03, 2006 9:21 AM -0500 Linus Hicks
Please configure your email client to not quote email addresses...
wrote:
This is certainly not true for the source machine. It typically has 70gb
free (it's still running a 32-bit Oracle database server). The
desti
--On Friday, March 03, 2006 9:21 AM -0500 Linus Hicks <[EMAIL PROTECTED]>
wrote:
This is certainly not true for the source machine. It typically has 70gb
free (it's still running a 32-bit Oracle database server). The
destination machine started out with about 2.8gb free. I will run it
again and
On Fri, Mar 03, 2006 at 06:33:37PM +1100, Craig Hammond wrote:
> Any way of doing this without stopping and restarting it.
One possibility is to setup IP prioritization on your network so that
rsync can use as much free bandwidth as possible until higher priority
packets cause it to slow down.
If
Wayne Davison wrote:
On Fri, Mar 03, 2006 at 09:21:25AM -0500, Linus Hicks wrote:
I'm transferring one file, which is obvious from my command line. Is the
FAQ incorrect?
The FAQ is incomplete in how the size of the file can affect the sender's
memory. If the destination file already exists, t
On Fri, Mar 03, 2006 at 05:56:33AM -0600, Harry Putnam wrote:
> rsync error: some files could not be transferred
> (code 23) at main.c(882) [sender]
>
> How can I determine which files these were?
Look for the error messages that rsync output earlier in the transfer.
They will be easier to see
On Fri, Mar 03, 2006 at 09:21:25AM -0500, Linus Hicks wrote:
> I'm transferring one file, which is obvious from my command line. Is the
> FAQ incorrect?
The FAQ is incomplete in how the size of the file can affect the sender's
memory. If the destination file already exists, the sender needs to b
https://bugzilla.samba.org/show_bug.cgi?id=3579
Summary: Add support for pregenerated directory listings
Product: rsync
Version: 2.6.7
Platform: All
OS/Version: All
Status: NEW
Severity: enhancement
Priority: P3
Linus Hicks wrote:
Wayne Davison wrote:
On Thu, Mar 02, 2006 at 02:07:14PM -0500, Linus Hicks wrote:
I do not understand the exceeding long times shown in the last two
runs.
Since the user/sys CPU time didn't also mushroom, I would suggest that
you check to see if your system ran out of free
Flames invited if I'm wrong on any of this, but:
Some (long overdue) backups indicate that network speed
should be much more important than cpu speed.
Your results will depend heavily on your exact mix
and I cannot think of any reasonable way to quantify it.
That said, this may help give you a clu
Wayne Davison wrote:
On Thu, Mar 02, 2006 at 02:07:14PM -0500, Linus Hicks wrote:
I do not understand the exceeding long times shown in the last two
runs.
Since the user/sys CPU time didn't also mushroom, I would suggest that
you check to see if your system ran out of free memory and started t
When getting this error:
rsync error: some files could not be transferred
(code 23) at main.c(882) [sender]
How can I determine which files these were?
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smar
On Fri, 2006-03-03 08:02:55 +0100, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> // I wonder if this message has been posted, so I sent it again //
It was, but nobody answered yet.
> I'm preparing a plan for a production mode in my company: we need to
> mirror around 100GB of data trough a spe
[EMAIL PROTECTED] wrote:
>Hello,
>
> So: each night, from 0:00am to maximum 7:00am, the server will have to
>check the 100Go of files and see what files have been modified, then,
>upload them to the clients. Each file is around 4MB to 40MB in average.
>
>
Are the clients what you call the "mir
>>> > I'm using rsync for simple daily back up data from one HD to another. It
>>> > takes about 10 minutes daily under "nice -n 19". The problem is
>>> --bwlimit=KBPS limit I/O bandwidth; KBytes per second
MM>> --bwlimit only limits the rate of transfer over the network. V
16 matches
Mail list logo
