Backup Central

I was wondering if anyone can help. Myself and colleagues have been
struggling with this amanda problem for a couple of weeks now and we
dont seem to be no where near resolving it. We thought you may beable to
enlighten us!

Bascially the daily backups on hostname: tsssun1 (Solaris 8
machine)appears to be failing. I've set up two slices on the disk for
the data before it flushes it to tape:

/dev/dsk/c0t2d0s0 17408538 15 17234438 1% /amanda
/dev/dsk/c0t3d0s0 35006272 29 34656181 1% /amanda1



They write to disk but do not flush to tape. When I run an amflush on
it, it says that there are no files to flush. Also the /amanda and
/amanda1 partitions dont clear themselves up afterwards. Problem is,
this seems to be happening on different days (ie: one Monday it'll fail
and the next Monday it'll succeed - using the same tapes) I checked the
/tmp/ambackup_Daily.log file and it gave me about 10 lines of the error
below:

/tmp/ambackup_Daily.log
Use of uninitialized value at /opt/amanda/sbin/amstatus line 868.


/opt/amanda/sbin/amstatus

elsif($dump_finished{$hostpart} == 1 &&

$taper_started{$hostpart} != 1) {
if( defined
$opt_waittaper ) {
printf "%8s ",
$datestamp if defined $opt_date;
printf
"%-${maxnamelength}s%2d", "$host:$partition", $level{$hostpart};
printf "%9dk",
$size{$hostpart};
print " dump
done";
if( defined
$starttime ) {
print "
(", &showtime($dump_time{$hostpart}), ")";
}
print ", wait
for writing to tape\n";
}




If there are errors from the night before, or if I have to do an amflush
then I normally run an amcleanup Daily and then kill off all Amanda
processes that are currently running. IS this correct? should I be
killing off all processes or should there be some running in order for
the following nights backup to succeed?

Also any ideas on why this is happening intermittantly?

A confused amanda user:

- Ranveer





________________________________________________________________________

Tertio Telecoms (www.telco-tertio.com)

Head Office: One Angel Square Torrens Street London EC1V 1PL
Tel: +44 (0)20 7843 4000 - Fax: +44 (0)20 7843 4001

Bath Office: Riverside Buildings 108 Walcot Street Bath BA1 5BG
Tel: +44 (0)1225 478000 - Fax: +44 (0)1225 478001

Munich Office: Freisinger Strasse 10, 85737 Ismaning/Munich, Germany,
Tel: +49 (0)89 665506 41 - Fax: +49 (0)89 665506 99

Any views expressed in this message are those of the individual sender,
except where the sender specifically states them to be the views of Tertio Ltd.

This email has been scanned by the MessageLabs Email Security System.
________________________________________________________________________

Ranveer Attalia wrote:

Bascially the daily backups on hostname: tsssun1 (Solaris 8
machine)appears to be failing. I've set up two slices on the disk for
the data before it flushes it to tape:

/dev/dsk/c0t2d0s0 17408538 15 17234438 1% /amanda
/dev/dsk/c0t3d0s0 35006272 29 34656181 1% /amanda1

If I understand it, these are defined as holdingdisk?



They write to disk but do not flush to tape. When I run an amflush on
it, it says that there are no files to flush. Also the /amanda and
/amanda1 partitions dont clear themselves up afterwards. Problem is,

Can you show an 'ls -l' of those disks? Before and after the flush.


this seems to be happening on different days (ie: one Monday it'll fail
and the next Monday it'll succeed - using the same tapes) I checked the
/tmp/ambackup_Daily.log file and it gave me about 10 lines of the error
below:

Actually it's the first time I hear of "/tmp/ambackup_Daily.log".
It's probably created by your home-made backup script that invokes
amanda.
Can you show us that script? (Or mail it to me personally, if you like.)


/tmp/ambackup_Daily.log
Use of uninitialized value at /opt/amanda/sbin/amstatus line 868.

I wonder what "amstatus" is doing in that home-made script...
I use amstatus only interactivily.
Also, what version of amanda is this?


/opt/amanda/sbin/amstatus
elsif($dump_finished{$hostpart} == 1 &&
[...]
print ", wait
for writing to tape\n";

Is that a quote of the contents of /tmp/ambackup_Daily.log? or did
you quote (without linenumbers) the part around line 686 in the mail?


If there are errors from the night before, or if I have to do an amflush
then I normally run an amcleanup Daily and then kill off all Amanda
processes that are currently running. IS this correct? should I be
killing off all processes or should there be some running in order for
the following nights backup to succeed?

Why are there running amanda processes? And what are they doing?
Personnally, I would first kill them, and then run amcleanup, in that
order. (Actually first finding out what they doing!)


--
Paul Bijnens, Xplanation Tel +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUM Fax +32 16 397.512
http://www.xplanation.com/ email: Paul.Bijnens < at > xplanation.com
***********************************************************************
* I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, *
* quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, *
* PF4, F20, ^X^X, :, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, *
* kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... *
* ... "Are you sure?" ... YES ... Phew ... I'm out *
***********************************************************************