Good afternoon,
If you have a pool in a "Non appendable volumes" state, with jobs in a
awaiting storage state so running, and you try to add some new volumes,
each one with a specific capacity, as you launch the label command for
this purpose in bconsole, the new volume gets started using at just that
very brief moment. This causes you, to unable to then finish, that label
command or at least the impossibility of running later a "update volume"
command, for fixing the max volume size.
Can a pool or a catalogue, be able to be set in some sort of "pause"
state in a moment that it's in a "Non appendable volumes" state, in
order to be able to provide the needed (and required) storage for tasks
to continue and end successfully?
Thanks a lot in advance,
Best regards,
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users