20Likes
LinkBack URL
About LinkBacks
if your box is set up to allow fxp you will need this program here: Wing FTP Server - Secure FTP Server software for Windows and LinuxOriginally Posted by hybridx3
;
We are the best invite forum on the internet! Here you will find free invites, free seedboxes, free bonuses, and much more. Our members know the true meaning of sharing and have created a truly global bittorent community! Our site has the most up to date information on all private trackers and our members will guide you and introduce you to this truly secretive and enlightened club. Ready to get started? Register now!
if your box is set up to allow fxp you will need this program here: Wing FTP Server - Secure FTP Server software for Windows and Linux
;
pgmoney, thanks for the tutorial. I may need to transfer files soon, so this is great help.
Edit: I have CuteFTP Pro, is there any reason why I couldn't use it? I did a google search and it stated that it has the option to do server to server.
But of course, I am interested in the best and fasted solution.
Last edited by maverick2001; November 19th, 2011 at 05:31 PM.
This is a good tutorial, although not all seedboxes support FXP. I found out the hard way. When i upgraded my 100mbit box to a faster 1gigabit box i wanted to transfer all my files to the new box. Insinctively i went for FXP, and found out by constant error messages that my boxes dont support FXP (seednet.eu) So I had to use Putty to transfer the files via rsync, which was a pain in the ass to finally get it to work properly, now i got all files transfer from one box to another. Only thing with rsync is that i do not know a command to be able to view what speed the files are transferring at. I dont think they are going that fast which is unusual but it seems to be taking quite a while to transfer the files. Anyone familiar with rsync, if u have any tips i'd appreciate it.
There is a really easy way using scp that has not been mentioned...
If you put all the files and folders you want to copy over to a different server into one folder then use use scp to copy that single folder to save typing..
eg.
The above assumes:-scp -r ~/copythis john@111.11.6654:/home/john/
1. The folder to copy to the other server is called 'copythis'
2. The user on the other server is called 'john'
3. The server of the other ip is '111.11.6654'
4. The 'copythis' folder is in your home folder.
5. You want to copy to /home/john/ on the other server.
(change these values as required)
You should do this in the SSH of the server where the folder is and it will ask you for the password for the other user.
Last edited by Kitkatra; January 26th, 2012 at 01:40 PM.
This method worked great for me and the server to server transfer is wickedly fast. I transferred some 50gb of data from one box to my new one in a few minutes. Much easier than the whole making a new torrent and re-downloading hassle.
Took some experimenting to get the transfer to work, but eventually it successfully transferred with both servers set on passive mode with auth tls connection protocol. No doubt it'll be different in each situation, but it might help if you're having difficulty to try what I did.
Last edited by ko10; March 29th, 2012 at 01:52 PM.
This came up for me when I moved to a new seedbox a while back. I found the easiest way was just to install an ftp client on the new box and ftp directly from the old box to the new one.
"The strength to change what I can, the inability to accept what I can't, and the incapacity the tell the difference."
This is the best way. I always found FXP leaves alot of 99% torrents, when you try to reload them in the new server. SCP dont seem to cause this problem.
Remember you can also copy your .session folder, just remove the rtorrent.lock file else rtorrent will not start up.
rsync -avhP --stats --times «dir» «target-host»:
PotUK Recruiter
FXP is the way forward when moving things from box to box.
Any good torrent host will have FXP enabled on their FTP servers, any very good torrent host will have SFTP protocol allowed on their FXP as well as their FTP, its quick, clean and no nonsense.
Absolutely disagree with this statement. FXP is the WORST way to move forward here, and any smart host will have FXP off by default. Having FXP enabled on a server opens MAJOR security holes in said server. That being said any smart provider will either turn FXP on temporarily per the users request, or explain to the user how to use SCP, which is by far the most secure and reliable method of transferring files. FXP is a FTP protocol, and as such has much higher data loss rates, especially when transferring large amounts of data. SCP will almost always max out the possible connection between servers, will run recursively, and will not lose or corrupt data as FXP will. SCP is also a linux protocol and so there is no need to enable anything, its there, and as long as you have a user account via SSH on the server you can user it, no questions asked. It also requires all of one line of code to move everything you need.
If you really need to transfer stick with SCP, which you can find many resources on by Googling it. FXP is just a disaster waiting to happen.
And just as a side note, there is no such thing as FXP over SFTP. Again FXP is a FTP related method of transfer between two servers, where as SFTP is actually a SSH method of file transfer, the two are unrelated and not interchangeable or able to be used together.
Last edited by DarkSlider; April 4th, 2012 at 08:13 AM.
Posting Permissions
Reply With Quote
