Hello,
since Saturday (2008-05-31) my ananda backup didn't run.
A closer look when I run the command /usr/sbin/amstatus DailyFull get me
this output:
Day '31' out of range 1..30 at /usr/sbin/amstatus line 1148
using /var/lib/amanda/DailyFull/log/amdump.1 from Sa Mai 21 15:30:08
CEST
I coudn't
A bug in amstatus should not prevent your backup to run correctly.
Changing amdump.1 can't help to start a backup run (amdump).
Your backup should run correctly even if amstatus crash.
Can you send me a copy of the bogus amdump.1 file? I would like to look
at it.
Which locale are you using?
Hi,
I've now gotten as far as getting Amanda to think the tape drive has 2
slots (I believe)...well at least I can do an amcheck successfully...
One question:
When amdump runs and fills up the first tape, what should I expect to
see?
Does Amanda simply eject the first tape and just waits
On Wed, Jun 4, 2008 at 11:04 AM, Johan Booysen [EMAIL PROTECTED] wrote:
One question:
That's *three* questions ;)
When amdump runs and fills up the first tape, what should I expect to
see?
Does Amanda simply eject the first tape and just waits until the second
tape is inserted?
Does it
Ah, ok - but this would only apply to version 2.6, like Jean-Louis said?
I'm using the 2.5.0 RHEL5 version of Amanda. We tend to stick to
installing official Red Hat packages...
I'm running a test amdump, so will see what happens.
Thanks very much for the replies.
Johan
-Original
In 2.5.0, it write a message to /dev/tty, if you start the command from
an interactive shell, you should see a message, if you run it from cron,
then the message is lost.
Newer version allow to send an email message.
Jean-Louis
Johan Booysen wrote:
Hi,
I've now gotten as far as getting
Hello Jean-Louis,
Am Mittwoch, den 04.06.2008, 09:34 -0400 schrieb Jean-Louis Martineau:
A bug in amstatus should not prevent your backup to run correctly.
Changing amdump.1 can't help to start a backup run (amdump).
Your backup should run correctly even if amstatus crash.
Can you send me a
