Re: [Bacula-users] Warning about setting File/Job Retentions in Pool resource!
UP Vlad23 wrote: Thank you for reply. What retentions are for my task? Can Bacula give me this not so difficult functionality? Situation is next: 1) Bacula can't set Job and Files Retentions for Job resource - only for Pool and Client resources. 2) I can't define Job and Files Retentions in Client Resource, because I have 1 Client, that backups on some Pools with different Volume Retention (It will purge all jobs for all pools - I describe this problem in main question) 3) We found out that I can't define Job and Files Retentions in Pool Resource, because it applied to jobs in other Pools too. Volume, Jobs, and Files retention must be defined only for one Pool and don't applied to other pools. Or Jobs and File Retention can be not defined anywhere, but then bacula do volume purging for pool, bacula must do job and file retention for this pool. I don't uderstand: If bacula did volume retention - what reason to keep records about jobs and files from this volume in catalog Stephen Thompson wrote: For more clarity: What actually happens is that when writing to the Pool where the File/Job Retentions are specified, the retentions will apply to any File/Job's that were ALSO written to another Pool, thus overriding the Client resource regardless of Pool. On 04/26/2010 11:52 AM, Stephen Thompson wrote: My, possibly mistaken, understanding of having File/Job Retention directives in a Pool resource was to be able to deviate from File/Job Retentions set by the Client resource AND to confine those retentions to the Pool where they are specified. What actually happens is that when using the Pool where the File/Job Retentions are specified, the retentions will apply to any File/Job's that were written to another Pool, overriding the Client resource. Real life example: The Job Retention for all my clients defaults to 1 year and I have monthly full Pools that I keep for a year. I also have an incremental/differential pool that I recycle on a 60-90 day basis. When I set the File/Job Retention to 90 days for my incremental/differential Pool and ran a complete set of incrementals, the 90 day retention was then applied to all of those jobs, not just for the incremental/differential Pool where the 90 day period was set, but for all of my monthly full Pools as well! This effectively purged 9 months of my Catalog records. :( Yes, I had a backup of the Catalog and yet it took 12 hours to restore. But, please note that it can be dangerous to use File/Job retentions in a Pool resource. thanks, Stephen -- Stephen Thompson Berkeley Seismological Laboratory step...@seismo.berkeley.edu215 McCone Hall # 4760 404.538.7077 (phone) University of California, Berkeley 510.643.5811 (fax) Berkeley, CA 94720-4760 -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users -- View this message in context: http://old.nabble.com/Job-Retention-for-concrete-Pool-purge-jobs-in-other-pools%21-tp28362535p28408955.html Sent from the Bacula - Users mailing list archive at Nabble.com. -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Warning about setting File/Job Retentions in Pool resource!
Thank you for reply. What retentions are for my task? Can Bacula give me this not so difficult functionality? Situation is next: 1) Bacula can't set Job and Files Retentions for Job resource - only for Pool and Client resources. 2) I can't define Job and Files Retentions in Client Resource, because I have 1 Client, that backups on some Pools with different Volume Retention (It will purge all jobs for all pools - I describe this problem in main question) 3) We found out that I can't define Job and Files Retentions in Pool Resource, because it applied to jobs in other Pools too. Volume, Jobs, and Files retention must be defined only for one Pool and don't applied to other pools. Or Jobs and File Retention can be not defined anywhere, but then bacula do volume purging for pool, bacula must do job and file retention for this pool. I don't uderstand: If bacula did volume retention - what reason to keep records about jobs and files from this volume in catalog Stephen Thompson wrote: For more clarity: What actually happens is that when writing to the Pool where the File/Job Retentions are specified, the retentions will apply to any File/Job's that were ALSO written to another Pool, thus overriding the Client resource regardless of Pool. On 04/26/2010 11:52 AM, Stephen Thompson wrote: My, possibly mistaken, understanding of having File/Job Retention directives in a Pool resource was to be able to deviate from File/Job Retentions set by the Client resource AND to confine those retentions to the Pool where they are specified. What actually happens is that when using the Pool where the File/Job Retentions are specified, the retentions will apply to any File/Job's that were written to another Pool, overriding the Client resource. Real life example: The Job Retention for all my clients defaults to 1 year and I have monthly full Pools that I keep for a year. I also have an incremental/differential pool that I recycle on a 60-90 day basis. When I set the File/Job Retention to 90 days for my incremental/differential Pool and ran a complete set of incrementals, the 90 day retention was then applied to all of those jobs, not just for the incremental/differential Pool where the 90 day period was set, but for all of my monthly full Pools as well! This effectively purged 9 months of my Catalog records. :( Yes, I had a backup of the Catalog and yet it took 12 hours to restore. But, please note that it can be dangerous to use File/Job retentions in a Pool resource. thanks, Stephen -- Stephen Thompson Berkeley Seismological Laboratory step...@seismo.berkeley.edu215 McCone Hall # 4760 404.538.7077 (phone) University of California, Berkeley 510.643.5811 (fax) Berkeley, CA 94720-4760 -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users -- View this message in context: http://old.nabble.com/Job-Retention-for-concrete-Pool-purge-jobs-in-other-pools%21-tp28362535p28374125.html Sent from the Bacula - Users mailing list archive at Nabble.com. -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Warning about setting File/Job Retentions in Pool resource!
My, possibly mistaken, understanding of having File/Job Retention directives in a Pool resource was to be able to deviate from File/Job Retentions set by the Client resource AND to confine those retentions to the Pool where they are specified. What actually happens is that when using the Pool where the File/Job Retentions are specified, the retentions will apply to any File/Job's that were written to another Pool, overriding the Client resource. Real life example: The Job Retention for all my clients defaults to 1 year and I have monthly full Pools that I keep for a year. I also have an incremental/differential pool that I recycle on a 60-90 day basis. When I set the File/Job Retention to 90 days for my incremental/differential Pool and ran a complete set of incrementals, the 90 day retention was then applied to all of those jobs, not just for the incremental/differential Pool where the 90 day period was set, but for all of my monthly full Pools as well! This effectively purged 9 months of my Catalog records. :( Yes, I had a backup of the Catalog and yet it took 12 hours to restore. But, please note that it can be dangerous to use File/Job retentions in a Pool resource. thanks, Stephen -- Stephen Thompson Berkeley Seismological Laboratory step...@seismo.berkeley.edu215 McCone Hall # 4760 404.538.7077 (phone) University of California, Berkeley 510.643.5811 (fax) Berkeley, CA 94720-4760 -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Warning about setting File/Job Retentions in Pool resource!
For more clarity: What actually happens is that when writing to the Pool where the File/Job Retentions are specified, the retentions will apply to any File/Job's that were ALSO written to another Pool, thus overriding the Client resource regardless of Pool. On 04/26/2010 11:52 AM, Stephen Thompson wrote: My, possibly mistaken, understanding of having File/Job Retention directives in a Pool resource was to be able to deviate from File/Job Retentions set by the Client resource AND to confine those retentions to the Pool where they are specified. What actually happens is that when using the Pool where the File/Job Retentions are specified, the retentions will apply to any File/Job's that were written to another Pool, overriding the Client resource. Real life example: The Job Retention for all my clients defaults to 1 year and I have monthly full Pools that I keep for a year. I also have an incremental/differential pool that I recycle on a 60-90 day basis. When I set the File/Job Retention to 90 days for my incremental/differential Pool and ran a complete set of incrementals, the 90 day retention was then applied to all of those jobs, not just for the incremental/differential Pool where the 90 day period was set, but for all of my monthly full Pools as well! This effectively purged 9 months of my Catalog records. :( Yes, I had a backup of the Catalog and yet it took 12 hours to restore. But, please note that it can be dangerous to use File/Job retentions in a Pool resource. thanks, Stephen -- Stephen Thompson Berkeley Seismological Laboratory step...@seismo.berkeley.edu215 McCone Hall # 4760 404.538.7077 (phone) University of California, Berkeley 510.643.5811 (fax) Berkeley, CA 94720-4760 -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
