We are moving our lyris server over to our new server. At this time our old server is still up where we have the files. But it could be shut off at the end of the day today or who knows when. We did not renew our contract. So I have this 511 MB that we have been trying to upload to our server. The thing is either it is too big of a file or something but it won't complete the send.

So we are down to this alternative. Burning the file onto a cd and then shipping it overnight to the datacenter to be placed on the system. Since this server is at efree if we ask for any support then it costs a ton of money. So how can I get this file from the CD onto my machine. It is a Red Hat Linux 7.1 server I believe is what is installed.

Or if I can still get to my old flies is there a way to use wget, but of course I need instructions on how to install and use it, but I thought maybe we could do that.

Suggestions/Advice?

I ran into the same problem, with it just not wanting to send that huge file.

run a ftp server on your computer

use wget on the server and grab it
wget ftp://user:pass@yourip:port/path/filename.exe

Are you trying to go from server to server? Who are you going to-from? Can you download it to your machine and then upload to the new machine?

That is what we tried to do. I downloaded a copy of it from the originail server and then to my local machine. Then tried to connect to my new server (west coast) it sent about 110 GB of 511 GB of the file before it gave an error saying that it could not send the file

I have been able to mount my cdrom on my server from the command line, the only problem is I don't have a cd in it. But I am hoping since I can access the cd rom from the command line that I can just copy the file that way.

At this time I think we have access to the old server and the new server, so does that help in any way or give me an option.

Shawn

Edit: I found this article helpful in determing the cd rom and the other hardware on the server. Someone else might find this useful also

http://www.linuxfocus.org/English/September1999/article106.html

110GB? 511GB? If youre talking that much transfer, you should save money and fedex the drives rather than transfer that over the internet. You will be paying a lot to transfer that much.

its mb not gb

Figured that but he typed it twice in the above post...

By any chance, when you try to FTP it, do you use a particular user name on the new server? If so, you may want to check your /home/user_name, whether the quota is not somehow set at 110MB or something ...

I have done transfer of 400MB files and it worked fine. It did give me problem at first (stop after 100MB) but it was because I use an account with 100MB quota set for it ...

Just my two cents ...

cheers,
:beer:

Originally posted by dektong
By any chance, when you try to FTP it, do you use a particular user name on the new server? If so, you may want to check your /home/user_name, whether the quota is not somehow set at 110MB or something ...

I have done transfer of 400MB files and it worked fine. It did give me problem at first (stop after 100MB) but it was because I use an account with 100MB quota set for it ...

Just my two cents ...

cheers,
:beer:

I transfer ISO's around all the time from here to there to over yonder.

I use Zmodem a lot of the time, it's handy when you're in a shell and want a file uploaded or download, just sz filename and I get it locally. Or use the Zmodem transfer queue in SecureCRT and upload it.

Sounds kinda like a quota problem the original poster is having. There's no reason except for quota or disk space that I can think of to stop him moving that file.

the problem isnt a quota problem
it has happend to me before on my server

I could not upload a big file constantly (it was 3gb)
it stopepd at like 600mb

Trust me, there were no quotas.

I had to setup an FTP server, and then wget it from the shell, it worked fine, never stoped, never slowed down, didtn disconnect.

I really can't explain WHY exactly this problem occurs when uploading a big file through your FTP client, but it just does for some resaon

But i know that if you setup a ftp server, (temporarily) and wget it, it will work! :D

The 110MB stopping point could also be a limit problem. do a ulimit -a and see what the entry for max file size is. We've been bitten by this one ourselves.

Chris

Does this help?

[root@gagsplus bestofhumor]# ulimit -a
core file size (blocks) 1000000
data seg size (kbytes) unlimited
file size (blocks) unlimited
max locked memory (kbytes) unlimited
max memory size (kbytes) unlimited
open files 1024
pipe size (512 bytes) 8
stack size (kbytes) 8192
cpu time (seconds) unlimited
max user processes 2048
virtual memory (kbytes) unlimited


We did ship a CD out there overnight, I am hoping that I am able to just copy the files directly from the CD that I made and upload it to a directory. Just have to figure out exactly how we can do it.

And who knows what will happen since @home CAN shut down tonight. I am using comcast which uses Excite @ home

If you have ssh access scp is a cool... :)
scp as the name suggests is secure copy.

Have a great day :)

regards
amar

presuming it is your own server.

Telnet or SSH old-server

su root

tar czf backup.tar /old/server/htdocs

ftp new-sever

bin

put backup.tar

close

exit

exit

telnet or ssh new-server

su root

tar xzf backup.tar

mv -f /current/htdocs/dircetory /current/htdocs/dircetory_tmp

mv -f your /old/server/htdocs /current/htdocs/dircetory

I've done this several times and it works fine every time.