cloning running linux machine through network, strategy and tactics
Derek Carter (aka goozbach)
goozbach at friocorte.com
Wed Aug 8 08:05:39 MDT 2012
-----BEGIN PGP SIGNED MESSAGE-----
On 08/07/2012 04:49 PM, Ryan Byrd wrote:
> Linux Friends:
> Picture this: a "friend of mine" just set up a redhat linux machine
> running a website with apache/php/etc. It took a long time to get
> everything just right.
> Goal: He'd like so-called clone this live-running machine's files
> to a new freshly installed clean redhat linux machine so he doesn't
> have to repeat the effort. He wants two webservers all set up
> whereas he has only one presently.
> He's imagining something like this:
> [root at CurrentlyRunningServer ~]$ rsync -ave ssh --delete /*
> root at NewServer:/
Doing rsync manually is always asking for trouble. Luckily your
"friend" isn't the first to think of this idea. Prior to getting
proper configuration management in place in a past job I used the tool
called systemimager which is built for *EXACTLY* this use case. It
uses rsync on the back end and works around all the corner cases
you're probably gonna miss.
If I wasn't able to convince him to run proper configuration
management, I'd suggest the systemimager route.
However, configuration management has gotten much simpler lately with
the Ansible project. He should give that a shot. It's extremely
simple config management.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----END PGP SIGNATURE-----
More information about the PLUG