Copying this site to the new server now. It's bigger than I thought. I think I'll put it up on the new server (leaving the "real" site where it is for now) just to get a handle on all the steps involved in migrating.
I wasn't able to get the whole thing yesterday because I didn't understand enough. My connection is so flakey on this end that my terminal sessions kept disconnecting before the copy would finish. But with a little googling I discovered the unix utility 'screen'. Wow. Very cool. It's like virtual desktops - but inside your terminal session.
I ssh into the new server (ash) and there I invoke 'screen'. Now I get a new prompt on ash (this is the 'virtual' terminal session on ash.) From there I do my copy:
scp -1rq -l 256 username@tulip.example.net:/home/username/public_html/
/home/username/dmt2/
Now if my ssh session to ash gets disconnected, the scp copy just continues on it's way. Then I can reconnect over ssh to ash and this time I type 'screen -r' and it reconnects me to the virtual session I started inside of screen the first time.
And I could even ssh to ash from a totally different host and reattach the old screen session. Very slick.
Also this is my first real use of scp. I had been using sftp, but scp looks better in some instances. The switches on scp are as follows: -1 is forcing ssh protocol version 1; the -r is copying recursively through any lower directories; the -q is making it quiet (didn't really need that); and the '-l 256' is limiting the bandwidth to 256 kb/s since ash has a lot more bandwidth than tulip and I don't want to blow tulip's 95th out of the water.
Anyway, copying now. There are a *lot* of images on tulip. I had no idea. You guys are crazy.
Yeah, I passed 2000 some time in the last month or so.
All in the 25-100KB range, of course.
I like it, don't get me wrong. And there is *plenty* of space on the new server. ;-)
That took a long time at 256 kb/s, but finally got all 1.5 gigs of it.
|
- jim 2-14-2006 11:29 pm
I wasn't able to get the whole thing yesterday because I didn't understand enough. My connection is so flakey on this end that my terminal sessions kept disconnecting before the copy would finish. But with a little googling I discovered the unix utility 'screen'. Wow. Very cool. It's like virtual desktops - but inside your terminal session.
I ssh into the new server (ash) and there I invoke 'screen'. Now I get a new prompt on ash (this is the 'virtual' terminal session on ash.) From there I do my copy:
Now if my ssh session to ash gets disconnected, the scp copy just continues on it's way. Then I can reconnect over ssh to ash and this time I type 'screen -r' and it reconnects me to the virtual session I started inside of screen the first time.
And I could even ssh to ash from a totally different host and reattach the old screen session. Very slick.
Also this is my first real use of scp. I had been using sftp, but scp looks better in some instances. The switches on scp are as follows: -1 is forcing ssh protocol version 1; the -r is copying recursively through any lower directories; the -q is making it quiet (didn't really need that); and the '-l 256' is limiting the bandwidth to 256 kb/s since ash has a lot more bandwidth than tulip and I don't want to blow tulip's 95th out of the water.
Anyway, copying now. There are a *lot* of images on tulip. I had no idea. You guys are crazy.
- jim 2-15-2006 7:32 pm
Yeah, I passed 2000 some time in the last month or so.
- tom moody 2-15-2006 7:48 pm
All in the 25-100KB range, of course.
- tom moody 2-15-2006 7:50 pm
I like it, don't get me wrong. And there is *plenty* of space on the new server. ;-)
- jim 2-15-2006 8:39 pm
That took a long time at 256 kb/s, but finally got all 1.5 gigs of it.
- jim 2-16-2006 6:36 pm