BAT seems not to use the Maximum Volume Bytes when it calculates the % used
(it uses the average amount used per tape for each MediaType according to the
source code).
"Better" is subjective, but I think Maximum Volume Bytes is meaningless if you
use hardware compression on the tapes (unless you don't care about wasting
tape space).
__Martin
>>>>> On Fri, 8 Sep 2017 13:52:22 +0000, Hicks, Daniel CTR OSD DMEA said:
>
> Hello,
>
>
>
> I am using Bacula 9.0.3 on Centos7 and have the following issue when
> reviewing storage from bat. I am using LTO-5 tapes that are 1.5TB raw and
> 3TB compressed. I believe that I have set the Bacula-dir.conf tape pool
> definition correctly but when I look at bat after a single job wrote to
> tape. That job consisting of 479MG in size but bat reports that 48% of the
> tape is used.
>
>
>
> Please let me know if there is better way to define the tapes and if so
> where and how.
>
>
>
>
>
> # Tape pool definition
>
> Pool {
>
> Name = Tape
>
> Pool Type = Backup
>
> Recycle = yes
>
> AutoPrune = yes
>
> Volume Retention = 5 years
>
> Maximum Volume Bytes = 1500G
>
> Storage = HP-Overland-TL
>
> }
>
>
>
> Thanks
>
>
>
> Daniel Hicks
>
> Senior Systems Analyst
>
> DMEA IT Support
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
