Hello, I am very new to rsync and am wanting to have it back up more than 4 remote linux servers via ftp. I want to write a script that will open up a ftp connection using "ftp://username:password@ftp.server.com" with a server, then mount the drive containing the backups, copy the data that is new, unmount the drive, close the connection and move onto the next server until every server is successfully backed up to a external drive on my linux machine which is on my local network. I know that I have to use ssh with the connection to the servers for backup, but where to start is where I am at right now. Here are a couple of noobish questions: 1. Do I have to write my own file from scratch and hope it works? 2. How should I start to write my file in order to have it correlate with backing up multiple servers (syntax, switches, and so on)? If anyone has any advise on how I should start writing my config file, please let me know if you have any suggestions. Thanx, gxr ----- Computers are like air conditioners. They both dont work, if you open windows. -- View this message in context: http://www.nabble.com/Suggestions-for-basic-rsync-configuration-tp16025015p16025015.html Sent from the Samba - rsync mailing list archive at Nabble.com.
Whilst it is possible to write a script to mount FTP and copy the files across. This isn't what is usually done with Rsync. Rsync can be a replacement for FTP client. So it collects a list of altered files between two directories and puts these files into a remote directory. No FTP required. All you need to do is open up a port on your server to the Internet, install Rsync as a server(daemon) on one end and then run Rsync on the source whenever you need to do the backup. The cute thing is that Rsync don't care what platform the source or server is or whether or not it's across a LAN or WAN. Here is a batch line I typically use on Windows for backing up a directory across the Internet. rsync -zav --delete --recursive '/cygdrive/c/sourcedirectory/' username@mydomain.dom::backupdirectory/ Easy. This syncs the source to the backup directory. ie Rsync assumes the source is the 'master'. Once you've got Rsync working, you can then add a SSH layer so the traffic is encrypted. I'd advise getting the basic daemon working first, then on the client PC, issue a Rsync command to list the contents of the remote folder. Once you've got that listing working you know things like firewalls, port forwarding of routers is working. :-) Rsync by default using port 873. But it's easy to change this. Just ensure you do it with the daemon and client. ;-) To list the public remote directories. Rsync domain.dom:: Listing the contents of a directory set up in the daemon confg file is done by: Rsync domain.dom::backup Once you've got the basics, you can then add username and password protection in the confg file. Performing a list of a directory with a username is done like this: Rsync username@domain.dom::backup if a password is required, you're prompted for it. If you want the password auto-inserted, then you set a environmental variable In Windows this is added to the batch file of the client rsync. SET RSYNC_PASSWORD=mypassword A basic daemon conf.cfg file is something like this: ------------------------------------------------------------------------ log file = rsyncd.log pid file = rsyncd.pid use chroot=false uid=administrator gid=administrators charset = utf-8 strict modes = false secrets file =/cygdrive/c/cwrsync/passwordfile [backup] comment=rsync directory path = /cygdrive/c/mybackup/ read only = false transfer logging = yes list=yes #auth users=username ------------------------------------------------------------------------ password file is a list of users and passwords "username:password" on a single line. -- Stuart Halliday -----Original Message----- From: Geofoxer <pete.heiss@gmail.com> To: rsync@lists.samba.org Date: Thu, 13 Mar 2008 05:39:40 -0700 (PDT) Subject: Suggestions for basic rsync configuration> > Hello, > > I am very new to rsync and am wanting to have it back up more than 4 > remote > linux servers via ftp. I want to write a script that will open up a ftp > connection using "ftp://username:password@ftp.server.com" with a > server, > then mount the drive containing the backups, copy the data that is new, > unmount the drive, close the connection and move onto the next server > until > every server is successfully backed up to a external drive on my linux > machine which is on my local network. I know that I have to use ssh > with the > connection to the servers for backup, but where to start is where I am > at > right now. Here are a couple of noobish questions: > > 1. Do I have to write my own file from scratch and hope it works? > 2. How should I start to write my file in order to have it correlate > with > backing up multiple servers (syntax, switches, and so on)? > > If anyone has any advise on how I should start writing my config file, > please let me know if you have any suggestions. > > Thanx, > > gxr > > ----- > Computers are like air conditioners. They both dont work, if you open > windows. > -- > View this message in context: > http://www.nabble.com/Suggestions-for-basic-rsync-configuration-tp16025 > 015p16025015.html > Sent from the Samba - rsync mailing list archive at Nabble.com. > > -- > To unsubscribe or change options: > https://lists.samba.org/mailman/listinfo/rsync > Before posting, read: > http://www.catb.org/~esr/faqs/smart-questions.htmlThis email is the property of ECS Technology Ltd. This company is registered in Scotland with company number 212513. VAT registered GB 761 7456 12 http://www.ecs-tech.com/
Matt McCutchen-7 wrote:> >> ?hosts allow = trusted.hosts > > BTW, the "hosts allow" field needs to contain the actual list of trusted > hosts, not the name of a file holding the list. >So now I have tried the daemon again, and got a password prompt, which is better. I edited the "host allow = *" so that it would allow all hosts. But I tried at first adding the IP Address of my local router, and it didnt work. How can I configure the "hosts allow" field correctly to allow any requests from my network. Here is the error that I got: # rsync -zav <remote-server-ip>::realperson2 /random/file-or-directory Password: @ERROR: auth failed on module realperson2 rsync error: error starting client-server protocol (code 5) at main.c(1383) [receiver=2.6.9] I know that I had the password right, I even checked the rsync.secret file to double check. Do I have to have an actual domain name in order to give access to the daemon, or would putting in a IP Address be ok? ----- Computers are like air conditioners. They both dont work, if you open windows. -- View this message in context: http://www.nabble.com/Suggestions-for-basic-rsync-configuration-tp16025015p16118166.html Sent from the Samba - rsync mailing list archive at Nabble.com.
On Wed 19 Mar 2008, Peter Heiss wrote:> > Now I have a new situation, the linux OS was reinstalled (it crashed after a > bad restart) on the remote linux box where I was working with rsync. I have > reconfigured everything back to the way tit was before and I am now getting > a new error with the following command: > > # rsync -zav --progress <remote-server-ip>:/random/file-or-directory > /random/file-or-directory > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ > @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ > IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! > Someone could be eavesdropping on you right now (man-in-the-middle attack)! > It is also possible that the RSA host key has just been changed.Obviously the host key has changed, as you reinstalled the OS...> Offending key in /root/.ssh/known_hosts:1[...]> again through yast and all that. I have checked "/root/.ssh/known_hosts", > and the folder doesnt exist under the "root" directory. I also installed sslOn the client system? I.e. not the newly reinstalled system? I find that hard to believe. This is a simple ssh issue, nothing to do with rsync. Paul Slootman
I figured out the ssh error. Although I am still unable to connect to the remote host with the rsync daemon. Here is the error that I am getting again: # rsync -zav --progress root@<remote-server-ip>::realperson /random/file-or-directory rsync: failed to connect to <remote-server-ip>: Connection timed out (110) rsync error: error in socket IO (code 10) at clientserver.c(104) [receiver=2.6.9] I have set up the daemon on the remote machine and I have ran "rsync --daemon" to start up the daemon server. I also have enabled the rsync server on the firewall. I also want to restate that I am reconfiguring rsync on a previously new installed system, and the ssh errors are fixed. What am I still missing? ----- Computers are like air conditioners. They both dont work, if you open windows. -- View this message in context: http://www.nabble.com/Suggestions-for-basic-rsync-configuration-tp16025015p16178772.html Sent from the Samba - rsync mailing list archive at Nabble.com.
On Thu 20 Mar 2008, Peter Heiss wrote:> > I figured out the ssh error. Although I am still unable to connect to the > remote host with the rsync daemon. Here is the error that I am getting > again:To clarify: you know that ssh is now not involved, right?> # rsync -zav --progress root@<remote-server-ip>::realperson > /random/file-or-directory > rsync: failed to connect to <remote-server-ip>: Connection timed out (110)A timeout would indicate a firewall problem, the rsync port (873) is probably not allowed. Paul Slootman
Paul Slootman-5 wrote:> >> # rsync -zav --progress root@<remote-server-ip>::realperson >> /random/file-or-directory >> rsync: failed to connect to <remote-server-ip>: Connection timed out >> (110) > > A timeout would indicate a firewall problem, the rsync port (873) is > probably not allowed. >Yes I understand that ssh is not involved anymore here. I opened up the port on the firewall, so that problem is out of the way. The weird thing is that when I use the following command I dont get an error, I only get the timeout when i use the daemon to connect the remote server: # rsync -zav <remote-server-ip>:/random/file-or-directory/ /random/file-or-directory/ Password: With this command I can transfer files without any errors, it works perfectly. But when I use call the daemon on the remote server, it just sits there and does nothing until the connection times out. I haved double checked the firewall and everything is set up the way it should be. here my config files just in case there is something wrong with them (they look right ok to me): uid = root gid = roots read only = true use chroot = true transfer logging = true log format = %h %o %f %l %b log file = /var/log/rsyncd.log hosts allow = * slp refresh = 300 [realperson] path = /srv/www/vhosts/rsync/backup_out comment = Verzeichnis fuer rsync auth users = root secrets file = /etc/rsyncd.secrets Is there anything else that I can do here? [EDIT: I forgot to say that I will not be back until next tuesday. I will get back to this then... Happy Easter!!!] ----- Computers are like air conditioners. They both dont work, if you open windows. -- View this message in context: http://www.nabble.com/Suggestions-for-basic-rsync-configuration-tp16025015p16181496.html Sent from the Samba - rsync mailing list archive at Nabble.com.
On Thu 20 Mar 2008, Peter Heiss wrote:> >> # rsync -zav --progress root@<remote-server-ip>::realperson > >> /random/file-or-directory > >> rsync: failed to connect to <remote-server-ip>: Connection timed out > >> (110) > > > > A timeout would indicate a firewall problem, the rsync port (873) is > > probably not allowed. > > > > Yes I understand that ssh is not involved anymore here. I opened up the port > on the firewall, so that problem is out of the way. The weird thing is thatWell, I must disagree :-) A timeout on one port while another port connects fine is a firewall problem... Maybe the _outgoing_ firewall is the cause?> when I use the following command I dont get an error, I only get the timeout > when i use the daemon to connect the remote server: > > # rsync -zav <remote-server-ip>:/random/file-or-directory/ > /random/file-or-directory/ > Password:So port 22 is allowed to connect, while port 873 is not. Paul Slootman