Re: [Bacula-users] Wildfile

[Stefan G. Weichinger]

Am 11.04.24 um 07:49 schrieb Bill Arlofski via Bacula-users:

On 4/10/24 11:38 PM, Stefan G. Weichinger wrote:


First coffee here right now ;-)
Thanks for your example.


Hello Stefan,

You are welcome!

Well, it is 23:41 here now, so I have switched from coffee to beer. :)


Understandable ;-)



I didn't add "signature" but already came up with this yesterday:

Fileset {
    Name = "VM_XYZ"
    Include {
  File = "/mnt/backup/vmbackup/Backup XYZ"
  Options {
    WildFile = "*.vbk"
  }
  Options {
    Exclude = "Yes"
    RegexFile = ".*"
  }
    }
}

seems to work!


OH! Look at you, jumping from WildFile to RegexFile!  :)

I was trying to keep things simple, but OK. :)

Yes, this is fine. Remember my first post about there always being 
several ways to do something in Bacula? :)


Sure. So far it seems to work. At least I see other things to learn now 
... as I get used to Bacula.



Do I have to add that signature-line?


To confirm why I made that comment, try running a restore of one of 
these jobs that you have now backed up. ;)

>> What do you see?

Will do tmrw

Sounds as if I should add these lines asap.


Glad y
ou got this working!

And, if you like we can talk about Client side scripts to point your 
`File = ` at too. Just for more fun and practice, of course. BUT... 
client side scripts are a bit less scalable as you might imagine. :)


Right now I don't know if I might need them. But I always like to learn.




___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] MD5 Fatal Error

[Martin Simmons]

Please Cc replies to the list so other people can see them.

Did that job read from Vol0159 as well as writing to it?  If yes, then
messages like this help to show why:

pbckall004-dir JobId 5387: There are no more Jobs associated with Volume 
"Vol0159". Marking it purged.

To prevent that, I think you need to increase the Job Retention in the pool or
client resource so it keeps the job records for longer.

BTW, the job log lines below are in reverse order (latest is first) so that
make it confusing!

__Martin


> On Mon, 15 Apr 2024 09:56:53 +0200, Mohamed AIT EL HADJ said:
> 
> Yes, i think its the same problem but i dont know how to fix it. Do you 
> have any ideas ?
> 
> Le 12/04/2024 à 17:48, Martin Simmons a écrit :
> > Maybe the same problem as reported in
> > https://sourceforge.net/p/bacula/mailman/bacula-users/thread/c3bc9fed-3c84-46d3-2f40-9dd78590a773%40baculasystems.com/#msg37296305
> > ?
> >
> > I assume the "cycle in their volume list" comment there means it is writing 
> > to
> > a volume that it previous read.
> >
> > __Martin
> >
> >
> >> On Mon, 8 Apr 2024 11:27:20 +0200, Mohamed AIT EL HADJ via 
> >> Bacula-users said:
> >> Hello,
> >> My backups were working fine but yesterday I had a problem with one of
> >> my jobs which apparently has a problem with MD5.
> >>
> >> Here are the job logs:
> >>
> >> pbckall004-dir JobId 5387: Error: Unable to flush file records!
> >> pbckall004-dir JobId 5387: Fatal error: Error detected between 
> >> digest[466172]="zxdWYCUt+beniiSsYO+d6w" and 
> >> name[466171]="/var/opt/gitlab/gitlab-rails/shared/artifacts/12/53/1253e9373e781b7500266caa55150e08e210bc8cd8cc70d89985e3600155e860/2024_04_01/"
> >> pbckall004-dir JobId 5387: Fatal error: MD5 digest not same 
> >> FileIndex=466172 as attributes FI=466171
> >> pbckall004-sd JobId 5387: Sending spooled attrs to the Director. 
> >> Despooling 237,369,878 bytes ...
> >> pbckall004-sd JobId 5387: Elapsed time=02:20:45, Transfer rate=7.303 M 
> >> Bytes/second
> >> pbckall004-sd JobId 5387: End of Volume "Vol0197" at addr=898996114 on 
> >> device "DEV-dedup-DRV19" (/zfs/bacula).
> >> pbckall004-sd JobId 5387: Forward spacing Volume "Vol0197" to 
> >> addr=893762478
> >> pbckall004-sd JobId 5387: Ready to read from volume "Vol0197" on Aligned 
> >> device "DEV-dedup-DRV19" (/zfs/bacula).
> >> pbckall004-sd JobId 5387: End of Volume "Vol0165" at addr=515616168 on 
> >> device "DEV-dedup-DRV19" (/zfs/bacula).
> >> pbckall004-sd JobId 5387: New volume "Vol0159" mounted on device 
> >> "DEV-dedup-DRV1" (/zfs/bacula) at 07-avril-2024 18:22.
> >> pbckall004-sd JobId 5387: Recycled volume "Vol0159" on Aligned device 
> >> "DEV-dedup-DRV1" (/zfs/bacula), all previous data lost.
> >> pbckall004-dir JobId 5387: Using Volume "Vol0159" from 'Scratch' pool.
> >> pbckall004-dir JobId 5387: Recycled volume "Vol0159"
> >> pbckall004-dir JobId 5387: All records pruned from Volume "Vol0131"; 
> >> marking it "Purged"
> >> pbckall004-dir JobId 5387: New Pool is: Scratch
> >> pbckall004-dir JobId 5387: There are no more Jobs associated with Volume 
> >> "Vol0131". Marking it purged.
> >> pbckall004-dir JobId 5387: All records pruned from Volume "Vol0124"; 
> >> marking it "Purged"
> >> pbckall004-dir JobId 5387: New Pool is: Scratch
> >> pbckall004-dir JobId 5387: There are no more Jobs associated with Volume 
> >> "Vol0124". Marking it purged.
> >> pbckall004-dir JobId 5387: All records pruned from Volume "Vol0184"; 
> >> marking it "Purged"
> >> pbckall004-dir JobId 5387: New Pool is: Scratch
> >> pbckall004-dir JobId 5387: There are no more Jobs associated with Volume 
> >> "Vol0184". Marking it purged.
> >> pbckall004-dir JobId 5387: All records pruned from Volume "Vol0186"; 
> >> marking it "Purged"
> >> pbckall004-dir JobId 5387: New Pool is: Scratch
> >> pbckall004-dir JobId 5387: There are no more Jobs associated with Volume 
> >> "Vol0186". Marking it purged.
> >> pbckall004-dir JobId 5387: All records pruned from Volume "Vol0159"; 
> >> marking it "Purged"
> >> pbckall004-dir JobId 5387: New Pool is: Scratch
> >> pbckall004-dir JobId 5387: There are no more Jobs associated with Volume 
> >> "Vol0159". Marking it purged.
> >> pbckall004-sd JobId 5387: End of medium on Volume "Vol0179" 
> >> Bytes=53,686,844,017 Blocks=409,600 at 07-avril-2024 18:22.
> >> pbckall004-sd JobId 5387: User defined maximum volume size 53,687,091,200 
> >> will be exceeded on device "DEV-dedup-DRV1" (/zfs/bacula).    Marking 
> >> Volume "Vol0179" as Full.
> >>
> >> I have no idea how this could have happened or how to resolve the error.
> >>
> >> Any helps will be great.
> >>
> >> Regards,
> >>
> >>
> >>
> >> ___
> >> 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