Re: multiple LTOs in the same library

Exuvo <[email protected]> Thu, 18 May 2023 12:13:28 +0200
Newsgroups gmane.comp.archivers.amanda.user
Message-ID <[email protected]>
Here is the relevant part of my config with multiple separated tapes (all LTO5 in my case) in the same MSL2024.
This relies on you having labeled the tapes reasonably as it looks like labelstr can not match the LTO type.
I do not use autolabeling, only manual labeling with a script i run when i put in a new batch of tapes.

labeling script for the box of A***** tapes i have, you can probably modify this to put it in the correct storage pool based on LTO type:
tapes=`mtx -f /dev/tape/by-id/scsi-DEC8320699 status | grep "Storage Element" | grep "Full" | cut -d " " -f 10 | cut -d "=" -f2 | grep -E "^A[0-9]{5}"`
for tape in $tapes; do
    echo -n "Found archive tape $tape"
    new=`grep -c ${tape::-2} /etc/amanda/archive/tapelist`
    if [ "$new" -eq 0 ]; then
       echo -n ". New tape adding.. "
       sudo -u amanda amlabel --barcode "$tape" -f archive "${tape::-2}"
    fi
done

shared amanda conf:
define tapetype LTO5 {
     comment "LTO-5"
     length 1400 gbytes # for scheduling only
     speed 140000 kps # unused
     blocksize 1024 kbytes # optimizing-the-tape-speed.pdf suggest 1MB, manual suggests 256KB. default 32KB
}

weekly conf for 10 rotating tapes:
define policy retention {
     retention-tapes   5 tapes
     retention-days    0
     retention-recover 1 week
#    retention-recover 0
     retention-full    0
}

define storage backup-storage {
     policy "retention"
     tapepool "rotating"
     tpchanger "MSL2024"
     runtapes 2 # max number of tapes used in a single run of amdump
     tapetype "LTO5"
     labelstr "^ROT[0-9]{2,3}$" # label constraint regex: all tapes must match
     taperscan "lexical"
}
storage "backup-storage"

yearly conf with single use box of tapes:
define policy retention {
     retention-tapes  10 tapes
     retention-days    0
     retention-recover 0 week
     retention-full  300
}

define storage archive-storage {
#    policy "retention"
     tapepool "ironmountain"
     tpchanger "MSL2024"
     runtapes 10 # max number of tapes used in a single run of amdump
     tapetype "LTO5"
     labelstr "^A[0-9]{5}$" # label constraint regex: all tapes must match
     taperscan "lexical"
}
storage "archive-storage"

Anton "exuvo" Olsson
    [email protected]

On 2023-05-17 16:06, ASV wrote:
> That's correct, all drives are LTO8, but not all tapes. And no, there
> is no definition of any kind for slot positioning of the LTO7 right
> now.
>
> Thanks for your reply.
>
>
> On Tue, 2023-05-16 at 16:48 +0200, Stefan G. Weichinger wrote:
>> Am 16.05.23 um 16:34 schrieb ASV:
>>> Thanks exuvo, I'll try to dig a bit in that direction even though I
>>> was
>>> expecting some built-in functionality for that.
>> Are the LTO7-tapes always in defined slots?
>>
>> As far as I understand all *drives* are LTO8, but not all *tapes* ?
>>
>>
>>
>>
>>
>