Il 26/03/2017 01:54, Tomasz Michno ha scritto:
> Hello!
> [...]
> I'm not hiding that I'm just starting to get to know BareOS!
Hi Tomas. Welcome in.
> Status on VM:
>
> [root@BRZE-BareOS autochanger]# lspci
> [...]
> 00:03.0 SCSI storage controller: XenSource, Inc. Xen Platform Device (rev 02)
> [...]
>
> [root@BRZE-BareOS autochanger]# lsscsi -g
> [...]
> [3:0:0:0] tape IBM ULT3580-HH5 G9N1 /dev/st0 /dev/sg1
> [3:0:0:1] mediumx IBM 3573-TL E.20 /dev/sch0 /dev/sg2
You're running a very similar setup, as one of my bareos (v. 13.2.2) box (a
phisical "IBM System x3655"):
[root@bareos ~]# *lspci*
[...]
17:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS2008
PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03)
22:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS2008
PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03)
[...]
[root@bareos ~]# *lsscsi -g*
[...]
[3:0:0:0] tape IBM ULT3580-HH5 D8D5 /dev/st1 /dev/sg7
[3:0:0:1] mediumx IBM 3573-TL 8.50 /dev/sch1 /dev/sg8
[4:0:0:0] tape IBM ULT3580-HH5 D8D5 /dev/st0 /dev/sg5
[4:0:0:1] mediumx IBM 3573-TL 8.50 /dev/sch0 /dev/sg6
[...]
> [root@BRZE-BareOS device]# dmesg | grep 3:0:0
> [169037.229006] scsi 3:0:0:0: Sequential-Access IBM ULT3580-HH5
> G9N1 PQ: 0 ANSI: 6
> [169037.244229] scsi 3:0:0:1: Medium Changer IBM 3573-TL
> E.20 PQ: 0 ANSI: 5
> [169037.502748] scsi 3:0:0:0: Attached scsi generic sg1 type 1
> [169037.502799] scsi 3:0:0:1: Attached scsi generic sg2 type 8
> [169037.524809] st 3:0:0:0: Attached scsi tape st0
> [...]
> [169037.581515] ch 3:0:0:1: Attached scsi changer ch0
[root@bareos ~]# *dmesg | grep [34]:0:0*
scsi 2:3:0:0: Enclosure IBM-ESXS VSC7160 1.06 PQ: 0 ANSI: 3
scsi *4:0:0:0: Sequential-Access IBM ULT3580-HH5* D8D5 PQ: 0
ANSI: 6
[...]
scsi 4:0:0:1: Medium Changer IBM 3573-TL 8.50 PQ: 0 ANSI: 5
[...]
ses 2:3:0:0: Attached Enclosure device
st 4:0:0:0: Attached scsi tape st0
[...]
ch 4:0:0:1: Attached scsi changer ch0
[...]
scsi *3:0:0:0: Sequential-Access IBM ULT3580-HH5* D8D5 PQ: 0
ANSI: 6
[...]
st 3:0:0:0: Attached scsi tape st1
[...]
st 3:0:0:0: Attached scsi generic sg7 type 1
scsi 3:0:0:1: Medium Changer IBM 3573-TL 8.50 PQ: 0 ANSI: 5
[...]
ch 3:0:0:1: Attached scsi changer ch1
[...]
As you can see, our box is attached to *two distinct LTO-5 SAS
tape-drives, enclosed within a _single_ IBM T/L* (as the T/L is driven by
the drive, the O/S recognize two distinct devices related to the same T/L).
> [root@BRZE-BareOS autochanger]# cat /proc/scsi/scsi
> Attached devices:
> [...]
> Host: scsi3 Channel: 00 Id: 00 Lun: 00
> Vendor: IBM Model: ULT3580-HH5 Rev: G9N1
> Type: Sequential-Access ANSI SCSI revision: 06
> Host: scsi3 Channel: 00 Id: 00 Lun: 01
> Vendor: IBM Model: 3573-TL Rev: E.20
> Type: Medium Changer ANSI SCSI revision: 05
[root@bareos ~]# cat /proc/scsi/scsi
Attached devices:
[...]
Host: scsi4 Channel: 00 Id: 00 Lun: 00
Vendor: IBM Model: ULT3580-HH5 Rev: D8D5
Type: Sequential-Access ANSI SCSI revision: 06
Host: scsi4 Channel: 00 Id: 00 Lun: 01
Vendor: IBM Model: 3573-TL Rev: 8.50
Type: Medium Changer ANSI SCSI revision: 05
Host: scsi3 Channel: 00 Id: 00 Lun: 00
Vendor: IBM Model: ULT3580-HH5 Rev: D8D5
Type: Sequential-Access ANSI SCSI revision: 06
Host: scsi3 Channel: 00 Id: 00 Lun: 01
Vendor: IBM Model: 3573-TL Rev: 8.50
Type: Medium Changer ANSI SCSI revision: 05
Let me insist stating that scsi4:0:0:1 and scsi3:0:0:1 refers to the very
same phisical T/L.
As the general architecture, our box is similar to your, as it runs DIR +
SD + FD (although on [ancient/working] bareos 13.2.2)
Here are our main config item:
=> *BareOS SD* ( /etc/bareos/bareos-sd.conf )
Autochanger {
Name = LTO3-DT
Changer Device = /dev/tape/by-id/scsi-1IBM_3573-TL_00L2U78L8691_LL0
Device = LTO3-DT-D0
Device = LTO3-DT-D1
Changer Command = "/etc/bareos/scripts/mtx-changer %c %o %S %a %d"
}
[...]
Device {
Name = LTO3-DT-D0
Drive Index = 0
Media Type = DT-LTO-3
Archive Device = /dev/tape/by-id/scsi-35000e11136884001-nst
AutomaticMount = yes; # when device opened, read it
AlwaysOpen = yes;
RemovableMedia = yes;
RandomAccess = no;
Autochanger = yes
Labelmedia = no
Maximum Concurrent Jobs = 1
}
Device {
Name = LTO3-DT-D1
Drive Index = 1
Media Type = DT-LTO-3
Archive Device = /dev/tape/by-id/scsi-35000e11136884004-nst
AutomaticMount = yes; # when device opened, read it
AlwaysOpen = yes;
RemovableMedia = yes;
RandomAccess = no;
Autochanger = yes
Labelmedia = no
Maximum Concurrent Jobs = 1
}
=> *BareOS DIR* ( /etc/bareos/bareos-dir.conf )
[...]
Storage {
Name = TAPE_DOPPIO
Media Type = DT-LTO-3
Device = LTO3-DT
Address = 10.0.49.35
SDPort = 9103
Password = [...]
Autochanger = yes
Maximum Concurrent Jobs = 2
Allow Compression = no
}
[...]
Having said all the above, let me add that:
* we're not running/using WEB-UI: all our activities runs through "bconsole"
* we carefully scratch down our own configurations. So, tipically, we
remove all the stuff included in the RPMs and put down our own CFG
files. This means...
* we don't use the same approach as the 16.2 release. Altough we DO
heavily use "@include", we rely on it to store client config data in an
ordered way (from our-point-of-view, obviously);
Let me also add that:
* we're 110% satisfied about bareos. As a backup platform, It's
rock-solid and well-engineered. We won't consider other solutions,
unless strictly required/needed (see below);
* we're currently experiencing some problems (our main mail-server store
5TB of data and... backupping them [directly from the FD] tooks lot of
time]. Anyway, this is the price that we are paying for a missing
tuning (we're currently reinstalling the whole bareos infrastructure,
with a dedicated DIR+MySQL and different/external SD-boxes and
employing on-disk backups with copy/move jobs to tape. Hopefully things
will run slightly faster. This, on 16.2.... that I started installing
last week)
Back to your message:
> [...]
> ▒f▒Wbtape: ERROR TERMINATION at parse_conf.c:292
> Config error: Keyword "ChargerDevice" not permitted in this resource.
> Perhaps you left the trailing brace off of the previous resource.
> : line 4, col 17 of file
> /etc/bareos/bareos-sd.d/autochanger/3573-TL.conf
> *Charger* Device = /dev/tape/by-id/scsi-1IBM_3573-TL_00L2U78BW629_LL0
from the (working) config snippet I cut/pasted above, you can see that my
Autochanger directive include this:
*Changer* Device = /dev/tape/by-id/scsi-1IBM_3573-TL_00L2U78L8691_LL0
*Changer* Command = "/etc/bareos/scripts/mtx-changer %c %o %S %a %d"
and.... it's writte "Changer"... and not "*Charger*" :-)
Probably this might help [you] :-)
Should you have other questions, feel free to ask.
Bye,
DV
P.S.: We strongly rely on XEN --in general--, but I never tought about
PCI-redirecting the SCSI channel inside the VMs. This could be an option, for
our upcoming plans. Thanks for pointing this.
--
Damiano Verzulli
e-mail: [email protected]
---
possible?ok:while(!possible){open_mindedness++}
---
"...I want to serve my diskless Beowulf nodes via iSCSI with LVM over
RAID5 on IDE disks ..."
Oliver Xymoron (mlist.linux.scsi)
--
You received this message because you are subscribed to the Google Groups
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
For more options, visit https://groups.google.com/d/optout.
