Hard Drive "cloning" (linux) and HD config for ser

  • champi0n
  • Graduate
  • Graduate
  • User avatar
  • Posts: 199

Post 3+ Months Ago

First my main problem is im using an old 6gig drive which is now starting to fail (or rather it says cannot handle request - is what some of the errors say) and shuts down. This happens once, maybe twice in a 24 hour time period.

What i want to do is "clone" that drive to another 40 gig drive. As so i don't have to re-install and reconfigure everything.

Is there software for this? Or could i do it manually by configuring the partitions on the 40 gig, then copy everything from my current /hda1 to my new /hda1 and it should work fine?

-------------------

secondly, what would be the ideal HD config for a non-raid server?

my config is the 6gig holds my OS and its services, while a 200gig is mounted under the directory that holds all my hosted websites. Obviously im upgrading the old crap 6gig to something better... but is that type of configuration "good" or would the one 200gig be just as good or better?

also, is 512DDR better then say 1gig of PC133? (since the DDR is way faster i dont know if its better to have less faster ram, or more slower ram)


Thanks for your help/input.
  • Anonymous
  • Bot
  • No Avatar
  • Posts: ?
  • Loc: Ozzuland
  • Status: Online

Post 3+ Months Ago

  • this213
  • Guru
  • Guru
  • User avatar
  • Posts: 1260
  • Loc: ./

Post 3+ Months Ago

The "right" way to handle this is to actually reinstall and reconfigure everything - as you're trying to avoid.

DO NOT just copy everything from your old drive to the new drive in the manner you specify. If you do this, the best that will happen is you'll only be able to access 6 gigs on your 40 gig drive.

Depending on the services (and what versions they're at as opposed to the new versions you're going to install), you'll *probably* be able to just copy the configuration files over.

There's no such thing as an "ideal HD config for a server" because just about every server operates differently. Generally speaking, mount your drives with "noatime", format them to segregate writable and non-writable portions (an then mount those non-writable portions read only)

The more drives you have your system spread across, the better (to a point). The reason for this is simple, each drive head can only be in one position across all the platters at any given moment. This means that even if you have your system partitioned out correctly, you can only read or write to/from one partition at a time, whereas if you have two drives, they can both be operated on simultaneously. This is true whether you're using RAID or not.

More core (RAM) is always better than faster core. Even though DDR is faster than PC1xx, it's still about a hundred times slower than the processor. Once you're physical RAM space fills up, data that needs to be stored has to be written to the hard drive - which is what swap space is for. The more your system has to resort to the swap space, the slower it gets because that effectively slows the memory access times down to hard drive speeds which are about a hundred times slower than volitile core (RAM). So, on the issue of RAM, I'd take a 1gig PC133 system over a 512MB DDR system any day. Besides that, RAM is so cheap, I couldn't actually justify buying a 512MB chip anyway.

Since you're even asking the question of whether to use DDR or PC133, that means that you either have a k6 or k7 board (or thereabouts in Pentium numbers) that has the option of using both, or you're looking at upgrading your motherboard. If either of these is the case, throw that out (or relegate it to firewall duty) and get yourself something with a 64 bit processor. I say this mainly because you state that you're pushing web sites - which means you're probably using MySQL and Postgres, which both run better on 64 bit systems (because they both have native 64 bit code which has to be "translated" for 32 bit systems).

If you have the resources to do so, build a new system apart from the current server and make sure everything works the way it's supposed to, then just copy the web sites and databases over and have it take over for your current server. You're already talking about replacing the hard drive and RAM so you might as well just do the whole thing. You can usually build a decent 64 bit server from the ground up for less than $600 US these days (and you've already spent $200 of that).


my $.02

Post Information

  • Total Posts in this topic: 2 posts
  • Users browsing this forum: No registered users and 84 guests
  • You cannot post new topics in this forum
  • You cannot reply to topics in this forum
  • You cannot edit your posts in this forum
  • You cannot delete your posts in this forum
  • You cannot post attachments in this forum
 
cron
 

© 1998-2014. Ozzu® is a registered trademark of Unmelted, LLC.