I exclude the amanda dir from the rest of the backup, set it up so that 
the amanda dir is a DLE, always full, no record or index, starttime is 
when I'm sure all the other backups are done. This can have amanda report 
very long Run Time & Dump Time as it will include the time waiting for 
0700 to come around after the rest of the dumps have finished. If needed, 
I can pull it off the tape in the usual amanda DR way just using standard 
UNIX/Linux tools. It will be the very last DLE recorded.


mrdds2 /usr/local/etc/amanda {
 swcomp
 program "GNUTAR"
 record no
 index no
 dumpcycle 0
 starttime 0700
}


-----------------------------------------------------
toby bluhm
philips medical systems, cleveland ohio
tobias.bluhm AT philips DOT com
440-483-5323








Guy Dallaire <clepeterd AT gmail DOT com> 
Sent by:
owner-amanda-users AT amanda DOT org
11/10/2005 03:33 PM

To
"Amanda (E-mail)" <amanda-users AT amanda DOT org>
cc

Subject
is excluding /usr/local/var/amanda a bad idea ?
Classification







I excluded /usr/local/var/amanda from my amanda server backup because 
amanda was complaining a lot about strange backups (the indexes and db 
were updated while amanda was running tar on them, or something like that)

I'm realizing that if I lose this directory for some reason (ex: destroy 
the db or index directories by error) I will no longer be able to use 
amrecover and get a list of the backups that are on a particular tape. Or 
restores will be a lot more difficult, until I go through a complete 
dumpcycle.

Say you lose the amanda indexes and db, is there some sort of way to 
rebuild it from the tapes ? Or a way to know what files (and last modified 
date) are on which tapes ?

Thanks