Heiko,
What's the autolabel setting?
Do you allow config monthly to relabel tape from other config?
Jean-Louis
On 05/21/2014 07:32 AM, Heiko Schlittermann wrote:
Jean-Louis Martineau <[email protected]> (Mi 21 Mai 2014 13:08:33 CEST):
Heiko,
Can you post a lot more information to correctly describe the problem?
I've two configs
common to both configs:
define taperscan "dtele" {
plugin "XXX"
}
taperscan "dtele"
daily: labelstr "^daily\\.\\d+$"
monthly: labelstr "^monthly\\.\\d+$"
Each configuration uses an own tapelist file. But both
use the same changer/device configuration.
amtape <conf> inventory outputs the same for both configs:
slot 1: label daily.11 barcode A00011L5 (in drive 0)
slot 2: unknown state
slot 3: label daily.02 barcode A00002L5 (current)
slot 4: label daily.01 barcode A00001L5
slot 5: label daily.13 barcode A00013L5
slot 6: label daily.06 barcode A00006L5
slot 7: unknown state
slot 8: unknown state
The changer contains only "daily" tapes currently.
With XXX being "traditional" I get the expected results:
$ amtape monthly taper
found in slot 3: volume 'daily.02'
slot 3: volume 'daily.02' does not match labelstr (?^:^monthly\.\d+$)
~~~~~~~~~~~~~~~~~~~
private "patch"
to display the
regexp as regexp
… and so on
$ _
$ amtape daily taper
Searching for label 'daily.02': found in slot 3: volume 'daily.02'
Will write to volume 'daily.02' in slot 3.
$ _
With XXX being "lexial" I get
$ amtape daily taper
slot 3: volume 'daily.02'
Will write to volume 'daily.02' in slot 3.
$ _
$ amtape monthly taper
slot 1: volume 'daily.11'
Will write to volume 'daily.11' in slot 1.
$ _
daily.11 contains the last but one recent daily backup!!!
Overwriting it would be a bad idea!
Because I have "daily" tapes in may changer, the output of the "amtape
daily taper" is as I expected. But for "amtape monthly taper" I'd expect
something similiar to the "traditional" algorithm - a labelstr mismatch.
