Some of the files show something like this. The lines saying 'rm' don't
look good, like the current backups remove the ones from previous days.
I forgot to mention that the last backup's index is always there. But
when the next backup does it's thing, it's gone and replaced by the next
one.
This one is called amtrmidx.20031005004325.debug: (i.e., 2003-10-05).
This was a Sunday, and the files it's mentioning on the 'rm' lines are
the last backups from the previous Thursday (two backups prior).
There are no cron jobs. There is actually two configurations, one doing
full backups on sundays and then differential backups during the week
(tuesday - friday mornings). This backup on Sunday was NOT put to tape.
The Full backups, on sundays, does record to /etc/dumpdates. The other
backups, during the week, do not. Not sure if this is related. Perhaps
is /etc/dumpdates somehow tied in?
Right now, being tuesday, only have this mornings and sundays backup
indexes on disk. If i notice any other behavior (such as it stays until
the weekend. I have friday's as well, which seems to make sense as
Friday was a day that wasn't put to tape.
amtrmidx: debug 1 pid 9330 ruid 33 euid 33: start at Sun Oct 5 00:43:25
2003
/usr/lib/amanda/amtrmidx: version 2.4.3
tiger /novell/home
rm /local/amanda/var/index/tiger/_novell_home/20031002_1.gz
tiger /novell/Loans
rm /local/amanda/var/index/tiger/_novell_Loans/20031002_1.gz
tiger /novell/FinancialCircuit
rm /local/amanda/var/index/tiger/_novell_FinancialCircuit/20031002_1.gz
tiger /novell/DATA
rm /local/amanda/var/index/tiger/_novell_DATA/20031002_1.gz
tiger /novell/POINT
rm /local/amanda/var/index/tiger/_novell_POINT/20031002_1.gz
tiger /usr/cvs_root
amtrmidx: pid 9330 finish time Sun Oct 5 00:43:27 2003
On Tue, 2003-10-07 at 14:13, Paul Bijnens wrote:
> Tomas Maly wrote:
> > The index files for use with amrecover don't exist except for
> > non-flushed backups. I look in the directory that's set as the 'index
> > directory' in amanda.conf as well.
> >
> > amrecover is useless otherwise.
> >
> > Is this normal? I want to use amrecover to browse all backups on
> > current tapes. "index yes" is set for all backups, and they ARE there
> > for the non-flushed. they are at random days apart, so it's entirely
> > because I forgot to change the tape.
>
> No this is not normal. They do exist on my server, and they are
> useful for amrecover
>
> What is your tapecycle?
> Is that "index" directory shared with something else?
> A cron job that runs apart from amanda and is supposed to clean
> up but does too much?
> Any hints what's going on/going wrong in the debug files:
> a/tmp/amanda/amtrmidx.timestamp.debug ?
>
> --
> Paul
--
Tomas Maly <tomas_maly AT financialcircuit DOT com>
|
