Hello,

2014-10-03 1:27 GMT+02:00 Russ Button <russ...@telmate.com>:

>  The times they are a-changing, but my Dell Autochanger sure isn't...
>
> I'm working at getting an initial install of bacula up and running.  My
> backup server is a Dell R510 running CentOS 7.0, which has bacula version
> 5.2.13-18 in the yum repository.  I'm using mysql for the data base.  We're
> going to be writing to a Dell ML6000 (a re-labeled IBM Ultrium TD6) with
> LTO-6 tapes, which hold 2.5TB native.   There is one tape drive and 40 tape
> slots in the Dell autochanger, with 30 new, unused tapes in them.
>
> I've got the director successfully talking to the database and the local
> file daemon.  I believe that the storage daemon is successfully talking to
> the autochanger
>

Did you tested your configuration with btape? If not do it and apply all
recomendation. With btape you can test both drive and autochanger
configuration.

and the tape drive because in bconsole, I was able to add the tapes to the
> Default pool:
>
>
> *add pool=Default storage=ML6000-LTO3-0
> You probably don't want to be using this command since it
> creates database records without labeling the Volumes.
> You probably want to use the "label" command.
>

Did you read above message?

It say that you should use a label command instead of add. Please folow
this recomendation. The label command will add tapes to your Bacula
configuration. Add command has a different purpose.

 If your tape library support barcodes and you have a barcode labels on
your tapes then you can use a label barcodes command to successfully label
all required tapes.


>
>
> Now when I attempt a local backup, here's what I get:
> ========================================================
>  02-Oct 16:09 bacula-dir JobId 14: No prior Full backup Job record found.
> 02-Oct 16:09 bacula-dir JobId 14: No prior or suitable Full backup found
> in catalog. Doing FULL backup.
> 02-Oct 16:09 bacula-dir JobId 14: Start Backup JobId 14,
> Job=LocalBackup.2014-10-02_16.09.41_13
> 02-Oct 16:09 bacula-dir JobId 14: Using Device "ML6000-LTO3-0" to write.
> 02-Oct 16:09 bacula-sd JobId 14: No slot defined in catalog (slot=0) for
> Volume "LTO6-Vol0001" on "ML6000-LTO3-0" (/dev/nst0).
>
02-Oct 16:09 bacula-sd JobId 14: Cartridge change or "update slots" may be
> required.
> 02-Oct 16:09 bacula-sd JobId 14: Warning: mount.c:219 Open device
> "ML6000-LTO3-0" (/dev/nst0) Volume "LTO6-Vol0001" failed: ERR=dev.c:513
> Unable to open device "ML6000-LTO3-0" (/dev/nst0): ERR=No medium found
> 02-Oct 16:09 bacula-sd JobId 14: No slot defined in catalog (slot=0) for
> Volume "LTO6-Vol0001" on "ML6000-LTO3-0" (/dev/nst0).
> 02-Oct 16:09 bacula-sd JobId 14: Cartridge change or "update slots" may be
> required.
>

This errors exists because you did not use a label command.


>
> I built my bacula-sd.conf file from what I saw at:
>
> http://wiki.bacula.org/doku.php?id=sample_configs
>
> From my bacula-sd.conf
> =====================
>
> Autochanger {
>   Name = "ML6000 Library"
>   Device = ML6000-LTO3-0
>   Changer Device = /dev/sg8
>

Consider changing a device name to persistent device name provided by udev.


>   Changer Command = "/usr/libexec/bacula/mtx-changer %c %o %S %a %d"
>                     # %c = changer device
>                     # %o = command (unload|load|loaded|list|slots)
>                     # %S = slot index (1-based)
>                     # %a = archive device (i.e., /dev/sd* name for tape
> drive)
>                     # %d = drive index (0-based)
> }
>
> Device {
>   Name = ML6000-LTO3-0
>   Archive Device = /dev/nst0
>

As above. Consider using permanent device name provided by udev.


> Why is it bconsole can talk to the autochanger
>

Console "add" command is not talking to autochanger. A "label" command do.


> and get it to label
>

You can label tapes with label command, not add command.

best regards
-- 
Radosław Korzeniewski
rados...@korzeniewski.net
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to