Library auto-cleaning problem

1,008 views
Skip to first unread message

Adam Thompson

unread,
Jan 3, 2016, 2:37:53 PM1/3/16
to bareos-users
Hi,
I'm noticing that my library needs cleaning fairly regularly, and isn't getting cleaned automatically like I expect.

I'm currently running
* bareos-15.4.0.git.1450454374.ccd5008-1181.1.el6.x86_64.
* Dell PowerVault TL1000 - LTO6 (an OEM'd IBM TS2900 type 3572-HH6)

The library is configured as "6+1" slots, which means of its 10 slots, six are reserved for data tapes, one for a cleaning tape, one for "slack" space to shuttle tapes around, and two (one double-stacked slot) for I/O.

There is a cleaning tape in the library (barcode "CLNU00CU").

The library is configured to NOT auto-clean on its own, because Bareos theoretically should be doing it. *****Yes, I see the problem now. (Before hitting send, for a change!) See below for the other part of the question.*****

My bareos-sd.conf (minus the File storage and Director section):

=====
Storage {
Name = backup1-sd
Maximum Concurrent Jobs = 20
Plugin Directory = /usr/lib64/bareos/plugins
Plugin Names = autoxflate scsitapealert
NDMP Enable = yes
}
Device {
Name = "tapedrive-tl1000"
DeviceType = tape
ArchiveDevice = /dev/tape/by-id/scsi-350016977299e1010-nst
MediaType = LTO6
Check Labels = yes
LabelMedia = yes
AutoChanger = yes
AutomaticMount = yes
MaximumBlockSize = 1M
MaximumFileSize = 50GB
AutoInflate = both
Drive Tape Alert Enabled = yes
Spool Directory = /backups/spool
}
Autochanger {
Name = "autochanger-tl1000"
Changer Device = /dev/tape/by-id/scsi-1IBM_3572-TL_0000068403931001
Device = tapedrive-tl1000
Changer Command = "/usr/lib/bareos/scripts/mtx-changer %c %o %S %a %d"
}
Messages {
Name = Standard
director = backup1-dir = all
}
=====


Um. I just found the sentence in the docs where is says Bareos' autochanger support doesn't include cleaning. So, that explains why Bareos isn't cleaning the drive! Duh.

However, my library will only auto-clean if the drive is empty, and Bareos leaves a tape in the drive at all times by default.

I can run "release storage=TL1000 alldrives" manually, which of course works and allows auto-cleaning to work, but is there a better way to have Bareos unload the tape at the end of the day's runs so that autocleaning can happen?

As it is, if I turn on autocleaning for the library, the cleaning run happens when Bareos tries to load a new tape, and it can take long enough that Bareos times out.

Also, I'm finding that the drive is asking for cleaning about once a week. I'm backing up ~2-3TB per night to LTO6 tapes; does this sound normal for that volume of data?

-Adam

Marco van Wieringen

unread,
Jan 4, 2016, 4:55:56 AM1/4/16
to bareos...@googlegroups.com
On 01/ 3/16 08:37 PM, Adam Thompson wrote:
> Hi,
> I'm noticing that my library needs cleaning fairly regularly, and isn't getting cleaned automatically like I expect.
>
> I'm currently running
> * bareos-15.4.0.git.1450454374.ccd5008-1181.1.el6.x86_64.
> * Dell PowerVault TL1000 - LTO6 (an OEM'd IBM TS2900 type 3572-HH6)
>

Honestly if your drive needs cleaning regularly its either dying, you use very
bad tapes or it collecting dust. Normally you need cleaning very few times anything
else shows problems with the hardware. I cleaned my LTO4 drive maybe 2 or 3 times
the last 3 years.

So if you have support on the hardware I would run some diagnostic software
and get the drive swapped for a proper working one.

--
Marco van Wieringen marco.van...@bareos.com
Bareos GmbH & Co. KG Phone: +49-221-63069389
http://www.bareos.com

Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646
Komplementär: Bareos Verwaltungs-GmbH
Geschäftsführer: Stephan Dühr, M. Außendorf, J. Steffens,
P. Storz, M. v. Wieringen

Adam Thompson

unread,
Feb 17, 2016, 2:36:26 PM2/17/16
to Marco van Wieringen, bareos-users
Update:

I talked to Dell support.  On the LTO6 half-height drives, they specify that cleaning will required after every 40-50 hours of drive usage.  This is substantially more often than LTO3 or LTO4 drives required.  Newer firmware revisions for the drive are gradually getting more relaxed about needing cleaning.  And apparently the new generation of LTO6 tapes (like the new HP BaFe media) should drastically reduce the cleaning requirements over the legacy MP (metal-particle) tapes.

Naturally, Dell insists that my use of non-Dell-branded tapes is part of the problem ;-).  Even though Dell tapes are actually OEM'd FujiFilm tapes in the first place...


Based on running full backups, we're hitting 40 to 50 hours of on-head tape usage every two weeks or so.

So apparently this level of cleaning is actually normal for this drive.

(Dell TL1000, which is actually an IBM TS2600 (type 3572-TL) with an IBM ULT3580-HH6 drive)



I still wish there was a way to tell Bareos to automatically unload the tape after X hours of inactivity, so that the library auto-cleaning could kick in, instead of me having to do it manually.

There's a TapeAlert plugin, could that be extended to do auto-eject the tape if the drive requires cleaning after a backup job runs?  Except that despite having that plugin enabled, I don't see anything in the Bareos logs - it's the library emailing me to request cleaning...



Avant logo Adam Thompson
Senior Systems Administrator
voice: 204.789.9596 x24email: atho...@avant.ca | web: avant.ca

--
You received this message because you are subscribed to a topic in the Google Groups "bareos-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/bareos-users/6OA6NZQQKuk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to bareos-users...@googlegroups.com.
To post to this group, send email to bareos...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Marco van Wieringen

unread,
Feb 19, 2016, 2:55:05 PM2/19/16
to bareos...@googlegroups.com
On 02/17/16 08:36 PM, Adam Thompson wrote:
> Update:
>
> I talked to Dell support. On the LTO6 half-height drives, they specify that cleaning will required after every 40-50 hours of drive usage. This is substantially more often than LTO3 or LTO4 drives required. Newer firmware revisions for the drive are gradually getting more relaxed about needing cleaning. And apparently the new generation of LTO6 tapes (like the new HP BaFe media) should drastically reduce the cleaning requirements over the legacy MP (metal-particle) tapes.
>
> Naturally, Dell insists that my use of non-Dell-branded tapes is part of the problem ;-). Even though Dell tapes are actually OEM'd FujiFilm tapes in the first place...
>
>
> Based on running full backups, we're hitting 40 to 50 hours of on-head tape usage every two weeks or so.
>
> So apparently this level of cleaning is actually normal for this drive.
>
> (Dell TL1000, which is actually an IBM TS2600 (type 3572-TL) with an IBM ULT3580-HH6 drive)
>
>
>
> I still wish there was a way to tell Bareos to automatically unload the tape after X hours of inactivity, so that the library auto-cleaning could kick in, instead of me having to do it manually.
>
You could pick a time that works for you and have an Admin Job that releases the drive.
That will unload the drive (but use release and NOT unmount as that blocks the drive).

