Hello, I have three pools defined for a host with differing retention times:
Pool { Name = myhost.example.com-full Pool Type = Backup Maximum Volume Jobs = 1 Recycle = yes AutoPrune = yes Volume Retention = 6 months LabelFormat = "myhost.example.com-full-" } Pool { Name = myhost.example.com-diff Pool Type = Backup Maximum Volume Jobs = 1 Recycle = yes AutoPrune = yes Volume Retention = 4 weeks LabelFormat = "myhost.example.com-diff-" } Pool { Name = myhost.example.com-inc Pool Type = Backup Maximum Volume Jobs = 1 Recycle = yes AutoPrune = yes Volume Retention = 8 days LabelFormat = "myhost.example.com-inc-" } declared in the Schedule so: Schedule { Name = "myhost.example.com-monthly" Run = Level=Full Pool=myhost.example.com-full 1st sun at 23:05 Run = Level=Differential Pool=myhost.example.com-diff 2nd-5th sun at 23:05 Run = Level=Incremental Pool=myhost.example.com-inc mon-sat at 23:05 } This works fine unless a job get upgraded from incremental or diff to full. When a job gets upgraded, Bacula uses the pool the job was upgraded from instead of the pool the job was upgraded to. That is, when a job gets upgraded from inc to full, the inc pool is used. This causes the full jobs to be purged at the inc retention interval, which uses quite a bit more network traffic and disk space than I had planned for. How can I make Bacula use the full pool when a job gets upgraded? Thanks, Michael Anderson ------------------------------------------------------------------------------ The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials, tech docs, whitepapers, evaluation guides, and opinion stories. Check out the most recent posts - join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users