Hi,
for some reason old backups are still in the database, even if they are purged.
| 635 | Vol0635 | Purged | 1 | 928,733,695 |
0 | 7,776,000 | 0 | 0 | 0 | File | 2010-10-11 23:47:09
|
| 636 | Vol0636 | Purged | 1 | 562,976 |
0 | 7,776,000 | 0 | 0 | 0 | File | 2010-10-11 23:47:53
|
| 637 | Vol0637 | Purged | 1 | 1,240,464 |
0 | 7,776,000 | 0 | 0 | 0 | File | 2010-10-11 23:48:54
|
| 638 | Vol0638 | Purged | 1 | 106,572,432 |
0 | 7,776,000 | 0 | 0 | 0 | File | 2010-10-11 23:52:54
|
Pool configuration:
--
Pool {
Name = File
Pool Type = Backup
Recycle = no # Volumes nicht wieder verwenden.
AutoPrune = yes # Prune expired volumes
Action on Purge = Truncate # Loeschen
Volume Retention = 90 days #
File Retention = 90 days #
Job Retention = 90 days #
Maximum Volume Bytes = 20G # Limit Volume size to something
reasonable
Maximum Volumes = 900 # Limit number of Volumes in Pool
LabelFormat = "Vol"
}
I've tried to update the volumes, the pool and the statistics as suggested by
the documentation, but the volumes are still in the list.
What do I miss ?
Cheers,
Richard
------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
