Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I have 3 servers of exactly the same configuration. Is it possible to install linux on 1 exactly the way I want it, then clone over the installation? What would be the problems with doing this?

share|improve this question
    
What distribution of Linux are you referring you in this case? –  Rilindo Jun 14 '11 at 15:58

2 Answers 2

You should take a look at some Config Management systems. I suggest using Puppet or CFengine

What these allow you to do is define a system state on a master node, and then propogate this state onto other box's. For example you can define that each node should have package X, Y and Z, with a certain directory structure and specific files/users/configuration. Then the master will continually enforce this state onto all of its nodes. This requires some time to setup and configure properly but it can work wonders. There is a tool called Blueprint that will allow you to map out a running system and export it into a puppet recipe (or its own internal thing).

You could also just clone the HD's into another HD using Norton Ghost or Clonezilla but as MadHatter mentioned you might run into issues.

share|improve this answer
    
If this were truly a one-time deal, I've used SystemImager successfully for this. But realistically, Puppet or a similarly modern competitor to Cfengine would be the way to go long-term. For me, currently, imaging is for disaster recovery, unattended installation is for initial OS installs, and Puppet is for everything else. –  Mike Renfro Jun 14 '11 at 15:16

The usual big problems arise when details of the source system's hardware have been embedded in config files. These include network interface config files (which often have MAC addresses embedded in them), md RAID config files (which often have the UUIDs of physical devices in them) and modprobe.conf and similar files (that often have links between hardware-specific kernel modules and the various NICs, HDD controllers, etc. that they refer to).

There can also be issues with licence keys for proprietary software, which are often designed to be tied to hardware. But you weren't running any nasty proprietary software, were you? (grin)

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.