Re: [Bacula-users] getting my tape drive online

[Jonathan H. <jh...@sk...>]

-----Original Message-----
From: Dan Langille [mailto:da...@la...]
Sent: Friday, January 11, 2013 10:17 AM
To: lst...@kw...
Cc: bac...@li...
Subject: Re: [Bacula-users] getting my tape drive online


On Jan 11, 2013, at 3:45 AM, lst...@kw... wrote:

>
> Zitat von Jonathan Horne <jh...@sk...>:
>
>> My drive appears to be working correctly, and the devices I poll here
>> correspond to configurations I use in my config file.  Tests all seem
>> fine (to my layman's observation), but in practice actual commands
>> are failing.
>
> Have you also checked as user Bacula is running as? Maybe some missing
> permission on a script/directory?

In my experience, this is likely the problem.  In the URLs I pasted, you can see how I tested and correctly those exact situations.

--
Dan Langille - http://langille.org


OK, Dan was right, further experimentation was required.  Progress has been made.

First, I added bacula to tape group, based on what I see here.

 [root@d0lppb021 html]# ls -la /dev/sg6
crw-rw---- 1 root tape 21, 6 Jan  8 16:03 /dev/sg6
[root@d0lppb021 html]# ls -la /dev/nst1 /dev/nst1
crw-rw---- 1 root tape 9, 129 Jan  8 16:03 /dev/nst1
crw-rw---- 1 root tape 9, 129 Jan  8 16:03 /dev/nst1

then I change mtx.log so that bacula can access and write to it.  I didn't at first believe this was necessary, as bacula processes are running as root (shown by ps command), but that doesn't mean that child processes might not be forked as bacula user.  I don't know, so I humor the concept.  It seems to have helped.

[root@d0lppb021 html]# ls -la /var/spool/bacula/mtx.log
-rw-rw-r-- 1 root bacula 133794 Jan 11 11:07 /var/spool/bacula/mtx.log

After the above changes, I now I have different output from the label barcodes command:

*label barcodes
Automatically selected Catalog: MyCatalog
Using Catalog "MyCatalog"
The defined Storage resources are:
     1: File
     2: PV-TL4000
Select Storage resource (1-2): 2
Enter autochanger drive[0]:
Connecting to Storage daemon PV-TL4000 at d0lppb021.skopos.me:9103 ...
3306 Issuing autochanger "slots" command.
Device "PV-TL4000" has 47 slots.
Connecting to Storage daemon PV-TL4000 at d0lppb021.skopos.me:9103 ...
3306 Issuing autochanger "list" command.
The following Volumes will be labeled:
Slot  Volume
==============
   1  SK1004L3
   2  SK1006L3
   3  SK1009L3
Do you want to label these Volumes? (yes|no): yes
Defined Pools:
     1: Default
     2: Scratch
     3: YearlyBackups
     4: MonthlyBackups
     5: FullBackups
     6: IncrementalBackups
     7: DifferentialBackups
     8: TapeArchiveFullBackups
Select the Pool (1-8): 8
Connecting to Storage daemon PV-TL4000 at d0lppb021.skopos.me:9103 ...
Sending label command for Volume "SK1004L3" Slot 1 ...
3307 Issuing autochanger "unload slot 3, drive 0" command.
3304 Issuing autochanger "load slot 1, drive 0" command.
3305 Autochanger "load slot 1, drive 0", status is OK.
3920 Cannot label Volume because it is already labeled: "SK1004L3"  <---- I didn't get this before
Label command failed for Volume SK1004L3.
Sending label command for Volume "SK1006L3" Slot 2 ...
3307 Issuing autochanger "unload slot 1, drive 0" command.
3304 Issuing autochanger "load slot 2, drive 0" command.
3305 Autochanger "load slot 2, drive 0", status is OK.
3920 Cannot label Volume because it is already labeled: "SK1006L3"  <---- I didn't get this before
Label command failed for Volume SK1006L3.
Sending label command for Volume "SK1009L3" Slot 3 ...
3307 Issuing autochanger "unload slot 2, drive 0" command.
3304 Issuing autochanger "load slot 3, drive 0" command.
3305 Autochanger "load slot 3, drive 0", status is OK.
3920 Cannot label Volume because it is already labeled: "SK1009L3"  <---- I didn't get this before
Label command failed for Volume SK1009L3.
*

So things are looking much better now, I think I just need to figure out how to wipe those tapes, and im GTG.

Thanks for the advice everyone!
jonathan

________________________________
This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind SKOPOS to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose.