Re: [Bacula-users] Problem adding a new tape drive

2008-01-11 Thread Arno Lehmann
Hi,

11.01.2008 00:50, Jerry Lowry wrote:
> 
> 
> I have been trying to add another tape drive to my server.  These are 
> not in
> 
> an autochanger, they are separate tape drives.  I can access the tape 
> drive from
> 
> Linux with mt and as you will see in the documentation below btape 
> worked as
> 
> well.  But when I try to access the tape from bacula it does not see it.
> 
> I thought I had the configuration setup correctly but I must have missing
> 
> something.  I need another "pair" of eyes to look at the SD and DIR config.
> 
>  
> 
> thanks
> 
> ---
> 
> label
> 
> The defined Storage resources are:
> 
>  1: File
> 
>  2: Quantum-DLT-V4
> 
>  3: Quantum-DLT-V4-1
> 

It shows up here, so I suppose you reloaded the DIR configuration. But...

> 3999 Device "Quantum-DLT-1" not found or could not be opened.

... the SD doesn't know about this device.

> Label command failed for Volume distress-mon0208.
> 
> Do not forget to mount the drive!!!
> 
>  
> 
> st stor
> 
> The defined Storage resources are:
> 
>  1: File
> 
>  2: Quantum-DLT-V4
> 
>  3: Quantum-DLT-V4-1
> 
> Select Storage resource (1-3): 3
> 
> Connecting to Storage daemon Quantum-DLT-V4-1 at 
> distress.ACCOUNTING.EDT.LOCAL:9103
> 
>  
> 
> distress-sd Version: 2.0.3 (06 March 2007) i686-pc-linux-gnu redhat (Zod)
> 
> Daemon started 09-Jan-08 11:52, 11 Jobs run since started.
> 
>  Heap: bytes=19,491 max_bytes=152,863 bufs=84 max_bufs=103
> 
>  
> 
> Running Jobs:
> 
> No Jobs running.
> 
> 
> 
>  
> 
> Jobs waiting to reserve a drive:
> 
> 
> 
>  
> 
> Terminated Jobs:
> 
>  JobId  LevelFiles  Bytes   Status   FinishedName
> 
> ===
...
> 
> 
>  
> 
> Device status:
> 
> Device "FileStorage" (/backupdb/backup) is not open.
> 
> Device "Quantum-DLT" (/dev/nst0) is mounted with 
> Volume="distress-010908" Pool="Default"
> 
> Total Bytes=32,169,424,896 Blocks=498,657 Bytes/block=64,512
> 
> Positioned at File=36 Block=0
> 
> 

You probably didn't restart the SD after the configuration change.
reload only reloads the DIR config, FD and SD have to be restarted 
after a configuration change.

...

> bacula-sd.conf
> 
>  
> 
> Device {
> 
>   Name = Quantum-DLT  # First tape – daily and weekly
> 
>   Drive Index = 0
> 
>   Media Type = DLT-V4
> 
>   Archive Device = /dev/nst0
> 
>   AutomaticMount = no;   # when device opened, read it
> 
>   AlwaysOpen = yes;
> 
>   RemovableMedia = yes;
> 
>   RandomAccess = no;
> 
>   AutoChanger = no
> 
>  
> 
> Device {
> 
>   Name = Quantum-DLT-1# Second tape – monthly and 
> yearly
> 
>   Drive Index = 1
> 
>   Media Type = DLT-V4
> 
>   Archive Device = /dev/nst1
> 
>   AutomaticMount = no;   # when device opened, read it
> 
>   AlwaysOpen = yes;
> 
>   RemovableMedia = yes;
> 
>   RandomAccess = no;
> 
>   AutoChanger = no
> 
>  
> 
> ***bacula-dir.conf-  storage device section
> 
...
> Storage {
> 
>   Name = Quantum-DLT-V4-1
> 
> #  Do not use "localhost" here
> 
>   Address = distress.ACCOUNTING.EDT.LOCAL# N.B. Use a 
> fully qualified name here
> 
>   SDPort = 9103
> 
... and it's time to change the passwords :-)

>   Device = Quantum-DLT-1   # must be same as Device in Storage 
> daemon
> 
>   Media Type = DLT-V4  # must be same as MediaType in 
> Storage daemon
> 
> #  Autochanger = yes   # enable for autochanger device
> 
> }

Otherwise, the configuration looks good.

Arno

-- 
Arno Lehmann
IT-Service Lehmann
www.its-lehmann.de

-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] Problem adding a new tape drive

2008-01-10 Thread John Drescher
> I have been trying to add another tape drive to my server.  These are not in
>
> an autochanger, they are separate tape drives.  I can access the tape drive
> from
>
> Linux with mt and as you will see in the documentation below btape worked as
>
> well.  But when I try to access the tape from bacula it does not see it.
>
> I thought I had the configuration setup correctly but I must have missing
>
> something.  I need another "pair" of eyes to look at the SD and DIR config.
>
>
>

I am confused your status st shows that bacula does see the drive.
What do you mean by this? You can not run jobs on Quantum-DLT-V4-1?

John

-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] Problem adding a new tape drive

