Hello Bill!!!
First of all, thank you so much for your nice email. Really mate, thank
you for your nice answer.
Now, I go answering below in blue bold for instance... for being able to
distinguish better...
El 2022-02-10 19:44, Bill Arlofski via Bacula-users escribió:
> ATENCION
> ATENCION
> ATENCION!!! Este correo se ha enviado desde fuera de la organizacion. No
> pinche en los enlaces ni abra los adjuntos a no ser que reconozca el
> remitente y sepa que el contenido es seguro.
>
> On 2/10/22 10:15, egoitz--- via Bacula-users wrote:
>
>> 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.
>
> Hello egoitz,
>
> I have never heard of such a thing when labeling. The polling cycle to check
> if a volume is available is either 5 or 10
> minutes, which is usually plenty of time to label a new volume.
>
> TOTALLY AGREE. 5 OR 10 MINUTES ARE ENOUGH FOR ONE VOLUME BUT... IMAGINE YOU
> HAVE VOLUMES OF 5GB MAX AND A JOB THEN STARTS AS SOON AS THE VOLUME IS
> AVAILABLE. THEN THAT VOLUME BECOMES FULL BECOSE FILLING A 5GB VOLUME IS
> ABSOLUTELY FAST... THEN YOU SEE THE COMMENTED EFFECT. AT LEAST YOU SEE THAT
> EFFECT IN BACULA 5....
>
> Any reason why you would manually set MaxVolumeBytes? Or manually set
> anything for that matter. Let Bacula manage these
> things for you. :)
>
> You mean setting MaxVolumeBytes in the pool's config and just using this
> directive instead of a later update?. It seems so :) :) nice idea!!!
>
> You should set "MaximumVolumeBytes" in your Pool(s), then, as Bacula creates
> a volume or moves a volume into the pool the
> volume inherits this setting (and some others).
>
> NICE IDEA REALLY :) ... I DIDN'T KNOW THIS DIRECTIVE EXISTED.... IT ALLOWS ME
> NOT TO NEED THE UPDATE COMMAND AFTER LABEL....
>
> Optionally, you can create a scratch pool, set the "ScratchPool" setting in
> your normal pools to this scratch pool and when
> you label a volume, tell it to go into this scratch pool. By default, there
> is a pool called "Scratch" Bacula and treats this
> one special, and will automatically use it to pull media from when a volume
> is needed.
>
> Personally, I prefer to create separate scratch pools for each different
> "MediaType" I have and then also set the
> "RecyclePool" to the same as the "ScratchPool" setting in my pools so Bacula
> puts recycled volumes back into this specific
> scratch pool. This works well when you have (for example) a Full Pool, an Inc
> Pool, and a Diff pool with each using the same
> Scratch and Recycle pool settings. This way volumes don't get "stuck" in one
> of the pools when they are recycled and are
> available to be used in any pool when needed.
>
> WHAT YOU SAID IN THE LAST TWO PARAGRAPHS IS JUST NICE. JUST NICE!.
>
> PLEASE, LET ME COMMENT A COUPLE OF THINGS. WE ARE PLANNING TO BACKUP OUR
> MACHINES WITH CONSOLIDATED VIRTUALFULL + INCREMENTAL BACKUPS FOREVER. SOME OF
> OUR MACHINES TAKE AGES IN BEING BACKED UP AND THIS WAY, AS WE USE "ACCURATE"
> BACKUPS, WE COULD AVOID SOME LOAD ON THAT SERVERS.
>
> FOR THAT PURPOSE, WE HAVE THE INCREMENTAL JOBS POOL AND THE VIRTUAL FULL JOBS
> POOL. BOTH OF THEM SHARE PHISICALLY THE SAME DIRECTORY BECAUSE ELSE, WHEN
> BACULA NEEDS TO READ A PREVIOUS VIRTUAL FULL JOB TERMINATED, IT'S NOT ABLE TO
> FIND CURIOUSLY THE VIRTUAL FULL JOBS VOLUMES IN THEIR OWN POOL (THE POOL FOR
> VOLUMES USED IN VIRTUAL FULL BACKUPS).
>
> YOU SAID THAT FOR HAVING A FULL POOL AND A DIFF POOL AND A INC POOL, USING A
> SCRATCH AND A RECYCLE POOL WORKS NICE. Should it work too, in our progressive
> virtual full scenario?.
>
> Also, you can "stop" a job, do the things you need to do, then 'resume' it -
> Unless you are using Bacula 11.0.5 because in
> this version the stop command actually cancels jobs. This bug has been fixed
> in the coming version though.
>
> I'M USING THIS VERSION, BUT I DON'T REALLY NEED THAT STOP FEATURE IF I CAN
> USE A SCRATCH AND A RECYCLE POOL AS YOU STATED (WE WILL SEE LATER HOW TO
> RESTRICT EACH CUSTOMER'S USED BACKUP BYTES).
>
> And finally, you can set a "LabelFormat" in your disk volume pools (try to
> keep it simple), and set "LabelMedia = yes" in
> your disk devices and Bacula will do this entire job for you automatically.
> Just make sure to also set MaximumVolumes to some
> sensible number so that you do not fill your disk partition(s) to capacity.
> ;)
>
> HIGELY NICE ADVICE TOO MATE :) :) :)
>
> Hope some of this helps. :)
>
> HELPS, ARE YOU JOKING??. IS WHAT I WAS LOOKING FOR !!!!
>
> CAN I TRANSFER YOU SOME € THROUGH PAYPAL FOR INVITING YOU A COFFEE OR BEER?.
>
> THANKS A LOT REALLY AGAIN. PLEASE KEEP MY EMAIL FOR ANY HELP OR THING YOU
> COULD NEED. I WORK AT AN ISP AND IF YOU HAVE SOMETIME, SOME KIND OF NEW DOUBT
> AND I DON'T REALLY KNOW HOW TO ANSWER, I WILL ASK IT INTERNALLY FOR YOU AND
> GIVE YOU AN ANSWER.
>
> Best regards,
> Bill
>
> CHEERS BILL!
>
> --
> Bill Arlofski
> w...@protonmail.com
>
> _______________________________________________
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
