Am 2017-01-18 um 16:08 schrieb Stefan G. Weichinger:
> Am 2017-01-18 um 15:44 schrieb Jean-Louis Martineau:
>
>>> OK, so I created an extra policy-block for each storage and adjusted
>>> "retention-days". Works! "tapecycle" can be removed then?
>
>> tapecycle global setting can be removed yet, like many others global
>> setting, some code still use them instead of the storage setting.
>
> You mean "can't be removed yet", right?
>
> Which value to use for tapecycle then, if I have 2 different settings
> for 2 storages?
additional question regarding:
dump-selection [string | ALL] [ ALL | FULL | INCR ]
Default: no default. The dump-selection specify which dump will be
written to the storage. The first field is the tag, either it is ALL and
all DLEs matches or it is a tag string and a dle match only if it have
that tag. The second field is the level, it can be ALL for all level,
FULL for level 0 only or INCR for level > 0 only.
Isn't the default then implicitly "ALL ALL" ?
Could you provide real-world examples, please, on how to use that?
