Re: [Bacula-users] Help with regexp
I think you need to run the bscan utility to import the files on a tape volume back into your "Catalog". https://www.bacula.org/5.0.x-manuals/en/utility/utility/Volume_Utility_Tools.html#SECTION00272000 -- *Hector Barrera* *| **IMN CREATIVE* DIRECTOR OF TECHNOLOGY 622 West Colorado Street Glendale, California 91204 O: 818 858 0408 M: 562.413.5151 W: *imncreative.com <http://imncreative.com/>* On Tue, Mar 30, 2021 at 12:21 PM Heitor Faria wrote: > Hi folks, > > Hello, > > I need to restore data from Sept of 2020. I have the tape but the data has > been purged from the database. Bconsole is asking for "Regexp matching > files to restore? (empty to abort):". > > I'm embarrassed to say regexp is alien to me! The path I need is > "/projects/2020/220089/". All files below that is what I need. > > Any help here is greatly appreciated! Thank you! > > => https://regex101.com/ > I usually test the Python flavor for Bacula expressions. > > Regards, > -- > Thomas Plancon > CAD/IT MANAGER > > E: tplan...@bkaarchs.com > W: www.bkaarchitects.com <http://www.bkaarchs.com> > > [image: BKA/LOGO] > [image: LinkedIn] <https://www.linkedin.com/company/bka-architects/> [image: > FaceBook] > <https://www.facebook.com/pages/category/Commercial---Industrial/BKA-Architects-Inc-164150853637095/> > [image: > InsGram] <https://www.instagram.com/bka_architects/> > > > ___ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users > > -- > > MSc Heitor Faria > Bacula LATAM CEO > mobile1: + 1 909 655-8971 > mobile2: + 55 61 98268-4220 > [image: linkedin icon] > <https://www.linkedin.com/in/msc-heitor-faria-5ba51b3> > [image: logo] > América Latina > bacula.lat | bacula.com.br <http://www.bacula.com.br> > > ___ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users > ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Fwd: Baculum 11.0.2.1 Manage Autochanger.
Hello folks, I just upgraded to Bacula 11.0.1 and Baculum to ver. 11.0.2.1 Everything works, with the exception of being able to control our Quantum SuperLoader3 autochanger from within the Baculum interface. When I go to Storage, I don't see the Autochanger that I've configured via the Baculum API interface. I only see the device that I configured via the bacula-sd.conf file. If I select "Details" on the device that I configured via bacula-sd.conf file, and then click Manage Autochanger, I get this error: *Autochanger management is unavailable. To manage autochanger from here, add it to the API host devices on the API host side.* Any idea why the Baculum API is not passing the autochanger config to Baculum WEB? Please advise. -- *Hector Barrera* *| **IMN CREATIVE* DIRECTOR OF TECHNOLOGY 622 West Colorado Street Glendale, California 91204 O: 818 858 0408 M: 562.413.5151 W: *imncreative.com <http://imncreative.com/>* ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Baculum Autochanger "Update slots" not working.
Hello folks, It appears that the Volumes -> Update slots function does not work in Baculum 11.0.2.1 When I click on it, it does nothing. This used to work before I upgraded from version 9.6.x Please advise. -- *Hector Barrera* *| **IMN CREATIVE* DIRECTOR OF TECHNOLOGY 622 West Colorado Street Glendale, California 91204 O: 818 858 0408 M: 562.413.5151 W: *imncreative.com <http://imncreative.com/>* ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Baculum Autochanger "Update slots" not working.
Excellent! Thanks Gani. Hector. On Wed, Apr 14, 2021 at 6:43 PM Marcin Haba wrote: > Hello Hector, > > Thanks for letting know about this problem. It is a bug in Baculum > Web. Here is the commit that fixes it: > > > https://www.bacula.org/git/cgit.cgi/bacula/commit/?h=Branch-11.0&id=f816d945b47219d00bd2f1e616c57352d9e4bf95 > > New release with the fix should be available soon (within days). > > Best regards, > Marcin Haba (gani) > > On Wed, 14 Apr 2021 at 22:57, Hector Barrera > wrote: > > > > Hello folks, > > > > It appears that the Volumes -> Update slots function does not work in > Baculum 11.0.2.1 > > When I click on it, it does nothing. > > > > This used to work before I upgraded from version 9.6.x > > > > Please advise. > > > > -- > > Hector Barrera | IMN CREATIVE > > DIRECTOR OF TECHNOLOGY > > 622 West Colorado Street > > Glendale, California 91204 > > O: 818 858 0408 > > M: 562.413.5151 > > W: imncreative.com > > ___ > > Bacula-users mailing list > > Bacula-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/bacula-users > > > > -- > "Greater love hath no man than this, that a man lay down his life for > his friends." Jesus Christ > > "Większej miłości nikt nie ma nad tę, jak gdy kto życie swoje kładzie > za przyjaciół swoich." Jezus Chrystus > ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Fwd: Baculum 11.0.2.1 Manage Autochanger.
OK. I believe the problem is how I got the bacula-dir.conf and
bacula-sd.conf files configured.
These are the pertinent parts:
bacula-dir.conf
Storage {
Name = "File1"
SdPort = 9103
Address = "bacula02.imn.ad"
Password = "ZGZjNDMzZTg0OTR"
Device = "FileChgr1"
MediaType = "File1"
Autochanger = "File1"
MaximumConcurrentJobs = 10
}
Storage {
Name = "IBMLTO7"
Description = "IBM LTO7 Inside Quantum SuperLoader 3 Tape Library"
Address = "bacula02.imn.ad"
Password = "XX"
Device = "IBMLTO7"
MediaType = "LTO-7"
Autochanger = "IBMLTO7"
MaximumConcurrentJobs = 1
}
---
bacula-sd.conf
Device {
Name = "FileChgr1-Dev1"
MediaType = "File1"
ArchiveDevice = "/home/bacula/backups"
RemovableMedia = no
RandomAccess = yes
AutomaticMount = yes
LabelMedia = yes
AlwaysOpen = no
MaximumConcurrentJobs = 5
}
Device {
Name = "IBMLTO7"
Description = "IBM LTO7 in Library 1 Drive 1"
MediaType = "LTO-7"
DeviceType = "Tape"
ArchiveDevice = "/dev/tape/by-id/scsi-35005076312156b6c-nst"
RemovableMedia = yes
RandomAccess = no
AutomaticMount = yes
LabelMedia = yes
AlwaysOpen = yes
Autochanger = yes
AutoSelect = yes
ChangerDevice = "/dev/tape/by-id/scsi-3500e09efff10c86a"
AlertCommand = "sh -c 'tapeinfo -f %c |grep TapeAlert|cat'"
MaximumBlockSize = 512K
MaximumFileSize = 200
Spool Directory = "/home/bacula/spool"
MaximumSpoolSize = 20
}
Autochanger {
Name = "FileChgr1"
Device = "FileChgr1-Dev1"
ChangerDevice = "/dev/null"
ChangerCommand = ""
}
Autochanger {
Name = QUANTUM-LTO-Lib1
Description = "Quantum SuperLoader 3"
Device = "IBMLTO7"
Changer Device = "/dev/tape/by-id/scsi-3500e09efff10c86a"
Changer Command = "/opt/bacula/scripts/mtx-changer %c %o %S %a %d\"
Changer Device = "/dev/tape/by-id/scsi-3500e09efff10c86a"
}
This is the only way I got the LTO7 IBM Drive inside the Quantum
Superloader3 to work and change tapes automatically.
What should I change?
Hector B.
On Thu, Apr 15, 2021 at 1:35 PM Marcin Haba wrote:
> Hello Hector,
>
> Thanks for more details. Your tape drive device is already named 'IBMLTO7'
> and it causes this collision.
>
> On screenshot, that you sent, I see another autochanger name
> "QUANTUM-LTO-Lib1" in storage daemon configuration. Does it mean that you
> have two autochangers: IBMLTO7 and QUANTUM-LTO-Lib1? If yes, then why you
> didn't add 'QUANTUM-LTO-Lib1'it to the Director configuration as a
> storage/autochanger?
>
> To solve the problem with autochanger setting, I propose to look to
> bacula-dir.conf for Autochanger configuration that you would like to
> manage, for example:
>
> Storage {
>Name = "AAA"
>Device = "BBB"
>Autochanger = "yes"
>...
>...
> }
>
> and use name BBB as Autochanger name in Baculum API autochanger
> configuration, which basically is almost the same as you choose the
> Autochanger name from the drop down list with label "Copy from Bacula SD
> config".
>
> Best regards,
> Marcin Haba (gani)
>
> On Thu, 15 Apr 2021 at 21:55, Hector Barrera <
> hector.barr...@imncreative.com> wrote:
>
>> Thanks Marcin.
>>
>> The bconsole output is:
>> *show storage=IBMLTO7
>> Autochanger: name=IBMLTO7 address=bacula02.imn.ad SDport=9103 MaxJobs=5
>> NumJobs=0
>> DeviceName=IBMLTO7 MediaType=LTO-7 StorageId=6 Autochanger=1
>> AC group=6 ShareStore=*none*
>>
>> So the name of the Device should be *IBMLTO7 *
>>
>> When I try to change the Autochanger on the API side, I get an error
>> message: "Autochanger with the given name already exists" See attached
>> picture.
>>
>>
>>
>>
>> On Thu, Apr 15, 2021 at 11:31 AM Marcin Haba wrote:
>>
>>> Hello Hector,
>>>
>>> Yes, everything looks correct on the screenshots. Thanks for them. In
>>> this case before looking in logs, I have a question about the autochanger
>>> name. When you run in bconsole the following command:
>>>
>>> show storage=IBMLTO7
>>>
>>> could you tell me if in received output the 'DeviceName' value is
>>> "QUANTUM-LTO-SuperLoader3" ?
>>>
>>> If it isn't then please edit Autochanger config on the Baculum API side
>>> and please set in place "QUANTUM-LTO-SuperLoader
Re: [Bacula-users] Fwd: Baculum 11.0.2.1 Manage Autochanger.
That did it !!!
Thank you so much Marcin for all your help with this.
I'm now able to manage the autoloader magazines from within Baculum itself.
I don't use the Quantum WEB GUI anymore for these tasks.
I did discover a small bug in Baculum though, If you click on Storage ->
Click on "Details" of your storage device -> Configure Autochanger
You'll see in the ChangerCommand field this:
/opt/bacula/scripts/mtx-changer %c %o %S %a %d" *Changer Device = *
The "Changer Device =" part does not exist in the bacula-sd.conf file, this
is being added by Baculum.
The same happens when you add the Autochanger in the Baculum API after you
click "Copy from Bacula SD config:"
If you don't remove the "Changer Device =", it won't let you save.
Do you want me to open a Bug report for this?
Cheers!
Hector Barrera.
On Thu, Apr 15, 2021 at 7:23 PM Marcin Haba wrote:
> Hello Hector,
>
> Many thanks for showing your Bacula configuration. Indeed, it explains why
> you experienced the problem with names in Baculum.
>
> I propose to use the following configuration below. I marked changed lines
> by "# Change X" marker
>
> bacula-dir.conf
>
> Storage {
> Name = "QUANTUM-LTO-changer1" # Change 1
> Description = "Quantum SuperLoader 3 Tape Library" # Change 2
> Address = "bacula02.imn.ad"
> Password = "XX"
> Device = "QUANTUM-LTO-Lib1"# Change 3
> MediaType = "LTO-7"
> Autochanger = yes # Change 4
> MaximumConcurrentJobs = 1
> }
> ---
>
> bacula-sd.conf
>
> Autochanger {
> Name = QUANTUM-LTO-Lib1
> Description = "Quantum SuperLoader 3"
> Device = "IBMLTO7"
> Changer Device = "/dev/tape/by-id/scsi-3500e09efff10c86a"
> Changer Command = "/opt/bacula/scripts/mtx-changer %c %o %S %a %d\"
> # Changer Device = "/dev/tape/by-id/scsi-3500e09efff10c86a" # Change 5
> (line to remove)
> }
>
> Please note that after doing Change 1 (IBMLTO7 => QUANTUM-LTO-changer1 in
> Storage resource) you will need to update all jobs that were using this
> Storage to use the new name. I mean changing in Job and JobDefs (and Pool)
> resources:
>
> Storage = IBMLTO7
>
> into:
>
> Storage = QUANTUM-LTO-changer1
>
> After doing it and reloading daemons configuration, please create
> Autochanger configuration in Baculum API by selecting "Copy from Bacula SD
> config" drop down list item "QUANTUM-LTO-Lib1". Auto-filled values will be
> correct and will not cause any name's collision.
>
> Best regards,
> Marcin Haba (gani)
>
> On Fri, 16 Apr 2021 at 00:27, Hector Barrera <
> hector.barr...@imncreative.com> wrote:
>
>> OK. I believe the problem is how I got the bacula-dir.conf and
>> bacula-sd.conf files configured.
>>
>> These are the pertinent parts:
>>
>> bacula-dir.conf
>>
>> Storage {
>> Name = "File1"
>> SdPort = 9103
>> Address = "bacula02.imn.ad"
>> Password = "ZGZjNDMzZTg0OTR"
>> Device = "FileChgr1"
>> MediaType = "File1"
>> Autochanger = "File1"
>> MaximumConcurrentJobs = 10
>> }
>> Storage {
>> Name = "IBMLTO7"
>> Description = "IBM LTO7 Inside Quantum SuperLoader 3 Tape Library"
>> Address = "bacula02.imn.ad"
>> Password = "XX"
>> Device = "IBMLTO7"
>> MediaType = "LTO-7"
>> Autochanger = "IBMLTO7"
>> MaximumConcurrentJobs = 1
>> }
>> ---
>>
>> bacula-sd.conf
>>
>> Device {
>> Name = "FileChgr1-Dev1"
>> MediaType = "File1"
>> ArchiveDevice = "/home/bacula/backups"
>> RemovableMedia = no
>> RandomAccess = yes
>> AutomaticMount = yes
>> LabelMedia = yes
>> AlwaysOpen = no
>> MaximumConcurrentJobs = 5
>> }
>> Device {
>> Name = "IBMLTO7"
>> Description = "IBM LTO7 in Library 1 Drive 1"
>> MediaType = "LTO-7"
>> DeviceType = "Tape"
>> ArchiveDevice = "/dev/tape/by-id/scsi-35005076312156b6c-nst"
>> RemovableMedia = yes
>> RandomAccess = no
>> AutomaticMount = yes
>> LabelMedia = yes
>> AlwaysOpen = yes
>> Autochanger = yes
>> AutoSelect = yes
>> ChangerDevice = "/dev/ta
Re: [Bacula-users] Fwd: Baculum 11.0.2.1 Manage Autochanger.
Great.
I removed the trailing \ (backslash) all good now.
Have a great weekend!
Hector Barrera.
On Fri, Apr 16, 2021 at 12:12 PM Marcin Haba wrote:
> Hello Hector,
>
> Great. Thanks for your positive feedback :-)
>
> For this additional " Changer Device = " string, it is a typo error in
> bacula-sd.conf. In my previous mail, when I sent the autochanger
> configuration, I didn't notice that there is a backslash quote character
> instead of quote character at the end of the Changer Command directive and
> it causes that bsdjson prints wrong value:
>
> Autochanger {
> Name = QUANTUM-LTO-Lib1
> Description = "Quantum SuperLoader 3"
> Device = "IBMLTO7"
> Changer Device = "/dev/tape/by-id/scsi-3500e09efff10c86a"
> Changer Command = "/opt/bacula/scripts/mtx-changer %c %o %S %a %d\"
> <= HERE IT IS
> # Changer Device = "/dev/tape/by-id/scsi-3500e09efff10c86a" # Change 5
> (line to remove)
> }
>
> Please change this line:
>
> Changer Command = "/opt/bacula/scripts/mtx-changer %c %o %S %a %d\"
>
> into the following line:
>
> Changer Command = "/opt/bacula/scripts/mtx-changer %c %o %S %a %d"
>
> and the redundant Changer Command = should disappear.
>
> Best regards,
> Marcin Haba (gani)
>
> On Fri, 16 Apr 2021 at 20:55, Hector Barrera <
> hector.barr...@imncreative.com> wrote:
>
>> That did it !!!
>>
>> Thank you so much Marcin for all your help with this.
>>
>> I'm now able to manage the autoloader magazines from within Baculum
>> itself. I don't use the Quantum WEB GUI anymore for these tasks.
>>
>> I did discover a small bug in Baculum though, If you click on Storage ->
>> Click on "Details" of your storage device -> Configure Autochanger
>> You'll see in the ChangerCommand field this:
>> /opt/bacula/scripts/mtx-changer %c %o %S %a %d" *Changer Device = *
>> The "Changer Device =" part does not exist in the bacula-sd.conf file,
>> this is being added by Baculum.
>>
>> The same happens when you add the Autochanger in the Baculum API after
>> you click "Copy from Bacula SD config:"
>> If you don't remove the "Changer Device =", it won't let you save.
>> Do you want me to open a Bug report for this?
>>
>> Cheers!
>>
>> Hector Barrera.
>>
>> On Thu, Apr 15, 2021 at 7:23 PM Marcin Haba wrote:
>>
>>> Hello Hector,
>>>
>>> Many thanks for showing your Bacula configuration. Indeed, it explains
>>> why you experienced the problem with names in Baculum.
>>>
>>> I propose to use the following configuration below. I marked changed
>>> lines by "# Change X" marker
>>>
>>> bacula-dir.conf
>>>
>>> Storage {
>>> Name = "QUANTUM-LTO-changer1" # Change 1
>>> Description = "Quantum SuperLoader 3 Tape Library" # Change 2
>>> Address = "bacula02.imn.ad"
>>> Password = "XX"
>>> Device = "QUANTUM-LTO-Lib1"# Change 3
>>> MediaType = "LTO-7"
>>> Autochanger = yes # Change 4
>>> MaximumConcurrentJobs = 1
>>> }
>>> ---
>>>
>>> bacula-sd.conf
>>>
>>> Autochanger {
>>> Name = QUANTUM-LTO-Lib1
>>> Description = "Quantum SuperLoader 3"
>>> Device = "IBMLTO7"
>>> Changer Device = "/dev/tape/by-id/scsi-3500e09efff10c86a"
>>> Changer Command = "/opt/bacula/scripts/mtx-changer %c %o %S %a %d\"
>>> # Changer Device = "/dev/tape/by-id/scsi-3500e09efff10c86a" # Change 5
>>> (line to remove)
>>> }
>>>
>>> Please note that after doing Change 1 (IBMLTO7 => QUANTUM-LTO-changer1
>>> in Storage resource) you will need to update all jobs that were using this
>>> Storage to use the new name. I mean changing in Job and JobDefs (and Pool)
>>> resources:
>>>
>>> Storage = IBMLTO7
>>>
>>> into:
>>>
>>> Storage = QUANTUM-LTO-changer1
>>>
>>> After doing it and reloading daemons configuration, please create
>>> Autochanger configuration in Baculum API by selecting "Copy from Bacula SD
>>> config" drop down list item "QUANTUM-LTO-Lib1". Auto-filled values will be
>>> correct and will not cause
Re: [Bacula-users] How to convert the catalogue to Bacula 11.0.2 mode.
In my case, I upgraded from version 9.6.x via yum without a problem. The RPM took care of the database upgrade for me. As a precaution, I took a snapshot of the VMWare server just to make sure I could revert back. -- *Hector Barrera* *| **IMN CREATIVE* DIRECTOR OF TECHNOLOGY 622 West Colorado Street Glendale, California 91204 O: 818 858 0408 W: *imncreative.com <http://imncreative.com/>* On Wed, Apr 28, 2021 at 6:18 AM Erik P. Olsen wrote: > Hello, > > I am planning to upgrade to Bacula 11.0.2 but reading about how to convert > the catalogue > makes me a bit uneasy. The statement is: "Normally, it is automatic". What > does it mean > that it is automatic? Does it actually run the script by itself first time > Bacula 11.02 > is started? > > -- > Erik P. Olsen - Copenhagen, Denmark > Fedora 33/64 bit xfce Claws-Mail POP3 Gramps 5.1.3 Bacula 9.6.5 > > > ___ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users > ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Getting a LTO8 drive work with Bacula.
quot;/dev/tape/by-id/scsi-3500e09efff10c86a" ChangerCommand = "/opt/bacula/scripts/mtx-changer %c %o %S %a %d" } --- I should mention that running this actually works: mt -f /dev/nst0 rewind tar -cvf /dev/nst0 . mt -f /dev/nst0 rewind tar -xvf /dev/nst0 Running the tar directly to the tape drive works. I was able to tar several files and extract them without a problem. So the problem seems to be with my bacula configuration. Please help, I'm banging my head against the trying to make our new LTO8 drive work with Bacula. Cheers! -- *Hector Barrera* *| **IMN CREATIVE* DIRECTOR OF TECHNOLOGY 622 West Colorado Street Glendale, California 91204 O: 818 858 0408 M: 562.413.5151 W: *imncreative.com <http://imncreative.com/>* ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Getting a LTO8 drive work with Bacula.
Thanks, Gary for replying back. I used the /dev/nst0 as a shortcut when I typed the command and I use the /dev/tape/by-id/scsi-35000e111cc2d8001-nst in the bacula-sd.conf file just in case the tape drive name gets changed by Centos when the server gets rebooted (it tends to happen on rare occasions), so by using the dev/tape/by-id/ this assures bacula to always find the tape device name no matter what. Nonetheless,.running the tapeinfo command but this time using the /dev/tape/by-id outputs the same information: [root@bacula02 ~]# tapeinfo -f /dev/tape/by-id/scsi-35000e111cc2d8001-nst Product Type: Tape Drive Vendor ID: 'IBM ' Product ID: 'ULTRIUM-HH8 ' Revision: 'N9M1' Attached Changer API: No SerialNumber: '1097012184' MinBlock: 1 MaxBlock: 8388608 SCSI ID: 1 SCSI LUN: 0 Ready: yes BufferedMode: yes Medium Type: 0x78 Density Code: 0x5c BlockSize: 0 DataCompEnabled: yes DataCompCapable: yes DataDeCompEnabled: yes CompType: 0xff DeCompType: 0xff BOP: yes Block Position: 0 Partition 0 Remaining Kbytes: -1 Partition 0 Size in Kbytes: -1 ActivePartition: 0 EarlyWarningSize: 0 NumPartitions: 1 MaxPartitions: 3 Partition0: 1071 Partition1: 57857 Partition2: 0 Partition3: 0 -- This problem is a weird one, because like I said in my previous email, I'm able to tar files directly to the tape drive, i.e. tar -cvf /dev/nst0 and I'm able to extract them back. If you notice while running the btape test, it appears that the command is able to write to the drive the first file, then it reads the last block back without a problem, but when it tries to write a second time, then it fails: 12-Apr 15:59 btape JobId 0: Re-read of last block succeeded. <--- *btape: btape.c:1156-0 Error writing block to device.* Is as if the drive is not writing the correct EOF bit at the end of the file transfer. Also, there's another command that outputs the drive status: [root@bacula02 ~]# mt -f /dev/tape/by-id/scsi-35000e111cc2d8001-nst status SCSI 2 tape drive: File number=0, block number=0, partition=0. Tape block size 0 bytes. Density code 0x5c (no translation). Soft error count since last status=0 General status bits on (4101): BOT ONLINE IM_REP_EN Thanks again. Hector B. On Tue, Apr 12, 2022 at 7:20 PM Gary R. Schmidt wrote: > On 13/04/2022 09:46, Hector Barrera wrote: > > Hello Gentlemen, > > > > I wonder if any of you had a chance to make an IBM LTO8 Tape Drive work > > with Bacula 11.0.1 > > > > Previously we had an IBM LTO7 that worked great, but this new drive is > > not working as expected, the btape test function throws out an error. > > > > I followed the Bacula chapter: "Testing Your Tape Drive With Bacula" > > > > Here's some information about our setup: > > > > *_Tape Drive:_* > > > > [root@bacula02 tmp]# tapeinfo -f /dev/nst0 > > >ArchiveDevice = "/dev/tape/by-id/scsi-35000e111cc2d8001-nst" > > You are referring to things using different names. > > What happens if you change them to be consistent? > > Cheers, > GaryB-) > > > ___ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users > ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Getting a LTO8 drive work with Bacula.
Thank you, Martin!
Your suggestion to add the debug level revealed the problem!
btape: block_util.c:316-0 === adata=0 binbuf=524200
btape: block_util.c:577-0 Zero end blk: adata=0 cleared=64 buf_len=524288
wlen=524288 binbuf=524224
btape: block_util.c:361-0 block_header: block_len=524224
btape: block_util.c:377-0 ser_block_header: adata=0 checksum=543943d7
btape: block_util.c:598-0 Enter: bool is_user_volume_size_reached(DCR*,
bool)
btape: block_util.c:625-0 *Maximum volume size 2,000,000,000 *exceeded Vol=
device="IBMLTO8" (/dev/tape/by-id/scsi-35000e111cc2d8001-nst).
Marking Volume "" as Full.
btape: block_util.c:631-0 Return from is_user_volume_size_reached=1
btape: block_util.c:632-0 Leave: bool is_user_volume_size_reached(DCR*,
bool)
For some reason, I had this directive in my bacula-sd.conf file:
*MaximumVolumeSize = 20*
Which is only mostly used for disk-based backups, not for tapes!
Thanks again Martin.
Problem solved.
Cheers!
Hector Barrera.
On Wed, Apr 13, 2022 at 3:41 AM Martin Simmons wrote:
> I suggest adding the -d200 argument to btape so it prints some debugging
> info.
>
> Also, which driver are you using? I think you need to avoid the lin_tape
> driver because it doesn't work with Bacula.
>
> __Martin
>
>
> >>>>> On Tue, 12 Apr 2022 16:46:55 -0700, Hector Barrera said:
> >
> > Hello Gentlemen,
> >
> > I wonder if any of you had a chance to make an IBM LTO8 Tape Drive work
> > with Bacula 11.0.1
> >
> > Previously we had an IBM LTO7 that worked great, but this new drive is
> not
> > working as expected, the btape test function throws out an error.
> >
> > I followed the Bacula chapter: "Testing Your Tape Drive With Bacula"
> >
> > Here's some information about our setup:
> >
> > *Tape Drive:*
> >
> > [root@bacula02 tmp]# tapeinfo -f /dev/nst0
> > Product Type: Tape Drive
> > Vendor ID: 'IBM '
> > Product ID: 'ULTRIUM-HH8 '
> > Revision: 'N9M1'
> > Attached Changer API: No
> > SerialNumber: '1097012184'
> > MinBlock: 1
> > MaxBlock: 8388608
> > SCSI ID: 1
> > SCSI LUN: 0
> > Ready: yes
> > BufferedMode: yes
> > Medium Type: 0x78
> > Density Code: 0x5c
> > *BlockSize: 0*
> > DataCompEnabled: yes
> > DataCompCapable: yes
> > DataDeCompEnabled: yes
> > CompType: 0xff
> > DeCompType: 0xff
> > BOP: yes
> > Block Position: 0
> > Partition 0 Remaining Kbytes: -1
> > Partition 0 Size in Kbytes: -1
> > ActivePartition: 0
> > EarlyWarningSize: 0
> > NumPartitions: 1
> > MaxPartitions: 3
> > Partition0: 1071
> > Partition1: 57857
> > Partition2: 0
> > Partition3: 0
> >
> > First I thought the problem might be with the block size, but as you can
> > see above, the drive is already to 0
> >
> > *Running the btape test function:*
> >
> > [root@bacula02 tmp]# btape -c /opt/bacula/etc/bacula-sd.conf
> > /dev/tape/by-id/scsi-35000e111cc2d8001-nst
> > Tape block granularity is 1024 bytes.
> > btape: butil.c:295-0 Using device:
> > "/dev/tape/by-id/scsi-35000e111cc2d8001-nst" for writing.
> > btape: btape.c:477-0 open device "IBMLTO8"
> > (/dev/tape/by-id/scsi-35000e111cc2d8001-nst): OK
> > *test
> >
> > === Write, rewind, and re-read test ===
> >
> > I'm going to write 1 records and an EOF
> > then write 1 records and an EOF, then rewind,
> > and re-read the data to verify that it is correct.
> >
> > This is an *essential* feature ...
> >
> > 12-Apr 15:59 btape JobId 0: Re-read of last block succeeded.
> > *btape: btape.c:1156-0 Error writing block to device.*
> > *
> > --
> > Attempting to WEOF a second time claims the tape is in read-only mode:
> >
> > *weof
> > btape: Fatal Error at tape_dev.c:953 because:
> > tape_dev.c:952 Attempt to WEOF on non-appendable Volume
> > 12-Apr 16:25 btape: Fatal Error at tape_dev.c:953 because:
> > tape_dev.c:952 Attempt to WEOF on non-appendable Volume
> > btape: btape.c:607-0 Bad status from weof. *ERR=tape_dev.c:952 Attempt to
> > WEOF on non-appendable Volume*
> >
> >
> > *Our bacula-sd.conf (LTO8 in bold):*
> >
> > Storage {
> > Name = "bacula02-sd"
> > SdAddress = **.**.**.**
> > WorkingDirectory = "/opt/bacula/working"
> > PidDirectory = "/opt/bacula/working"
> > PluginDirectory = "/opt/bacula/plugins"
> > MaximumConcurrentJobs = 20
&g
Re: [Bacula-users] About bacula-dir.conmsg
Quick question, where is this file located at? Please advise. Hector B. On Mon, May 2, 2022 at 7:28 AM Guilherme Santos wrote: > Hey guys, what's up? > > Could someone tell me more about bacula-dir.conmsg? Mine is about > 21G... Why this archive has this size? > Thanks!! > ___ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users > ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] About bacula-dir.conmsg
Thanks Bill. Hector B. On Mon, May 2, 2022, 10:35 AM Bill Arlofski via Bacula-users < bacula-users@lists.sourceforge.net> wrote: > On 5/2/22 11:08, Hector Barrera wrote: > > Quick question, where is this file located at? > > > > Please advise. > > > > Hector B. > > It is in the directory configured in the Director's bacula-dir.conf file > as the "Working Directory" and this is different > for different distributions depending on what the package maintainer > decides. > > Hope this helps. > > > Best regards, > Bill > > -- > Bill Arlofski > w...@protonmail.com > ___ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users > ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
