Re: [Bacula-users] Adding volumes (in a file type storage) while tasks are awaiting free storage
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. Any reason why you would manually set MaxVolumeBytes? Or manually set anything for that matter. Let Bacula manage these things for you. :) 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). 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. 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. 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. ;) Hope some of this helps. :) Best regards, 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] Adding volumes (in a file type storage) while tasks are awaiting free storage
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
Re: [Bacula-users] Bacula 11 and Forever virtualfull plus incrementals
Hi!
I think I solved it. I have defined the path in "Archive Device" of the
Device, defined in bacula-sd.conf, to point to the same directory as the
path in "Archive Device" of the Device for incremental backups. I have
read this advice in "Bacula : Network backup strategies and solutions".
I think I have understood too how virtual buff behaves and how job
dependency works finally :) :)
Thank you so much,
Best regards,
El 2022-02-10 08:57, ego...@ramattack.net escribió:
> Hi!,
>
> Concretely for all this set up I have borrowed ideas from
> https://www.bacula.lat/bacula-virtual-synthetic-full-and-forever-incremental-backups/?lang=es
>
>
> But it seems not to work as its... directly
>
> Cheers!
>
> El 2022-02-09 19:48, egoitz--- via Bacula-users escribió:
>
>> ATENCION: Este correo se ha enviado desde fuera de la organización. No
>> pinche en los enlaces ni abra los adjuntos a no ser que reconozca el
>> remitente y sepa que el contenido es seguro.
>>
>> Good afternoon,
>>
>> I have been trying to configure Bacula 11 with PostgreSQL 12 as database
>> backend. (Have not seen a more advisable combination...)
>>
>> One of my goals, was to be able to do only once a first full backup and
>> later each day run an incremental backup.
>>
>> Basically I wanted to have :
>>
>> - Four month of virtualfull backup (so 4 virtual full backup) that have been
>> done in the first day of each month. Perhaps an incremental one really too,
>> after this virtual full backup of the first day of the month.
>>
>> - The rest of the days of these 4 month I would do incremental backups from
>> it's parent virtual full.
>>
>> - So, I wanted to have a virtual full backup per month, done the first day
>> of each month for having more "handy or easy" restoration, from any of the
>> following incremental backup.
>>
>> For achieving that, I have configured (I put just what I consider that are
>> the relevant parts only ) :
>>
>> + IN THE SD
>>
>> Device {
>> Name = FileStorage-BACK99
>> Media Type = File
>> Archive Device = /expert/baculadata/LIBRERIA/LIBRERIA-BACK99
>> LabelMedia = yes; # lets Bacula label unlabeled media
>> Random Access = Yes;
>> AutomaticMount = yes; # when device opened, read it
>> RemovableMedia = no;
>> AlwaysOpen = no;
>> Maximum Concurrent Jobs = 5
>> }
>>
>> Device {
>> Name = FileStorage-BACK99-VF
>> Media Type = File
>> Archive Device = /expert/baculadata/LIBRERIA/LIBRERIA-BACK99-VF
>> LabelMedia = yes; # lets Bacula label unlabeled media
>> Random Access = Yes;
>> AutomaticMount = yes; # when device opened, read it
>> RemovableMedia = no;
>> AlwaysOpen = no;
>> Maximum Concurrent Jobs = 5
>> }
>>
>> Device {
>> Name = FileStorageRestore-BACK99
>> Media Type = File
>> Archive Device = /expert/baculadata/LIBRERIA/LIBRERIA-BACK99R
>> LabelMedia = yes; # lets Bacula label unlabeled media
>> Random Access = Yes;
>> AutomaticMount = yes; # when device opened, read it
>> RemovableMedia = no;
>> AlwaysOpen = no;
>> Maximum Concurrent Jobs = 5
>> }
>>
>> + In the dir
>>
>> Storage {
>> Name = File-BACK99
>> Address = node05.cloudbackup.ramattack.net
>> SDPort = 9103
>> Password = "the-password-used"
>> Device = FileStorage-BACK99
>> Media Type = File
>> Maximum Concurrent Jobs = 5
>> TLS Enable = Yes
>> TLS Require = Yes
>> TLS CA Certificate File = "/usr/local/etc/bacula/cacert.pem"
>> TLS Certificate =
>> "/usr/local/etc/bacula/node05.cloudbackup.ramattack.net-cert.pem"
>> TLS Key = "/usr/local/etc/bacula/node05.cloudbackup.ramattack.net-key.pem"
>> }
>>
>> Storage {
>> Name = FileStorage-BACK99-VF
>> Address = node05.cloudbackup.ramattack.net
>> SDPort = 9103
>> Password = "the-password-used"
>> Device = FileStorage-BACK99-VF
>> Media Type = File
>> Maximum Concurrent Jobs = 5
>> TLS Enable = Yes
>> TLS Require = Yes
>> TLS CA Certificate File = "/usr/local/etc/bacula/cacert.pem"
>> TLS Certificate =
>> "/usr/local/etc/bacula/node05.cloudbackup.ramattack.net-cert.pem"
>> TLS Key = "/usr/local/etc/bacula/node05.cloudbackup.ramattack.net-key.pem"
>> }
>>
>> Storage {
>> Name = FileRestore-BACK99
>> Address = node05.cloudbackup.ramattack.net
>> SDPort = 9103
>> Password = "the-password-used"
>> Device = FileStorageRestore-BACK99
>> Media Type = File
>> Maximum Concurrent Jobs = 5
>> TLS Enable = Yes
>> TLS Require = Yes
>> TLS CA Certificate File = "/usr/local/etc/bacula/cacert.pem"
>> TLS Certificate =
>> "/usr/local/etc/bacula/node05.cloudbackup.ramattack.net-cert.pem"
>> TLS Key = "/usr/local/etc/bacula/node05.cloudbackup.ramattack.net-key.pem"
>> }
>>
>> AS JOB IN BACULA CONFIG :
>>
>> JobDefs {
>> Name =
>> "backed-up-vm-by-bacula-server.clientes.cloudbackup.ramattack.net-fd_defs"
>> Client =
>> "backed-up-vm-by-bacula-server.clientes.cloudbackup.ramattack.net-fd"
>> Messages = GENERAL05
>> Priority
Re: [Bacula-users] Bacula 11 and Forever virtualfull plus incrementals
Hi!,
Concretely for all this set up I have borrowed ideas from
https://www.bacula.lat/bacula-virtual-synthetic-full-and-forever-incremental-backups/?lang=es
But it seems not to work as its... directly
Cheers!
El 2022-02-09 19:48, egoitz--- via Bacula-users escribió:
> ATENCION: Este correo se ha enviado desde fuera de la organización. No pinche
> en los enlaces ni abra los adjuntos a no ser que reconozca el remitente y
> sepa que el contenido es seguro.
>
> Good afternoon,
>
> I have been trying to configure Bacula 11 with PostgreSQL 12 as database
> backend. (Have not seen a more advisable combination...)
>
> One of my goals, was to be able to do only once a first full backup and later
> each day run an incremental backup.
>
> Basically I wanted to have :
>
> - Four month of virtualfull backup (so 4 virtual full backup) that have been
> done in the first day of each month. Perhaps an incremental one really too,
> after this virtual full backup of the first day of the month.
>
> - The rest of the days of these 4 month I would do incremental backups from
> it's parent virtual full.
>
> - So, I wanted to have a virtual full backup per month, done the first day of
> each month for having more "handy or easy" restoration, from any of the
> following incremental backup.
>
> For achieving that, I have configured (I put just what I consider that are
> the relevant parts only ) :
>
> + IN THE SD
>
> Device {
> Name = FileStorage-BACK99
> Media Type = File
> Archive Device = /expert/baculadata/LIBRERIA/LIBRERIA-BACK99
> LabelMedia = yes; # lets Bacula label unlabeled media
> Random Access = Yes;
> AutomaticMount = yes; # when device opened, read it
> RemovableMedia = no;
> AlwaysOpen = no;
> Maximum Concurrent Jobs = 5
> }
>
> Device {
> Name = FileStorage-BACK99-VF
> Media Type = File
> Archive Device = /expert/baculadata/LIBRERIA/LIBRERIA-BACK99-VF
> LabelMedia = yes; # lets Bacula label unlabeled media
> Random Access = Yes;
> AutomaticMount = yes; # when device opened, read it
> RemovableMedia = no;
> AlwaysOpen = no;
> Maximum Concurrent Jobs = 5
> }
>
> Device {
> Name = FileStorageRestore-BACK99
> Media Type = File
> Archive Device = /expert/baculadata/LIBRERIA/LIBRERIA-BACK99R
> LabelMedia = yes; # lets Bacula label unlabeled media
> Random Access = Yes;
> AutomaticMount = yes; # when device opened, read it
> RemovableMedia = no;
> AlwaysOpen = no;
> Maximum Concurrent Jobs = 5
> }
>
> + In the dir
>
> Storage {
> Name = File-BACK99
> Address = node05.cloudbackup.ramattack.net
> SDPort = 9103
> Password = "the-password-used"
> Device = FileStorage-BACK99
> Media Type = File
> Maximum Concurrent Jobs = 5
> TLS Enable = Yes
> TLS Require = Yes
> TLS CA Certificate File = "/usr/local/etc/bacula/cacert.pem"
> TLS Certificate =
> "/usr/local/etc/bacula/node05.cloudbackup.ramattack.net-cert.pem"
> TLS Key = "/usr/local/etc/bacula/node05.cloudbackup.ramattack.net-key.pem"
> }
>
> Storage {
> Name = FileStorage-BACK99-VF
> Address = node05.cloudbackup.ramattack.net
> SDPort = 9103
> Password = "the-password-used"
> Device = FileStorage-BACK99-VF
> Media Type = File
> Maximum Concurrent Jobs = 5
> TLS Enable = Yes
> TLS Require = Yes
> TLS CA Certificate File = "/usr/local/etc/bacula/cacert.pem"
> TLS Certificate =
> "/usr/local/etc/bacula/node05.cloudbackup.ramattack.net-cert.pem"
> TLS Key = "/usr/local/etc/bacula/node05.cloudbackup.ramattack.net-key.pem"
> }
>
> Storage {
> Name = FileRestore-BACK99
> Address = node05.cloudbackup.ramattack.net
> SDPort = 9103
> Password = "the-password-used"
> Device = FileStorageRestore-BACK99
> Media Type = File
> Maximum Concurrent Jobs = 5
> TLS Enable = Yes
> TLS Require = Yes
> TLS CA Certificate File = "/usr/local/etc/bacula/cacert.pem"
> TLS Certificate =
> "/usr/local/etc/bacula/node05.cloudbackup.ramattack.net-cert.pem"
> TLS Key = "/usr/local/etc/bacula/node05.cloudbackup.ramattack.net-key.pem"
> }
>
> AS JOB IN BACULA CONFIG :
>
> JobDefs {
> Name =
> "backed-up-vm-by-bacula-server.clientes.cloudbackup.ramattack.net-fd_defs"
> Client =
> "backed-up-vm-by-bacula-server.clientes.cloudbackup.ramattack.net-fd"
> Messages = GENERAL05
> Priority = 10
> }
>
> Job {
> Name =
> "backed-up-vm-by-bacula-server.clientes.cloudbackup.ramattack.net-fd_copia"
> JobDefs =
> "backed-up-vm-by-bacula-server.clientes.cloudbackup.ramattack.net-fd_defs"
> Type = Backup
> Schedule = "SEMANAL_MIERCOLES_1800"
> Messages = GENERAL05
> ##Max Full Interval = 7 days no sense when using virtualfulls I
> assume...
> Backups To Keep = 32
> DeleteConsolidatedJobs = yes
> Pool = catalogo_BACK99_incrementales
> NextPool = catalogo_BACK99_VF
> Reschedule On Error = Yes
> Reschedule Interval = 10 minutes
> Reschedule Times = 5
> Max Wait Time = 7200
> Accurate = Yes
>
Re: [Bacula-users] Too Big? 11.0.5/FreeBSD Ports
On 2022-02-10 05:21, Larry Rosenman wrote: [snip] Looks like it was my firewall not allowing an ESTABLISHED session over 2 hours. I've increased it to 1 Day, and all seems(!) better. You might want to turn on Heart Beat Interval, both in the File daemon and the Storage daemon. You can set it to a minute or maybe 5 minutes or so. Regards! -- Josip Deanovic ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
