I have not learned anything about using a drive image. How does that work and how long would it take use a drive image to configure a new server?
Only as long as it took to copy the image over; modern software squeezes down images quite a bit.
Coincidentally, Sunday evening I was reading the Christmas 2008 issue of
Linux Format; it has an article on
Clonezilla. It's free, Linux-based, and according to the article, it's fast. It doesn't store the entire partition byte-by-byte, but only the parts of the partition that contain data.
Also how does that affect different hard drive sizes?
I haven't studied that yet, but if it works the say it should, then you should be able to define partition sizes and it should know how to handle that. One reason for starting this thread was to get answers to questions like these; hopefully this thread won't just be you and I.
Will it work with software RAID1?
If by no other way certainly you can clone on to one drive and then build the RAID. In fact some Linux distributions do it just that way on installation.
Sorry for the questions but I have no idea how that works. I guess that is why I have never considered.
Learning it will take some time but I think it'll save a lot of time as well.
I had previously considered using a fully configure small drive and using dd to copy it to the drive I am going to use in the server and then extend the partitions. But it just did not seem like it would save me that much time.
I'd only do it if the software could do the expansion. According to the article you can run Clonezilla partition by partition, and it does know enough to use different size partitions. More studying, and testing is obviously required, but since we do a lot to the default OS and the default DirectAdmin distributions (often taking over two hours) it would be worth it to us.
Currently I am using the old customapache so after the install I have to manually upgrade php. I should probably spend some time learning to use custombuild and that will probably save me time.
You should
. We find it makes upgrading a lot simpler and a lot faster.
What I didn't like about custombuild was the different httpd configuration files. I had become used to using one main config file and then all the user's config files. Custombuild makes it harder for me to find things since now I don't know what file a particular configuration is. I hate learning something new just to be able to do the same thing that I have always done.
I agree; I like the monolithic file myself. But I've learned my way around, and now I'm used to it.
Jeff