It looks like when a particular job is run and there were no changes
recorded, it purges the Volume. Is this the desired behavior? Should it
mark a Volume as such just because there were no recorded changes? I'd
think you'd just keep the Volume and just keep it marked as Used. A SELECT
* FROM File WHERE JobId = '54' returns no results, that was the last job run
before the entries pasted below showed up, this is expected though as this
was an incremental and no files were changed.
Here's the relevant log entries, this is when the next job is run it checks
for old Volumes to purge:
05-May 16:05 company-services-01-dir JobId 55: There are no more Jobs
associated with Volume
"company-services-01-fd-company-services-01.2011-05-05_16.05.02_08-Incremental".
Marking it purged.
05-May 16:05 company-services-01-dir JobId 55: All records pruned from
Volume
"company-services-01-fd-company-services-01.2011-05-05_16.05.02_08-Incremental";
marking it "Purged"
Here's my Pool setup:
Pool {
Name = File
Action On Purge = Truncate
Pool Type = Backup
Maximum Volume Jobs = 1
Maximum Volume Bytes = 5G
AutoPrune = yes
Recycle = no
Label Format = "${Client}-${JobName}-${Level}"
UseVolumeOnce = yes
Volume Retention = 30 days
}
------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network
management toolset available today. Delivers lowest initial
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
