|
|
| Reporter | tmorris | Assigned To | bruno-at-bareos | |
|---|
| Priority | normal | Severity | major | Reproducibility | always |
|---|
| Status | closed | Resolution | won't fix | |
|---|
| Platform | Linux | OS | Ubuntu | OS Version | 20.04 |
|---|
| Product Version | 23.0.1 | |
|---|
|
|
| Summary | 0001611: Increasing retention period for pool does not increase retention period for previously created volumes when recycled |
|---|
| Description | When changing the "Volume Retention" setting on a pool, this does not update volumes in the pool when they are recycled. My expectation is that after recycling a volume will have the new value for retention period. |
|---|
| Steps To Reproduce | Create a pool with a very short retention period. Example:
Pool {
Name = IncrPool0
Pool Type = Backup
Storage = BackupStore
Recycle = yes
Recycle Oldest Volume = yes
Auto Prune = yes
Action On Purge = Truncate
Maximum Volume Jobs = 1
Maximum Volumes = 1000
Volume Retention = 32
Label Format = "Incr-"
}
Run a number of jobs utilizing this pool, then modify the pool such that Volume Retention = 32 days
Run more jobs utilizing the same pool and see that the earlier volumes are recycled for new jobs, but the retention period on those volumes remains 32 seconds afer recycling. I have been able to see the continuing messages in bconsole that still show a retention period of 32 seconds even after the setting was changed and configs reloaded, and the volumes were recycled multiple times afterward. |
|---|
| Additional Information | If this is an expected behavior, I believe it is undocumented, and there is likewise no documentation that I have found for how to fix the situation. The docs recommend not using the "delete" command, only mentioning that it necessitates the use of bscan, which itself notes that if it is being used something has gone wrong.
Changing the retention period of volumes in a pool upon rewrite seems like necessary functionality to me as a user -- same goes for sane changing of almost any configuration value, without having to start over. This issue is also confusing to debug, as the jobs get pruned and thus disappear from the records visible in the UI. I was only able to tell what was going on by reviewing messages in bconsole.
Obviously my steps to reproduce don't include my exhaustive configuration -- I haven't set up a fully isolated installation and done a truly minimal reproduction, but let me know if I can provide any other config or system particulars, or if there are other questions I can answer. Also, I selected "Major" for severity, as this severely impedes my ability to evolve my backup system in production, and "normal" for priority as I really don't know how this relates to other issues. Thank you |
|---|
| Tags | No tags attached. |
|---|
|
|
