Hello Hendrik and thanks for your patience in explanations ;-)
> Again:
>
> 1) rsync -e ssh /local/path user@remoteserver:/remote/path
> This will use *SSH* authentication to setup the connection,
> and then access the filesystem using user's rights.
>
> 2) rsync /local/path rsync://remoteser
Hello again...
> > I have to say that on a similar setup, I'm succeeding with
> the command
> > I told you before.
>
> Then you are using the rsync daemon method, and you will have
> to check on the server side to allow access without passwords
> in /etc/rsyncd.conf, or make use of the enviro
Hello Hendrik and thanks for your reply.
> "rsync rsync://host" is different from "rsync -e ssh path host:/path"
>
> using ssh, you want the 2nd form
I have to say that on a similar setup, I'm succeeding with the command I
told you before.
I think I have to go a bit deeper in details: I'm using
Hello everybody.
I got a strange problem, which I hope to solve with your help.
I'm doing "remote backups" using rsync in an ssh tunnel. In the last
setup I realized, something is driving me crazy and I can't find *what*
the problem is.
I managed to successfully login via ssh in a "passwordless"
2009/11/4 henri :
>
>> rsync -ahzv --delete --progress --numeric-ids --ignore-errors
>> "/Users/bonny/Music/iTunes Music"
>> "rsync://r...@192.168.1.100/musica/iTunes Music"
>
>
> I am guessing that your iTunes Music folder is well 50MB. As such, testing
> with a smaller directory will reduce the t
2009/10/31 Matt McCutchen :
> On Sat, 2009-10-31 at 17:06 +0100, Boniforti Flavio wrote:
>> I'm almost getting exhausted, thus I have to bother you people to get some
>> help.
>
> That's a non sequitur. Check
> http://www.catb.org/~esr/faqs/smart-questions.html#
Hello list.
I'm almost getting exhausted, thus I have to bother you people to get some help.
I simply want to sync my "iTunes Music" folder from my MacBook over to my NAS.
The scenario is like this:
source path: "/Users/bonny/Music/iTunes/iTunes Music/" (in here there
are all the subfolders I wa
> I'm coming back to this issue, which I did not have time to
> go on further...
>
> One of the DSL lines has been ugpraded:
>
> Before = 5000/500
> Actual = 2/1000
[cut]
> The conclusion is, there seems to be a "fixed timeout" which
> happens at constant times. What can I do now? OK, I'
> This looks like an application is running where the backup is
> to be made. The application opens and locks the files
> with an exclusive lock and the rsync program must then wait
> until it is freed by the application or times out.
>
> This is a typical problem under Windows. Can you ask th
> All right, so it's a timeout. That means either the rsync
> protocol deadlocked (which would constitute a bug) or the
> network lost data. To determine which, please run all three
I'm coming back to this issue, which I did not have time to go on
further...
One of the DSL lines has been ug
Hy people, where could this be coming from?
rsync: send_files failed to open "Alfredo Polti
SA/wz_ALFREDO_POLTI_SA.ac0" (in Winway_z-32): Device or resource busy
(16)
rsync: send_files failed to open "Alfredo Polti
SA/wz_ALFREDO_POLTI_SA.ac3" (in Winway_z-32): Device or resource busy
(16) rsync er
> You are missing rsync's output to stderr. There should be at
> a minimum "rsync error: error in rsync protocol data stream
> (code 12)", and probably a preceding error message that would
> give us an idea of what the problem is. Adjust your setup so
> you can capture the stderr, or if all e
> No, rsync's post-transfer checksum will catch the corruption,
> and rsync will redo the transfer. IOW, rsync is designed to
> recover from false block matches, except that false matches
> in a compressed transfer can cause a fatal error by throwing
> the -z protocol out of sync.
So, Matt, w
> That is just the error code and its interpretation. What
> error message comes prior to that?
This is the whole log:
/usr/bin/rsync -rtzv --port=8873 --delete --ignore-errors --numeric-ids
\
--delete-excluded --stats --progress localhost::Carlo/ \
/mnt/remote/Customer/daily.0/Carlo/
Hello there,
is it a known issue/problem with rsync transferring big files (let's say
over 0,5 GB)? I'm using "rsync -rtz" to transfer over an SSH tunnel and
I always get
12 Error in rsync protocol data stream
Any suggestions on how to solve this? Maybe removing "z" compression
could be helping?
> This question has been answered. Upgrade to 3.0.5 on both sides.
Why has upgrading to 3.0.5 to be done *on both sides*? Any explanation?!
As I'm running Debian Lenny (which has 3.0.3), do I have to switch to
Debian Sid to get it upgraded?
Thanks,
Flavio Boniforti
PIRAMIDE INFORMATICA SAGL
Via
> You should not use -z at ALL with large numbers of small
> files. The increased latency of the
> compression/decompression will far exceed any time saved in
> transmission. You're not on a 300 baud modem, I assume?
> -z should be used when you are sending large files that are
> compressib
> It would help if you gave the command used.
> The opendir refers to a module name "Profili", but without
> knowing if you're syncing to or from the module I can't say
> whether it's source or destination.
Yes, of course you're right.
The module "profili" is the remote server which I'm syncing
Hello list.
I've got following:
rsync: opendir "client05" (in Profili) failed: Permission denied (13)
rsync: delete_file: rmdir(client02/SendTo) failed: Permission denied
(13)
Am I correct if I say that the "opendir" is related to the source I'm
trying to rsync, but the "delete_file" is related
Hello there,
I'm transferring with rsnapshot in an SSH tunnel data from a remote
Windows 2003 SBS Server to my Linux Server. While transferring a
3GB-File, I get:
2009/02/23 23:32:37 [3888] rsync: writefd_unbuffered failed to write
4092 bytes [sender]: Connection reset by peer (104)
2009/02/23 23
Hello list.
I'm doing nightly syncs over SSH with rsnapshot, and now rsync gives me
strange errors, like:
rsync: failed to connect to localhost: Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(122)
[receiver=3.0.3]
-
Hello list.
I'm posting here although I'm actually running rsync from within
rsnapshot, but the problem is really rsync-related.
I've set up remote backups: remote client to backup from is Windows
Server 2003 with sshd and rsyncd running, local server is Debian Linux
(Lenny) with rsnapshot config
On 6/2/07, Matt McCutchen <[EMAIL PROTECTED]> wrote:
> How should I be setting "uid" and "gid" in the server's conf file?
You should set both to root so that the server (more properly called a
daemon) has the power to set the ownership of the backup files.
Otherwise, the daemon will silently ski
Hello there...
I'd like to have some doubts cleared out... therefore I'm posting here...
I want to back-up my PC's /home directory onto another Linux PC. On
the "server" I've set up a directory called /backup and now I'd like
to know which permissions it should have for that my backups succeed.
24 matches
Mail list logo
