On 01/05/2011 05:39 PM, Max Schubert wrote:
While a live back up is definitely a good idea, if you start storing
your configuration tree in a version control system off server - CVS,
GIT, SVN, any other one you choose - then the back up issue on the
live server only becomes one of backing up
On 01/05/2011 05:39 PM, Max Schubert wrote:
While a live back up is definitely a good idea, if you start storing
your configuration tree in a version control system off server - CVS,
GIT, SVN, any other one you choose - then the back up issue on the
live server only becomes one of backing up
Greetings,
I would like to backup Nagios. I'm imagining rsyncing the files to
another server that runs a backup job to tape each night.
I'm on Ubuntu 10.04 and used it's package management system to install
Nagios, so this isn't a compiled version.
I'm not exactly sure where all the Nagios
What it really comes down to is exactly *what* you want to back up. If
it's just the configuration, then the stuff in /etc should be all you
need. The stuff in /var will contain the current state (logs, lock
files, status.dat, etc.). The things in /usr should only be things that
are
On 01/05/2011 01:10 PM, Tony Yarusso wrote:
What it really comes down to is exactly *what* you want to back up. If
it's just the configuration, then the stuff in /etc should be all you
need. The stuff in /var will contain the current state (logs, lock
files, status.dat, etc.). The things in
While a live back up is definitely a good idea, if you start storing
your configuration tree in a version control system off server - CVS,
GIT, SVN, any other one you choose - then the back up issue on the
live server only becomes one of backing up retention.dat, which has
changes you / your users
