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-----
Hash: SHA1

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:/ 
> --exclude={/etc/sysconfig/*,/dev/*,/proc/*,/sys/*,/tmp/*,/run/*,/mnt/*,/media/*,/lost+found,/home/*/.gvfs}
>
> 
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[1] 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[2] project. He should give that a shot. It's extremely
simple config management.


[1]: http://www.systemimager.org/
[2]: http://ansible.github.com/

- --
Derek
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJQInIzAAoJECcWlbcE84qzybwQAINvRcF0uBhAVWYhAjCZTWJk
CvNvRZqa8PV/9uWyDIujDGZRok1kvq0cfhRmsJ8fbZG1fNz7S+XkYt0lZ6nVPr3/
VfbRFMRev+uOCTGK0E1+2Zyf56cfP3fgnI9oNeNoB9Fdbh3DxKBOopb9ECMYwe4a
j3BP+Z+WoM6CiRCv7WlIb/r1/DIXI6WqSAmvPjiGp/qtjicZRWL7pdDjCMy8QokG
RDmazxr9GBvg19HGQIg3Ph4bq7a3MFeq23hc3twb2ZYQhLmfLceGPIeDjwxknU/2
V8dEMSJUYbc5lJmAXdlIwXgLurims69sz3dkhXxN4fg0SGcqiChKXcMIKDpbanKO
z78Y3LktlhOWyIDcz5tBguWu82I1/2mzxmqsLFd8G8F1DIjJAlRGoemmLHjkxDRf
NOaffWOTgH6XSNhvyYRfC+uvKnDrmlUJr5028vDVdczLZeFXBJ03HSF2BQttIY6v
TWkp4L3R97qRnhUinvCOc5C4H5TnTRiWi4t93MmyYtNMC1v8ebyy6LG8ZpFVU+EO
1biO8X2/jzbp8yo1rfH4XGle9qprnBeKjpNU6bieVOs2Z+oMltx+qC7yHBIMzvPh
HmExXv5vPVZ40jKcIi5K3PywDRb7xF7bwI1Hvx5QaxLY5T2aeo6n4w1YJw7XLEF9
ygcKzdxNGtETKxEqnPqF
=PN+O
-----END PGP SIGNATURE-----


More information about the PLUG mailing list