> There's a TapeAlert plugin, could that be extended to do auto-eject the tape if the drive requires cleaning after a backup job runs? Except that despite having that plugin enabled, I don't see anything in the Bareos logs - it's the library emailing me to request cleaning...
>
The TapeAlert plugin only captures the low level SCSI TapeAlert info and inserts it into
the database for now. One day we should have it visible in the webui so you can based on
this info look at drives and tapes and see how they behaved over time. You could unload
the plugin and fall back to the old alert command in the SD definition and possibly write
some script that does the hard work. Extending the TapeAlert to interpret the TapeAlert
info is possible only there is no consumer of such events as the current plugin interface
works on a per Job basis so you need some other plugin to react on an event. Again its all
available so you can hack whatever you like but I would settle on releasing the drive at
some time you think is convenient. If you play with the priorities of the Admin Jobs you
may even be able to have it being suspended if it kicks in to early on any running Job.
Not sure however if Admin Jobs fully play well with priorities etc.

Adam Thompson

unread,
Mar 1, 2016, 12:30:13 PM3/1/16
to Marco van Wieringen, bareos-users
On Fri, Feb 19, 2016 at 1:54 PM, Marco van Wieringen <marco.van...@bareos.com> wrote:
On 02/17/16 08:36 PM, Adam Thompson wrote:
> I still wish there was a way to tell Bareos to automatically unload the tape after X hours of inactivity, so that the library auto-cleaning could kick in, instead of me having to do it manually.

You could pick a time that works for you and have an Admin Job that releases the drive.
That will unload the drive (but use release and NOT unmount as that blocks the drive).

​So far, this works acceptably well.  I have a window every day during which no backup should ever be running​
 
​.  Thankfully, releasing the drive does allow the library to auto-clean.

​Thank you,

-Adam

Reply all
Reply to author
Forward
0 new messages