diff options
Diffstat (limited to 'sag-0.6.1-www/Invisible/sag-0.6/node104.html')
| -rw-r--r-- | sag-0.6.1-www/Invisible/sag-0.6/node104.html | 45 |
1 files changed, 45 insertions, 0 deletions
diff --git a/sag-0.6.1-www/Invisible/sag-0.6/node104.html b/sag-0.6.1-www/Invisible/sag-0.6/node104.html new file mode 100644 index 0000000..8191564 --- /dev/null +++ b/sag-0.6.1-www/Invisible/sag-0.6/node104.html @@ -0,0 +1,45 @@ +<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> +<!--Converted with LaTeX2HTML 96.1-h (September 30, 1996) by Nikos Drakos (nikos@cbl.leeds.ac.uk), CBLU, University of Leeds --> +<HTML> +<HEAD> +<TITLE>What to back up</TITLE> +<META NAME="description" CONTENT="What to back up"> +<META NAME="keywords" CONTENT="sag"> +<META NAME="resource-type" CONTENT="document"> +<META NAME="distribution" CONTENT="global"> +<LINK REL=STYLESHEET HREF="sag.css"> +</HEAD> +<BODY LANG="EN" > + <A NAME="tex2html1625" HREF="node105.html"><IMG WIDTH=37 HEIGHT=24 ALIGN=BOTTOM ALT="next" SRC="./next_motif.gif"></A> <A NAME="tex2html1623" HREF="node96.html"><IMG WIDTH=26 HEIGHT=24 ALIGN=BOTTOM ALT="up" SRC="./up_motif.gif"></A> <A NAME="tex2html1617" HREF="node103.html"><IMG WIDTH=63 HEIGHT=24 ALIGN=BOTTOM ALT="previous" SRC="./previous_motif.gif"></A> <A NAME="tex2html1627" HREF="node1.html"><IMG WIDTH=65 HEIGHT=24 ALIGN=BOTTOM ALT="contents" SRC="./contents_motif.gif"></A> <A NAME="tex2html1628" HREF="node114.html"><IMG WIDTH=43 HEIGHT=24 ALIGN=BOTTOM ALT="index" SRC="./index_motif.gif"></A> <BR> +<B> Next:</B> <A NAME="tex2html1626" HREF="node105.html">Compressed backups</A> +<B>Up:</B> <A NAME="tex2html1624" HREF="node96.html">Backups</A> +<B> Previous:</B> <A NAME="tex2html1618" HREF="node103.html">Multilevel backups</A> +<BR> <P> +<H1><A NAME="SECTION001160000000000000000">What to back up</A></H1> +<P> + You want to back up as much as possible. The major exception + is software that can be easily reinstalled,<A NAME="tex2html51" HREF="footnode.html#3001"><IMG ALIGN=BOTTOM ALT="gif" SRC="./foot_motif.gif"></A> but even they may have configuration + files that it is important to back up, lest you need to do + all the work to configure them all over again. Another major + exception is the <tt>/proc</tt><A NAME="3089"> </A> filesystem; since that only + contains data that the kernel always generates automatically, + it is <em>never</em> a good idea to back it up. Expecially + the <tt>/proc/kcore</tt><A NAME="3091"> </A> file is unnecessary, since it is just + an image of your current physical memory; it's pretty large + as well. +<P> + Gray areas include the news spool, log files, and many other + things in <tt>/var</tt><A NAME="3093"> </A>. You must decide what you consider + important. +<P> + The obvious things to back up are user files (<tt>/home</tt><A NAME="3095"> </A>) and + system configuration files (<tt>/etc</tt><A NAME="3097"> </A>, but possibly other things + scattered all over the filesystem). +<P> +<BR> <HR> +<P><ADDRESS> +<I>Lars Wirzenius <BR> +Sat Nov 15 02:32:11 EET 1997</I> +</ADDRESS> +</BODY> +</HTML> |