| 7:29 am on Apr 26, 2011 (gmt 0)|
I guess you need CURL or similar.
| 7:39 am on Apr 26, 2011 (gmt 0)|
What about logging on to the first server with SSH and starting an SFTP session to the second?
| 7:44 am on Apr 26, 2011 (gmt 0)|
I am very new to linux commands or SSH. can you please elaborate a bit :(
| 8:00 am on Apr 26, 2011 (gmt 0)|
SSH is a protocol which allows to to login to a text command prompt on one of the remote servers. This allows you to start commands directly on that server. If your desktop is not Linux based, you will need a terminal emulation prgram to create that connection.
On the remote server you can use the SFTP command to transfer files from one server to the other. SFTP is a command line tool which allows you send files from one of the servers to another.
| 7:38 am on May 30, 2011 (gmt 0)|
SFTP is just like FTP if you've ever used it, just secure
| 2:43 pm on May 30, 2011 (gmt 0)|
If you are using SSH you can scp files as well
scp local/file/path/here username@server_name_or_ip:/location/to/copy/to
If I want to copy a file to example.com
scp /home/test/thefile.xml email@example.com:/tmp/
If I want to copy a file from example.com
scp firstname.lastname@example.org:/tmp/thefile.xml /home/test/
| 3:19 pm on May 30, 2011 (gmt 0)|
I use 'scp' (secure copy) to copy files. Just like copy, but encrypted and between two servers. It's the only thing I use, never use FTP because I don't run ftp on my machines.
You may also want to add the -C switch, which compresses the file. That can speed things up a bit. i.e. copy file1 from server1 to server2, on server1:
scp -C /home/user/file1 email@example.com:/home/user
You must have ssh running on server2 to make this work though.
If you want to automate the copying, say through a cron job running on server1 (so it copies files every night) you may want to use rsync instead of scp. rsync is like scp, but adds the capability of only copying over changed files, thus reducing bandwidth. I use rsync to automate copying my webserver backups to an offsite machine. Full details here:
The important part in that post is setting up the public keys so that server1 can log into server2 without getting prompted for a userid/password. However the same thing works for scp as well - if you set up the keys as noted in that post, then server1 can scp or ssh (or rsync) to server2 without a password request.