Re: [Bacula-users] VirtualFull and correct volume management...

2024-06-05 Thread Marco Gaiarin
Mandi! Bill Arlofski via Bacula-users In chel di` si favelave... > First, you are passing them incorrectly. Just quote the whole line like: Bingo! For google searches, because level have spaces, the correct row is: Run After Job = "/etc/bacula/scripts/deleteFailedJobs %c \"%l\"" > S

Re: [Bacula-users] VirtualFull and correct volume management...

2024-05-31 Thread Bill Arlofski via Bacula-users
On 5/31/24 8:56 AM, Marco Gaiarin wrote: If you *really* want to automatically delete failed jobs (I personally don't think this is a good idea), you can use a RunScript in an Admin type Job like: Why in and 'Admin' job? I've tried to add something like: Run After Job = /etc/bacula/

Re: [Bacula-users] VirtualFull and correct volume management...

2024-05-31 Thread Marco Gaiarin
Mandi! Martin Simmons In chel di` si favelave... > Yes, that is how volumes work. Bacula can only append at the end of a volume, > so the volume size would increase forever if it could switch back to Append > after purging some jobs. To reuse a volume, it needs to be recycled, which > only hap

Re: [Bacula-users] VirtualFull and correct volume management...

2024-05-31 Thread Marco Gaiarin
Mandi! Bill Arlofski via Bacula-users In chel di` si favelave... > Why not set in your Pool(s) `MaximumVolumeJobs = 1` Ah! Brilliant! Never minded abou that!!! > If you prefer to have volumes stay in a pool they were initially created in > forever, ignore that previous paragraph. :) I've no

Re: [Bacula-users] VirtualFull and correct volume management...

2024-05-29 Thread Bill Arlofski via Bacula-users
On 5/24/24 2:39 AM, Marco Gaiarin wrote: I suspect that 'job counter' get resetted if and only if all jobs in a volume get purged; this lead me to think that my configuration simpy does not work in a real situation, because sooner or later jobs get 'scattered' between volumes and virtual job of

Re: [Bacula-users] VirtualFull and correct volume management...

2024-05-29 Thread Martin Simmons
> On Fri, 24 May 2024 10:39:06 +0200, Marco Gaiarin said: > > > I suspect that 'job counter' get resetted if and only if all jobs in a > > volume get purged; this lead me to think that my configuration simpy does > > not work in a real situation, because sooner or later jobs get 'scattered' >

Re: [Bacula-users] VirtualFull and correct volume management...

2024-05-28 Thread Marco Gaiarin
> I suspect that 'job counter' get resetted if and only if all jobs in a > volume get purged; this lead me to think that my configuration simpy does > not work in a real situation, because sooner or later jobs get 'scattered' > between volumes and virtual job of consolidation stop to work, so job

Re: [Bacula-users] VirtualFull and correct volume management...

2024-05-15 Thread Marco Gaiarin
Mandi! Josh Fisher via Bacula-users In chel di` si favelave... > I use the following in my query.sql file: OK, thanks! Now i can verify that: *list media pool=FVG-PP-HFA3-1FilePool +-++---+-+-+--+--+-+--+-

Re: [Bacula-users] VirtualFull and correct volume management...

2024-05-10 Thread Josh Fisher via Bacula-users
On 5/9/24 10:02, Marco Gaiarin wrote: I've setup some backup jobs for some (mostly windows) client computer; i mean 'client' as 'not always on'. ... 2) There's some way i can get the 'jobs in volume X'? I can query jobs for volume, but i've not found a way to query volumes for jobs I use

[Bacula-users] VirtualFull and correct volume management...

2024-05-09 Thread Marco Gaiarin
I've setup some backup jobs for some (mostly windows) client computer; i mean 'client' as 'not always on'. I've setup a job like this: Job { Name = FVG-SV-EEG JobDefs = DefaultJob Storage = SVPVE3FileMulti Pool = FVG-SV-EEGFilePool Messages = Standard