2008-01-10 Thread Ryan Novosielski
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Jerry Lowry wrote:
> I have been trying to add another tape drive to my server.  These are not in
> 
> an autochanger, they are separate tape drives.  I can access the tape
> drive from
> 
> Linux with mt and as you will see in the documentation below btape worked as
> 
> well.  But when I try to access the tape from bacula it does not see it.
> 
> I thought I had the configuration setup correctly but I must have missing
> 
> something.  I need another "pair" of eyes to look at the SD and DIR config.
> 
>  
> 
> thanks

What gives with the Quantum-DLTV4-1 vs. Quantum-DLT-1?

> ---
> 
> label
> 
> The defined Storage resources are:
> 
>  1: File
> 
>  2: Quantum-DLT-V4
> 
>  3: Quantum-DLT-V4-1
> 
> Select Storage resource (1-3): 3
> 
> Enter new Volume name: distress-mon0208
> 
> Defined Pools:
> 
>  1: Default
> 
>  2: Monthly
> 
> Select the Pool (1-2): 2
> 
> Connecting to Storage daemon Quantum-DLT-V4-1 at
> distress.ACCOUNTING.EDT.LOCAL:9103 ...
> 
> Sending label command for Volume "distress-mon0208" Slot 0 ...
> 
> 3999 Device "Quantum-DLT-1" not found or could not be opened.
> 
> Label command failed for Volume distress-mon0208.
> 
> Do not forget to mount the drive!!!
> 
>  
> 
> st stor
> 
> The defined Storage resources are:
> 
>  1: File
> 
>  2: Quantum-DLT-V4
> 
>  3: Quantum-DLT-V4-1
> 
> Select Storage resource (1-3): 3
> 
> Connecting to Storage daemon Quantum-DLT-V4-1 at
> distress.ACCOUNTING.EDT.LOCAL:9103
> 
>  
> 
> distress-sd Version: 2.0.3 (06 March 2007) i686-pc-linux-gnu redhat (Zod)
> 
> Daemon started 09-Jan-08 11:52, 11 Jobs run since started.
> 
>  Heap: bytes=19,491 max_bytes=152,863 bufs=84 max_bufs=103
> 
>  
> 
> Running Jobs:
> 
> No Jobs running.
> 
> 
> 
>  
> 
> Jobs waiting to reserve a drive:
> 
> 
> 
>  
> 
> Terminated Jobs:
> 
>  JobId  LevelFiles  Bytes   Status   FinishedName
> 
> ===
> 
>   1800  Incr20211.02 G  OK   09-Jan-08 19:24 Futility
> 
>   1801  Incr114995.0 M  OK   09-Jan-08 20:07 Denial
> 
>   1802  Incr174266.9 M  OK   09-Jan-08 21:07 nestucca
> 
>   1803  Incr4471.864 G  OK   09-Jan-08 22:10 Bagby
> 
>   1804  Full 35,51215.28 G  OK   09-Jan-08 22:41 Destruction
> 
>   1805  Full  0 0   Other09-Jan-08 23:11 Doom
> 
>   1806  Incr  1,3491.758 G  OK   10-Jan-08 08:47 Gloom
> 
>   1807  Incr663777.3 M  OK   10-Jan-08 08:49 Distress
> 
>   1808  Full  1162.4 M  OK   10-Jan-08 08:49 BackupCatalog
> 
>   1809  Full  0 0   Cancel   10-Jan-08 14:43 Doom
> 
> 
> 
>  
> 
> Device status:
> 
> Device "FileStorage" (/backupdb/backup) is not open.
> 
> Device "Quantum-DLT" (/dev/nst0) is mounted with
> Volume="distress-010908" Pool="Default"
> 
> Total Bytes=32,169,424,896 Blocks=498,657 Bytes/block=64,512
> 
> Positioned at File=36 Block=0
> 
> 
> 
>  
> 
> In Use Volume status:
> 
> distress-010908 on device "Quantum-DLT" (/dev/nst0)
> 
> 
> 
>  
> 
> [EMAIL PROTECTED] bin]# btape -c /usr/local/bacula/bin/bacula-sd.conf 
> /dev/nst1
> 
> Tape block granularity is 1024 bytes.
> 
> btape: butil.c:286 Using device: "/dev/nst1" for writing.
> 
> btape: btape.c:368 open device "Quantum-DLT-1" (/dev/nst1): OK
> 
> *test
> 
> I'm going to write 1000 records and an EOF
> 
> then write 1000 records and an EOF, then rewind,
> 
> and re-read the data to verify that it is correct.
> 
>  
> 
> This is an *essential* feature ...
> 
>  
> 
> btape: btape.c:825 Wrote 1000 blocks of 64412 bytes.
> 
> btape: btape.c:499 Wrote 1 EOF to "Quantum-DLT-1" (/dev/nst1)
> 
> btape: btape.c:841 Wrote 1000 blocks of 64412 bytes.
> 
> btape: btape.c:499 Wrote 1 EOF to "Quantum-DLT-1" (/dev/nst1)
> 
> btape: btape.c:850 Rewind OK.
> 
> 1000 blocks re-read correctly.
> 
> Got EOF on tape.
> 
> 1000 blocks re-read correctly.
> 
> === Test Succeeded. End Write, rewind, and re-read test ===
> 
>  
> 
>  
> 
>  The test ran through without errors...only copied first part for
> brevity
> 
>  
> 
> bacula-sd.conf
> 
>  
> 
> Device {
> 
>   Name = Quantum-DLT  # First tape ? daily and weekly
> 
>   Drive Index = 0
> 
>   Media Type = DLT-V4
> 
>   Archive Device = /dev/nst0
> 
>   AutomaticMount = no;   # when device opened, read it
> 
>   AlwaysOpen = yes;
> 
>   RemovableMedia = yes;
> 
>   RandomAccess = no;
> 
>   AutoChanger = no
> 
>  
> 
> Device {
> 
>   Name = Quantum-DLT-1# Second tape ? monthly and yearly
> 
>   Drive Index = 1
> 
>   Media Type = DLT-V4
> 
>   Archive Device = /dev/nst1
> 
>   AutomaticMount = no;   # when device opened, read it
> 
>   AlwaysOpen = yes;
> 
>   RemovableMedia = yes;
> 
>   RandomAccess

[Bacula-users] Problem adding a new tape drive

2008-01-10 Thread Jerry Lowry
I have been trying to add another tape drive to my server.  These are not in

an autochanger, they are separate tape drives.  I can access the tape drive
from

Linux with mt and as you will see in the documentation below btape worked as

well.  But when I try to access the tape from bacula it does not see it.

I thought I had the configuration setup correctly but I must have missing

something.  I need another "pair" of eyes to look at the SD and DIR config.

 

thanks

 

 

---

label

The defined Storage resources are:

 1: File

 2: Quantum-DLT-V4

 3: Quantum-DLT-V4-1

Select Storage resource (1-3): 3

Enter new Volume name: distress-mon0208

Defined Pools:

 1: Default

 2: Monthly

Select the Pool (1-2): 2

Connecting to Storage daemon Quantum-DLT-V4-1 at
distress.ACCOUNTING.EDT.LOCAL:9103 ...

Sending label command for Volume "distress-mon0208" Slot 0 ...

3999 Device "Quantum-DLT-1" not found or could not be opened.

Label command failed for Volume distress-mon0208.

Do not forget to mount the drive!!!

 

st stor

The defined Storage resources are:

 1: File

 2: Quantum-DLT-V4

 3: Quantum-DLT-V4-1

Select Storage resource (1-3): 3

Connecting to Storage daemon Quantum-DLT-V4-1 at
distress.ACCOUNTING.EDT.LOCAL:9103

 

distress-sd Version: 2.0.3 (06 March 2007) i686-pc-linux-gnu redhat (Zod)

Daemon started 09-Jan-08 11:52, 11 Jobs run since started.

 Heap: bytes=19,491 max_bytes=152,863 bufs=84 max_bufs=103

 

Running Jobs:

No Jobs running.



 

Jobs waiting to reserve a drive:



 

Terminated Jobs:

 JobId  LevelFiles  Bytes   Status   FinishedName 

===

  1800  Incr20211.02 G  OK   09-Jan-08 19:24 Futility

  1801  Incr114995.0 M  OK   09-Jan-08 20:07 Denial

  1802  Incr174266.9 M  OK   09-Jan-08 21:07 nestucca

  1803  Incr4471.864 G  OK   09-Jan-08 22:10 Bagby

  1804  Full 35,51215.28 G  OK   09-Jan-08 22:41 Destruction

  1805  Full  0 0   Other09-Jan-08 23:11 Doom

  1806  Incr  1,3491.758 G  OK   10-Jan-08 08:47 Gloom

  1807  Incr663777.3 M  OK   10-Jan-08 08:49 Distress

  1808  Full  1162.4 M  OK   10-Jan-08 08:49 BackupCatalog

  1809  Full  0 0   Cancel   10-Jan-08 14:43 Doom



 

Device status:

Device "FileStorage" (/backupdb/backup) is not open.

Device "Quantum-DLT" (/dev/nst0) is mounted with Volume="distress-010908"
Pool="Default"

Total Bytes=32,169,424,896 Blocks=498,657 Bytes/block=64,512

Positioned at File=36 Block=0



 

In Use Volume status:

distress-010908 on device "Quantum-DLT" (/dev/nst0)



 

[EMAIL PROTECTED] bin]# btape -c /usr/local/bacula/bin/bacula-sd.conf /dev/nst1

Tape block granularity is 1024 bytes.

btape: butil.c:286 Using device: "/dev/nst1" for writing.

btape: btape.c:368 open device "Quantum-DLT-1" (/dev/nst1): OK

*test

I'm going to write 1000 records and an EOF

then write 1000 records and an EOF, then rewind,

and re-read the data to verify that it is correct.

 

This is an *essential* feature ...

 

btape: btape.c:825 Wrote 1000 blocks of 64412 bytes.

btape: btape.c:499 Wrote 1 EOF to "Quantum-DLT-1" (/dev/nst1)

btape: btape.c:841 Wrote 1000 blocks of 64412 bytes.

btape: btape.c:499 Wrote 1 EOF to "Quantum-DLT-1" (/dev/nst1)

btape: btape.c:850 Rewind OK.

1000 blocks re-read correctly.

Got EOF on tape.

1000 blocks re-read correctly.

=== Test Succeeded. End Write, rewind, and re-read test ===

 

 

 The test ran through without errors...only copied first part for brevity

 

bacula-sd.conf

 

Device {

  Name = Quantum-DLT  # First tape - daily and weekly

  Drive Index = 0

  Media Type = DLT-V4

  Archive Device = /dev/nst0

  AutomaticMount = no;   # when device opened, read it

  AlwaysOpen = yes;

  RemovableMedia = yes;

  RandomAccess = no;

  AutoChanger = no

 

Device {

  Name = Quantum-DLT-1# Second tape - monthly and yearly

  Drive Index = 1

  Media Type = DLT-V4

  Archive Device = /dev/nst1

  AutomaticMount = no;   # when device opened, read it

  AlwaysOpen = yes;

  RemovableMedia = yes;

  RandomAccess = no;

  AutoChanger = no

 

***bacula-dir.conf-  storage device section

 

# Definition of DDS tape storage device

Storage {

  Name = Quantum-DLT-V4

#  Do not use "localhost" here 

  Address = distress.ACCOUNTING.EDT.LOCAL# N.B. Use a fully
qualified name here

  SDPort = 9103 

  Password = "Dn91BxJ/wNTn+9u3OX4ef1iRBXh1/Ch2GBaNiQzoQ9ny"  #
password for Storage daemon

  Device = Quantum-DLT # must be same as Device in Storage daemon

  Media Type = DLT-V4  # must be same as MediaType in Storage
daemon

#  Autochanger = yes