Thanks for that... I've enabled the Run before script and as said earlier changed the retention period to 5 days. Things look fine for now and I shall keep the forum posted on this.
Kumaran
On 10/25/05, Arno Lehmann <[EMAIL PROTECTED]> wrote:
Hello,
On 25.10.2005 10:00, Kumaran Babu wrote:
> I'm experiencing the same problem with
> 1. The backup will sit and wait for a MOUNT command to start a backup.
> 2. Sta 2/3/4 will not bring up what it does when you type STA and then
> 1/2/3/4
You could look up the status command syntax in the manual and you would
find that a "status all" or "status dir" works...
> I do not run a RUN before script. I have a daily full backup as in this
> case and a seperate Pool with 1 volume in each pool per day rotated
> every week...
>
> The rentention period was 6 days which Ive now changed to 5 hoping to
> solve the problem. Do not know what causes the problem.
You need to trigger tape recycling before you start a job.
I'm not sure about this, but it *might* be that there is an issue with
the current recycling code (I couldn't verify because I usually have
enough free tapes available...). The problem might be that job pruning
is not automatically followed with volume pruning. It seems that Bacula
looks for a new volume, in the search triggers pruning, but it only
prunes jobs from volumes. Only with the next search run, the volumes are
recognized as having no more jobs and are recycled. I think the sequence
of operatins is as follows:
Search volume
- prune volumes
- prune jobs
but, in case no available volumes are found, another prune volumes
should follow.
I might be wrong, of course - I didn't even produce debug output during
a pruning run.
Arno
> Any help would be great.
>
> Kumaran
--
IT-Service Lehmann [EMAIL PROTECTED]
Arno Lehmann http://www.its-lehmann.de
