RE: Dump not running

2001-01-16 Thread Nathan Bird

I will give chg-manual a go.. however here are the system details.

Tape Drive - Sony DDS TLS-S9000 ( it has an auto changer built in, which
uses an 8 tape holder stacker type layout )
OS - Redhat Linux 6.2
Amanda Version - Amanda-2.4.1p1

If you would like any more information I should be able to provide it...

but as I said I'll give the manual changer a try too.

Nathan

-Original Message-
From: Bort, Paul [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, 17 January 2001 2:29
To: 'Nathan Bird'; '[EMAIL PROTECTED]'
Subject: RE: Dump not running


Does it behave better if you change your changer to 'chg-manual'? It looks
kind of like it's trying to talk to a non-existent changer. If you provide
more information about your hardware (drive type, changer type) and software
(OS and AMANDA Version), that would help too.

-Original Message-
From: Nathan Bird [mailto:[EMAIL PROTECTED]]
Sent: Monday, January 15, 2001 10:18 PM
To: '[EMAIL PROTECTED]'
Subject: Dump not running


Hi,

Whenever I run 'amcheck' I get

[root@paperbark sbin]# ./amcheck hlink-data2
Amanda Tape Server Host Check
-
/usr/local/amanda/dumps: 1900471 KB disk space available, that's plenty.
amcheck-server: slot 8: date 20010112 label hlink-data12 (first labelstr
match)
NOTE: skipping tape-writable test.
Tape hlink-data12 label ok.
Server check took 6.004 seconds.

Amanda Backup Client Hosts Check

Client check: 1 host checked in 0.565 seconds, 0 problems found.

(brought to you by Amanda 2.4.1p1)


which to me would appear as though the dump is going to run correctly,
however the cronjob that I have set up for amdump never actually runs.

I have tried changing my disklist to only backup the /tmp directory and this
appears to run fine, but if I try to backup my /user directory 'amdump'
never appears to finish.

so i tried to run amverify and it just does this

[root@paperbark sbin]# ./amverify hlink-data2  
Tape changer is chg-multi...
1 slot...
Verify summary to root
Defects file is /tmp/amverify.24428/defects
amverify hlink-data2
Tue Jan 16 14:14:28 EST 2001

Loading current slot...
Using device 
aborted!for device to go ready...
cat: /tmp/amverify.24428/tapelist: No such file or directory

and I eventually have to push ctrl-c to stop it, it nevers becomes 'ready'

what should I be looking at to try and work out what is happening

cheers

Nathan



RE: Dump not running

2001-01-16 Thread Bort, Paul

Does it behave better if you change your changer to 'chg-manual'? It looks
kind of like it's trying to talk to a non-existent changer. If you provide
more information about your hardware (drive type, changer type) and software
(OS and AMANDA Version), that would help too.

-Original Message-
From: Nathan Bird [mailto:[EMAIL PROTECTED]]
Sent: Monday, January 15, 2001 10:18 PM
To: '[EMAIL PROTECTED]'
Subject: Dump not running


Hi,

Whenever I run 'amcheck' I get

[root@paperbark sbin]# ./amcheck hlink-data2
Amanda Tape Server Host Check
-
/usr/local/amanda/dumps: 1900471 KB disk space available, that's plenty.
amcheck-server: slot 8: date 20010112 label hlink-data12 (first labelstr
match)
NOTE: skipping tape-writable test.
Tape hlink-data12 label ok.
Server check took 6.004 seconds.

Amanda Backup Client Hosts Check

Client check: 1 host checked in 0.565 seconds, 0 problems found.

(brought to you by Amanda 2.4.1p1)


which to me would appear as though the dump is going to run correctly,
however the cronjob that I have set up for amdump never actually runs.

I have tried changing my disklist to only backup the /tmp directory and this
appears to run fine, but if I try to backup my /user directory 'amdump'
never appears to finish.

so i tried to run amverify and it just does this

[root@paperbark sbin]# ./amverify hlink-data2  
Tape changer is chg-multi...
1 slot...
Verify summary to root
Defects file is /tmp/amverify.24428/defects
amverify hlink-data2
Tue Jan 16 14:14:28 EST 2001

Loading current slot...
Using device 
aborted!for device to go ready...
cat: /tmp/amverify.24428/tapelist: No such file or directory

and I eventually have to push ctrl-c to stop it, it nevers becomes 'ready'

what should I be looking at to try and work out what is happening

cheers

Nathan