[TAG] Backup software/strategies

Kapil Hari Paranjape kapil at imsc.res.in
Sun Jul 15 07:57:36 MSD 2007


Hello,

On Sat, 14 Jul 2007, Rick Moen wrote:
> If you make sure every backup set has a catalougue of currently
> installed package names, then that plus locally generated files are
> literaly all that need be backed up.  Here is a complete list of
> directories that _do_ need backing up, on my server:

I would add the following to Rick's list:

	/var/lib/dpkg		Saves a lot of config info (alternatives, diverts, ...)
				which "dpkg --get-selections" misses out on.
	-/var/lib/dpkg/info	Leave out the really large subdirectory
				which contains no information not in the packages
	/var/cache/debconf	Keep all the debconf answered questions
	/var/lib/aptitude	Saves the package dependency choices

One also needs to consider the (usually minor) problems that may occur
if a package on the crashed system was out-of-date. When restoring
from the upstream Debian archive or CD, this package would be replaced
by a newer version.

On the whole I prefer to have at least one "mondo" style backup of
the system which gets me to a familiar working environment even while
one is trying to bring the dead back to life. With external bootable
USB this is quite feasible.
(This is a shameless plug for my article in LG #140!)

Regards,

Kapil.
--






More information about the TAG mailing list