Re: postgres load at restore

On 8/29/24 20:28, Marcin Haba wrote:
> On Fri, 30 Aug 2024 at 01:22, Phil Stracchino <[email protected] 
> <mailto:[email protected]>> wrote:
> 
>      > Yes, I see your idea. This full rebuild will cost creating all cache
>      > from scratch. For many jobs and paths it will take lots of resources.
> 
>     Well, I just tested my revised dbcheck script with inline bvfs cache
>     clear and rebuild, and it worked fine, runs for about two hours.  My
>     bvfs update job to run after all backups needs a little work though.
>     The job definition looks like this:
> 
> 
> Hello Phil,
> 
> Great. Two hours isn't that bad.
> 
>     But when run manually from BAT, BAT won't let me specify a level, runs
>     .bvfs_update with an empty level, then errors out because "" is not a
>     valid level.
> 
> 
>   It looks like a bug.


It LOOKS as though when run by the Director from the schedule, it 
completed successfully according to the Jobs Run log.  It generates TWO 
notification mail messages, though, the first of which has subject 
"-RunScript- ( ) Unknown term code" and contains only the following:

30-Aug 05:30 minbar-dir JobId 0: Using Catalog "Catalog"

The second looks like this:

Subject: BVFS_Update (Full) OK
Date: Fri, 30 Aug 2024 05:30:29 -0400
X-Original-To: [email protected]

30-Aug 05:30 minbar-dir JobId 1359: console command: run BeforeJob 
".bvfs_update"
30-Aug 05:30 minbar-dir JobId 1359: Start Admin JobId 1359, 
Job=BVFS_Update.2024-08-30_05.30.00_11
30-Aug 05:30 minbar-dir JobId 1359: Bacula 15.0.2 (21Mar24): 30-Aug-2024 
05:30:29
   JobId:                  1359
   Job:                    BVFS_Update.2024-08-30_05.30.00_11
   Scheduled time:         30-Aug-2024 05:30:00
   Start time:             30-Aug-2024 05:30:29
   End time:               30-Aug-2024 05:30:29
   Termination:            Admin OK

30-Aug 05:30 minbar-dir JobId 1359: Begin pruning Jobs older than 12 
months .
30-Aug 05:30 minbar-dir JobId 1359: No Jobs found to prune.
30-Aug 05:30 minbar-dir JobId 1359: Begin pruning Files.
30-Aug 05:30 minbar-dir JobId 1359: No Files found to prune.
30-Aug 05:30 minbar-dir JobId 1359: End auto prune.


Did Bacula effectively "hallucinate" a nonexistent Job with id 0 to run 
the script "before"?  Or is there still a bug triggering when running 
bvfs_update as a RunScript?  This does not happen with my other 
similarly-structured admin jobs, such as the one that expires volumes 
past th.

I tried running a restore of my workstation this morning, and it still 
took more than four minutes to build the directory tree.


Does this seem as though the bvfs cache is being built correctly and 
used?  Is there a way I can test and verify that it is working correctly?


-- 
   Phil Stracchino
   Fenian House Publishing
   [email protected]
   [email protected]
   Landline: +1.603.293.8485
   Mobile:   +1.603.998.6958



_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users