Re: [Bacula-users] Baculum Dashboard Job Status Graph
Hello Tim, That option does not exist in Baculum because always there is displayed job status summary graph for all jobs. However I agree that it could be a very useful option to be able to configure job age for this graph. So I prepared this change in Baculum. You can find it in this commit: https://www.bacula.org/git/cgit.cgi/bacula/commit/?id=92a6104eb10f39c07bec43207182c9a84a6b9fe2 This option to configure age is placed in the application settings (the gear wheel icon on the top left side of the interface). It will be available in the next Baculum release. Thanks! Best regards, Marcin Haba (gani) On Wed, 16 Feb 2022 at 20:58, Goodman, Tim wrote: > Is there a way to configure the date range for the Job Status Graph that > is on the dashboard to the last 24 hours or last week? > ___ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users > -- "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 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Baculum Dashboard Job Status Graph
Is there a way to configure the date range for the Job Status Graph that is on the dashboard to the last 24 hours or last week? ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Reusing schedule resource
Yes, that is what I have done now. I hadn't realised that pools specified in the schedule override those in the job. Best Chris On Wed, 16 Feb 2022, 4:37 pm Bill Arlofski via Bacula-users, < bacula-users@lists.sourceforge.net> wrote: > On 2/16/22 03:55, Chris Wilkinson wrote: > > Is it possible to define two jobs to use the same schedule resource, > i.e. have two jobs to run using the same schedule? > > > > It doesn't seem like that is possible since the schedule resource > requires to specify the pools that are used which would > > usually be different. I wonder if there is a logical reason for > requiring schedules to define the pools used when this info > > is already in the job resource? > > > > Regards > > Chris Wilkinson > > Hello Chris, > > I would recommend to remove the pool specification in the Schedule(s), and > instead use the "FullBackupPool", > "IncrementalBackupPool", and "DifferentialBackupPool" settings in your > Jobs/JobDefs. > > The "Pool" setting is required for a Job, so it must appear in the Job, a > JobDefs that the Job uses (if it uses one), or the > Schedule (if one is used). > > Additionally, if you use the three settings I mentioned above in your Job, > the Pool setting is still required, but will > always be ignored because one of the other three will automatically > override it depending on the Level of the job once the > job starts. > > > Hope this helps, > 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
Re: [Bacula-users] Reusing schedule resource
I have jobs set with priority 10 except for Catalog which is 11. I'll look
into mixed priority, thanks for the tip. I do get Catalog queued up when a
long job runs but it's not a problem.
Best
Chris
On Wed, 16 Feb 2022, 1:58 pm Gary R. Schmidt,
wrote:
> On 17/02/2022 00:18, Chris Wilkinson wrote:
> > I tried a schedule like so to test this out by deleting the Pool= part.
> >
> > Schedule {
> >Name = "archive"
> > # Run = Pool="archive-full" Level="Full" 1st sun at 4:00
> >Run = Level="Full" 1st sun at 4:00
> >Run = Pool="archive-diff" Level="Differential" 2nd-5th sun at 4:00
> >Run = Pool="archive-incr" Level="Incremental" mon-sat at 4:00
> > }
> >
> Look into using the "Priority" setting, my Incremental backups run at
> 48, Differentials at 49, and Fulls at 50. Catalog is at 91.
>
> Oh, and set "Allow Mixed Priority" to Yes to allow lower priority
> (higher number) jobs to start and wait for the higher priority (lower
> number) jobs to finish.
>
> My systems all do Incrementals Tuesday to Friday at 00:01, and different
> groups do either a Differential or Full on Saturday at 00:01 - alas some
> of the fulls now take more than the entire weekend, but we don't do much
> then. :-)
>
> Cheers,
> GaryB-)
>
>
> ___
> 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
Re: [Bacula-users] Reusing schedule resource
On 2/16/22 03:55, Chris Wilkinson wrote: > Is it possible to define two jobs to use the same schedule resource, i.e. > have two jobs to run using the same schedule? > > It doesn't seem like that is possible since the schedule resource requires to > specify the pools that are used which would > usually be different. I wonder if there is a logical reason for requiring > schedules to define the pools used when this info > is already in the job resource? > > Regards > Chris Wilkinson Hello Chris, I would recommend to remove the pool specification in the Schedule(s), and instead use the "FullBackupPool", "IncrementalBackupPool", and "DifferentialBackupPool" settings in your Jobs/JobDefs. The "Pool" setting is required for a Job, so it must appear in the Job, a JobDefs that the Job uses (if it uses one), or the Schedule (if one is used). Additionally, if you use the three settings I mentioned above in your Job, the Pool setting is still required, but will always be ignored because one of the other three will automatically override it depending on the Level of the job once the job starts. Hope this helps, Bill -- Bill Arlofski w...@protonmail.com ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Reusing schedule resource
On 17/02/2022 00:18, Chris Wilkinson wrote:
I tried a schedule like so to test this out by deleting the Pool= part.
Schedule {
Name = "archive"
# Run = Pool="archive-full" Level="Full" 1st sun at 4:00
Run = Level="Full" 1st sun at 4:00
Run = Pool="archive-diff" Level="Differential" 2nd-5th sun at 4:00
Run = Pool="archive-incr" Level="Incremental" mon-sat at 4:00
}
Look into using the "Priority" setting, my Incremental backups run at
48, Differentials at 49, and Fulls at 50. Catalog is at 91.
Oh, and set "Allow Mixed Priority" to Yes to allow lower priority
(higher number) jobs to start and wait for the higher priority (lower
number) jobs to finish.
My systems all do Incrementals Tuesday to Friday at 00:01, and different
groups do either a Differential or Full on Saturday at 00:01 - alas some
of the fulls now take more than the entire weekend, but we don't do much
then. :-)
Cheers,
GaryB-)
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Reusing schedule resource
I tried a schedule like so to test this out by deleting the Pool= part.
Schedule {
Name = "archive"
# Run = Pool="archive-full" Level="Full" 1st sun at 4:00
Run = Level="Full" 1st sun at 4:00
Run = Pool="archive-diff" Level="Differential" 2nd-5th sun at 4:00
Run = Pool="archive-incr" Level="Incremental" mon-sat at 4:00
}
This works fine. I had thought that the pool= was necessary but had misread the
docs and not appreciated the order of precedence of pool defs in job and
schedule resources.
Using the first version of the schedule resource in 2 jobs leads one of the
jobs to use the pool specified in the schedule rather than the one defined in
the job and hence the wrong volumes get written.
Best
-Chris-
> On 16 Feb 2022, at 11:15, Josip Deanovic wrote:
>
> On 2022-02-16 11:55, Chris Wilkinson wrote:
>> Is it possible to define two jobs to use the same schedule resource, i.e.
>> have two jobs to run using the same schedule?
>
> Hi Chris,
>
> Yes, it's possible and it's a common thing.
>
>> It doesn't seem like that is possible since the schedule resource requires
>> to specify the pools that are used which would usually be different. I
>> wonder if there is a logical reason for requiring schedules to define the
>> pools used when this info is already in the job resource?
>
> Definition of a Schedule resource doesn't require pool to be specified.
> Multiple jobs can use the same pool. This is also a common thing.
>
>
> Regards!
>
> --
> Josip Deanovic
>
>
> ___
> 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
Re: [Bacula-users] Reusing schedule resource
On 2022-02-16 11:55, Chris Wilkinson wrote: Is it possible to define two jobs to use the same schedule resource, i.e. have two jobs to run using the same schedule? Hi Chris, Yes, it's possible and it's a common thing. It doesn't seem like that is possible since the schedule resource requires to specify the pools that are used which would usually be different. I wonder if there is a logical reason for requiring schedules to define the pools used when this info is already in the job resource? Definition of a Schedule resource doesn't require pool to be specified. Multiple jobs can use the same pool. This is also a common thing. Regards! -- Josip Deanovic ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Reusing schedule resource
Is it possible to define two jobs to use the same schedule resource, i.e. have two jobs to run using the same schedule? It doesn't seem like that is possible since the schedule resource requires to specify the pools that are used which would usually be different. I wonder if there is a logical reason for requiring schedules to define the pools used when this info is already in the job resource? Regards Chris Wilkinson ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Remote FD cannot authenticate to local LAN SD
Show your version Dir, Sd and fd remote. On Mon, Feb 14, 2022 at 1:16 PM JD Atkinson wrote: > I have a SD system on a local LAN, that can back itself up, and backup > another server on the LAN no problem. > > Across a routed network, is an FD that tests fine for "bconsole status > client". > In none of my configurations will you find "localhost", and IP addresses > are used for all Address entries. > > When I "console status network" for the problem FD, I get the debug > below. I have an extremely similar configuration for the working local LAN > FD and the remote FD, but the local one works fine and the remote routed > one does not. > > There are no firewalls, no hosts.allow/deny, and network port connections > are possible and properly connect according to hand tests and the debug. > > The debug shows both the SD and the problem remote FD when tested. > Why does the SD say "Recv caps from Client failed"? > Why does the FD say "Recv caps from SD failed."? > > Bacula 11.0.0 all around, no inconsistencies there. > The working local FD runs Debian 10 > The problem remote FD runs Amazon EC2 (connection via VPN, but no > firewalls, filters, etc blocking network access as you can see from the > debug) > > --- > SD debug > --- > > atkinsonsvr-sd: dircmd.c:248-0 Do command: JobId= > > atkinsonsvr-sd: job.c:78-0 job=-Console-.2022-02-14_15.58.20_03 job_name=Backup_atkinsonsvr > client_name=jdatkinson-fd type=85 level=32 FileSet=atkinsonsvrFullSet > NoAttr=0 SpoolAttr=1 FileSetMD5=**Dummy** SpoolData=0 WritePartAfterJob=1 > PreferMountedVols=1 SpoolSize=0 rerunning=0 VolSessionId=1 > VolSessionTime=1644854291 sd_client=0 Authorization= > > atkinsonsvr-sd: job.c:100-0 rerunning=0 VolSesId=1 VolSesTime=1644854291 > > atkinsonsvr-sd: job.c:112-0 Start JobId=0 7fe5c800b098 > > atkinsonsvr-sd: job.c:158-0 >dird jid=0: 3000 OK Job SDid=2 > SDtime=1644854291 Authorization=CDCG-GGMK-IKNJ-APMJ-GLME-OPAI-CCIL-DNEE > > atkinsonsvr-sd: sd_plugins.c:285-0 === enter new_plugins === > > atkinsonsvr-sd: sd_plugins.c:287-0 No sd plugin list! > > atkinsonsvr-sd: sd_plugins.c:104-0 No b_plugin_list: generate_plugin_event > ignored. > > atkinsonsvr-sd: mem_pool.c:617-0 max_size=512 > > atkinsonsvr-sd: events.c:48-0 Events: code=SJ0001 daemon=atkinsonsvr-sd > ref=0x7fe5c800b098 type=job source=atkinsonsvr-dir text=Job Start jobid=0 > job=-Console-.2022-02-14_15.58.20_03 > > atkinsonsvr-sd: message.c:1534-0 Enter Jmsg type=17 > > atkinsonsvr-sd: dircmd.c:234-0 > atkinsonsvr-sd: dircmd.c:248-0 Do command: run > > atkinsonsvr-sd: job.c:182-0 Run_cmd: run > > atkinsonsvr-sd: jcr.c:936-0 set_jcr_job_status(0, F) > > atkinsonsvr-sd: jcr.c:945-0 OnEntry JobStatus=C newJobstatus=F > > atkinsonsvr-sd: jcr.c:956-0 Set new stat. old: C,0 new: F,0 > > atkinsonsvr-sd: jcr.c:961-0 leave setJobStatus old=C new=F > > atkinsonsvr-sd: job.c:192-0 sd_calls_client=0 sd_client=0 > > atkinsonsvr-sd: job.c:214-0 -Console-.2022-02-14_15.58.20_03 waiting 1800 > sec for FD to contact SD key=CDCG-GGMK-IKNJ-APMJ-GLME-OPAI-CCIL-DNEE > > atkinsonsvr-sd: job.c:216-0 === Block Job=-Console-.2022-02-14_15.58.20_03 > jid=0 7fe5c800b098 > > atkinsonsvr-sd: bsock.c:861-0 socket=6 who=client host=10.120.0.1 port=9103 > > atkinsonsvr-sd: bnet_server.c:235-0 Accept > socket=10.0.2.10.9103:10.120.0.1.56060 s=0x563e9764ced8 > > atkinsonsvr-sd: hello.c:161-0 authenticate: Hello Bacula SD: Start Job > -Console-.2022-02-14_15.58.20_03 14 tlspsk=0 > > atkinsonsvr-sd: hello.c:188-0 Found Client Job > -Console-.2022-02-14_15.58.20_03 > > atkinsonsvr-sd: hello.c:199-0 fd_version=14 sd_version=0 > > atkinsonsvr-sd: hello.c:431-0 >Send sdcaps: dedup=0 hash=1 > dedup_block=65536 min_dedup_block=1024 max_dedup_block=66556 > > atkinsonsvr-sd: hello.c:452-0 Recv caps from Client failed. ERR=Connection > reset by peer > > atkinsonsvr-sd: message.c:1534-0 Enter Jmsg type=3 > > atkinsonsvr-sd: hello.c:453-0 Recv caps from Client failed. ERR=Connection > reset by peer > > atkinsonsvr-sd: bsockcore.c:1112-0 BSOCKCORE::destroy() > > atkinsonsvr-sd: bsockcore.c:1125-0 BSOCKCORE::destroy():delete(this) > > atkinsonsvr-sd: bsock.c:90-0 BSOCK::~BSOCK() > > atkinsonsvr-sd: bsock.c:110-0 BSOCK::_destroy() > > atkinsonsvr-sd: bsockcore.c:200-0 BSOCKCORE::~BSOCKCORE() > > atkinsonsvr-sd: bsockcore.c:1079-0 BSOCKCORE::_destroy() > > atkinsonsvr-sd: bsockcore.c:1043-0 BSOCKCORE::close() > > atkinsonsvr-sd: job.c:229-0 === Auth cond errstat=0 > > --- > FD Debug > --- > > jdatkinson-fd: job.c:375-0 Executing Dir storage address=10.0.2.10 > port=9103 ssl=0 > > command. > > jdatkinson-fd: job.c:2670-0 StorageCmd: storage address=10.0.2.10 > port=9103 ssl=0 > > jdatkinson-fd: job.c:2697-0 Connect to storage: 10.0.2.10:9103 ssl=0 > > jdatkinson-fd: watchdog.c:197-0 Registered watchdog 7f8c6400c138, interval > 1800 one shot > > jdatkinson-fd: btimers.c:145-0 Start thread timer 7f8c6400cb68 tid > 7f8c6d25e700 for 1800 secs. > > jdatkinson-fd:
