V*list media pool=Windows-Full-Pool
+-+---+---+-+---+--+--+-+--+---+
---+-+
| MediaId | VolumeName| VolStatus | Enabled | VolBytes |
VolFiles | VolRetention |
Tom Epperly schrieb:
> Ralf Gross wrote:
>> Tom Epperly schrieb:
>>
>>> I don't understand why bacula seems to automatically create volumes
>>> for some pools, but forces me to use the "label" command for others.
>>> I've tried increasing the "Maximum Volumes" setting, but it doesn't
>>> se
Ralf Gross wrote:
Tom Epperly schrieb:
I don't understand why bacula seems to automatically create volumes for
some pools, but forces me to use the "label" command for others. I've
tried increasing the "Maximum Volumes" setting, but it doesn't seem to
help.
Have set 'LabelMedia =
Tom Epperly schrieb:
> I don't understand why bacula seems to automatically create volumes for
> some pools, but forces me to use the "label" command for others. I've
> tried increasing the "Maximum Volumes" setting, but it doesn't seem to
> help.
Have set 'LabelMedia = yes' in the Device co
2009/12/18 Tom Epperly :
> I don't understand why bacula seems to automatically create volumes for some
> pools, but forces me to use the "label" command for others. I've tried
> increasing the "Maximum Volumes" setting, but it doesn't seem to help.
>
> For example, these pools seem to automaticall
I don't understand why bacula seems to automatically create volumes for
some pools, but forces me to use the "label" command for others. I've
tried increasing the "Maximum Volumes" setting, but it doesn't seem to help.
For example, these pools seem to automatically generate named files
named U
