On Fri, 30 Mar 2007 11:34:33 +0300, Mantas M said:
Hi Ryan,
What i am trying to do is to force bacula not to reuse any previously
written volume EVER.
Have you tried setting the VolStatus to Archive on those volumes?
__Martin
It's really weird that bacula thinks this volume has no
No i haven't, but I'll try that.
Also, i guess I've worked out why volume size was incorrect. Apparently,
when migrating from older configs (pools were designed in different
way), i accidentally left Purge Oldest Volume = yes in pool
configuration. That is why the volumes were recycled...
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have deleted the original e-mail that contained the problem. ;) Please
leave the whole e-mail text intact as it helps people who want to join
in mid-way, even if they have deleted earlier mail.
Keep in mind that the Recycle flag here is different
Hello people,
I have a problem with bacula 1.38.11 ignoring retention periods and
reusing the same volumes over and over again. I've checked the database,
volume retention periods have the correct values (the same as configs).
Configuration follows:
Pools:
Maximum volumes = 0 #unlimited
Update:
i've found that VolStatus field in Media table has it's value set to
'Recycle'. That's why bacula is reusing the volumes.
However, the question remains: why the hell this field is set to Recycle
when recycle is disabled ?
Mantas M. wrote:
Hello people,
I have a problem with bacula
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Remember to always update your volumes from the pool. The volumes get
their settings when they are created, not when you change the config
file. See the manual for more information.
Mantas M. wrote:
Update:
i've found that VolStatus field in
