<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.14.1">
</HEAD>
<BODY>
/var/log<BR>
<BR>
useful to back that up for security reasons.<BR>
<BR>
definitely do /etc because if you cock a config up you have something to fall back on.<BR>
<BR>
<BR>
jamie<BR>
<BR>
On Fri, 2007-08-24 at 15:22 +1200, nic wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">Hi people</FONT>
<FONT COLOR="#000000">I have quite a lot to do with a bunch of key Linux servers. I'm not quite responsible for </FONT>
<FONT COLOR="#000000">them, but I do get asked things like 'what should we be backing up?'.</FONT>
<FONT COLOR="#000000">I know the obvious data directories, but I was thinking about the other things that are </FONT>
<FONT COLOR="#000000">less obvious, like /etc, /var/spool/cron, and /usr/local/bin (of course people only put </FONT>
<FONT COLOR="#000000">their dedicated scripts there...)</FONT>
<FONT COLOR="#000000">What else would you experts suggest? Would you bother with /etc, or just take some key files?</FONT>
<FONT COLOR="#000000">I don't think there's a requirement to have a replacement machine up and running in 5 </FONT>
<FONT COLOR="#000000">minutes. I'd expect they'd be happy with a couple of hours to load the OS, restore from </FONT>
<FONT COLOR="#000000">tape (or another machine) and some manual configuration, but it's the references for the </FONT>
<FONT COLOR="#000000">manual configuration, or the raw files so that the amount of configuration can be </FONT>
<FONT COLOR="#000000">minimised, that I'm interested in.</FONT>
<FONT COLOR="#000000">And if it makes any difference to your suggestions, there is a _lot_ of capacity on their </FONT>
<FONT COLOR="#000000">tape system, so the odd 100 Mb here or there doesn't matter too much</FONT>
<FONT COLOR="#000000">All comments appreciated</FONT>
<FONT COLOR="#000000">Nic C-L</FONT>
</PRE>
</BLOCKQUOTE>
</BODY>
</HTML>