Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm a super noob with Linux and I wanted to know how to Clone/Ghost a linux install from one server to another (they are pretty much the same hardware, Dell R710s) but I need to make many of them and I don't want to install one by one and setup them up one by one.

What I'm trying to accomplish is to setup and configure 1 server to have it working to where I need it and then clone it to 6 other servers.

Also, what would I need to change on there to make it a separate server, the first thing that comes to mind are the IPs and the Hostname.

Any tips and pointers would be great!

NOTE: I used Paragon Backup & Recovery 2011 last time on one of the servers but it just wouldn't boot from the cloned drive. What could I be missing on this? I'll defenitely look at the suggestions that were sent.

share|improve this question

You should investigate deployment solutions like Chef, Puppet or radmind -- These are all designed to help you make a bunch of servers follow a standard configuration/template.
Both Puppet and Chef are even capable of handling the IP and Hostname bits pretty much out of the box, and examples of usage abound.

share|improve this answer

You should check out Clonezilla, it mimics the workings of Norton Ghost. If you want to just deploy the image without post-configuration for network settings, you could configure your base-image to get all its network settings from a DHCP server.

share|improve this answer
I think I tried Clonezilla, the problem is that since it's a Dell Server it didn't quite work. I'll download the latest and give it a try. – Hondalex Aug 3 '11 at 19:33

Cloning can certainly work although my preference is to investigate the auto-install script option for the OS (Kickstart for RH type systems, AutoYAST for SuSE, I don't recall what the current preferred Debian solution is.) I find it easier in the long run to maintain the auto-installer and post-install scripts which configure the system to the local standard, which incidentally document very exactly how the systems are built so that the next system you install is guaranteed to be built the same way.

Even better is to decide to start with a config management system and not hand-edit files. Then you have a documented and version controlled description of what has been changed from the default system and can easily build or re-build a system to the correct state.

The alternative is to try and remember all the changes or remember to document them separately so that the next time you need to add or replace a system you don't have config regressions and have old problems come back that you forgot about.

share|improve this answer
The preferred solution for automatically installing Debian is the debian installer. – womble Aug 3 '11 at 22:59

Your Answer


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.