-*-text-*-
$Header: /CVSROOT/public/scylla-charybdis/md5backup/doc/full_backup.txt,v 1.1 2004/05/09 20:57:48 tino Exp $

How to do a backup:
===================

PLEASE NOTE THAT METADATA IS NOT BACKED UP FOR NOW!  FYI: If you don't
know what metadata is (file flags and such) md5backup is not for you.
md5backup is for experienced system administrators, those who know.

Local backup:     bin/dobackup.sh
Networked backup: see doc/sc-backup.txt

How to do a full backup:
========================

md5backup always runs incremental, so it does not know how to do a
full backup.  The closest thing to a full backup is, when you delete
the database (dbm file, usually in /backup/md5backup/dbm/).

The database is binary data, and thus you cannot look at it easily.
Therefore I consider it to be something, which must not be important
to md5backup.  If you delete the database, it is re-created on the
next run.

In this case md5backup has to closely examine all files on your hard
drive.  This takes a long time, and as the files in the file store are
compared byte by byte with the files from your hard drive, this even
takes longer than a full backup.

No, it's not a real compare run, but close to it.  A real compare run
would behave like a restore, but there is no restore yet.

See doc/restore.txt for more on restores.

-Tino
$Log: full_backup.txt,v $
Revision 1.1  2004/05/09 20:57:48  tino
added