Byte and file progress bars not available

[Joe Prevo]

I'm using Bacularis 2.4.0 with Bacula 13.0.3 and when a job is running, the byte and file progress bars show as not available. Can anyone advise me as to what I might be missing that would cause this. I've searched the web and read all the documents but can't figure out what I'm missing.

Thanks,

Joe

[Marcin Haba]

Hello Joe,

Byte and file progress bars are not displayed for new never run jobs.
You need to have at least one backup job finished for a given level.

For example if you start full backup, to see progress bar you need to
have at least one full backup for this job done. If you start an
incremental backup, to see the progress bar you need to have at least
one incremental backup done.

It is because to see progress bars we need to have an estimated
maximum value that is not available for new jobs.

Best regards,
Marcin Haba (gani)

> --
> You received this message because you are subscribed to the Google Groups "bacularis" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to bacularis+...@googlegroups.com.
> To view this discussion on the web, visit https://groups.google.com/d/msgid/bacularis/7d14072b-599f-4c10-84eb-17962e5dc0b7n%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.



--
"Greater love hath no man than this, that a man lay down his life for
his friends." Jesus Christ

"Większej miłości nikt nie ma nad tę, jak gdy kto życie swoje kładzie
za przyjaciół swoich." Jezus Chrystus

[Joe Prevo]

Ok, that makes sense. That's a clever way to provide estimates.

Joe

[B Smith]

Sorry, one more note: if a job spools, you know the spool bytes, so you could also use that once despooling begins.

[B Smith]

If I might make a suggestion about this, couldn't you use the estimate command to create the estimate for never before run jobs?

On Sunday, February 4, 2024 at 2:08:22 PM UTC-5 Joe Prevo wrote:

[Marcin Haba]

On Sat, 31 Aug 2024 at 09:37, B Smith <*@sheepdot.org> wrote:
>
> Sorry, one more note: if a job spools, you know the spool bytes, so you could also use that once despooling begins.

Hello B,

Thanks for your ideas. Yes, it is true that information about total
estimated size is in the estimate command specially for the file
backup. The spooled size is correct as well. Currently we use the
historical catalog records as the source of data that works if we have
some record(s) in the database.

Maybe in the future we will use the estimate command there. We will
see. At least I think it is a good alternative. Thanks again.