On Wed, Oct 19, 2011 at 3:54 AM, David Lee David.Lee@ecmwf.int wrote:
Dan White wrote:
I am looking for a way to preserve a server configuration for disaster recovery purposes.
Is there a way to "dump" the contents/configuration of a cobbler server such that it can be used as command line input to rebuild/duplicate the server ?
The report output has all the necessary information, but it is not in the same form as it would be when being entered on the command line.
Thanks. [...]
We're new to cobbler, but are developing something resembling this (using 2.0.11 at present).
But first a little detour into how we might view Disaster Recovery (DR).
<detour> </detour>
So don't think in terms of setting up a cobbler server. Rather consider setting up a cobbler service comprising two (or more) actual servers, and day-by-day keeping those server components in step with each other, and configuring clients to use them both. (Or if you have to have a single IP, then regularly switch that day-by-day hosting-IP of your service between the servers.)
The basic technology to keep multiple cobbler servers in step is "cobbler replicate".
(And we're supplementing that with a "configuration management" tool which itself configures and maintains those multiple cobbler servers. But that detail is outside scope of the cobbler-specific question.)
Cobbler replicate is definitely the way to go, or if you use some kind of SAN replication like SRDF you can store all of your data on a replicated LUN.