Hi Arno,
now i have very actual real data and i do not understand whats going wrong.
i just checked the backup and the following messages :
14-Apr 01:18 fileserver-dir: Pruned 6 Jobs on Volume
"Freitag_103_ab_30.1.06" from catalog.
14-Apr 01:18 fileserver-sd: ntserver.2007-04-14_01.05.00 Warning:
Director wanted Volume "Donnerstag_303_ab_30.1.06" for device "SDLT"
(/dev/nst0).
Current Volume "Freitag_103_ab_30.1.06" not acceptable because:
1998 Volume "Freitag_103_ab_30.1.06" status is Used, but should be
Append, Purged or Recycle (cannot automatically recycle current volume,
as it still contains unpruned data or the Volume Retention time has not
expired.).
14-Apr 01:18 fileserver-sd: Please mount Volume
"Donnerstag_303_ab_30.1.06" on Storage Device "SDLT" (/dev/nst0) for Job
ntserver.2007-04-14_01.05.00
14-Apr 02:18 fileserver-sd: Please mount Volume
"Donnerstag_303_ab_30.1.06" on Storage Device "SDLT" (/dev/nst0) for Job
ntserver.2007-04-14_01.05.00
14-Apr 04:18 fileserver-sd: Please mount Volume
"Donnerstag_303_ab_30.1.06" on Storage Device "SDLT" (/dev/nst0) for Job
ntserver.2007-04-14_01.05.00
ok bacula can not prune the volume but why ? ....
complete last week it works fine, but now bacula can't purge again.
i have the llist command output for the Freitag Volume:
MediaId: 20
VolumeName: Freitag_103_ab_30.1.06
Slot: 0
PoolId: 1
MediaType: SDLT
FirstWritten: 2007-03-23 09:44:52
LastWritten: 2007-03-24 04:04:30
LabelDate: 2007-03-23 09:44:52
VolJobs: 6
VolFiles: 145
VolBlocks: 2,206,529
VolMounts: 82
VolBytes: 142,347,429,166
VolErrors: 0
VolWrites: 28,399,307
VolCapacityBytes: 0
VolStatus: Used
Recycle: 1
VolRetention: 432,000
VolUseDuration: 82,800
MaxVolJobs: 0
MaxVolFiles: 0
MaxVolBytes: 0
InChanger: 1
EndFile: 144
EndBlock: 14,861
VolParts: 0
LabelType: 0
StorageId: 2
And the List Volumes output:
| 20 | Freitag_103_ab_30.1.06 | Used | 142,347,429,166 |
145 | 432,000 | 1 | 0 | 1 | SDLT |
2007-03-24 04:04:30 |
There are now messages between ... then i enter the command "mount" and
the following output :
14-Apr 07:52 fileserver.issler.de-dir: Recycled current volume
"Freitag_103_ab_30.1.06"
14-Apr 07:52 fileserver.issler.de-sd: Recycled volume
"Freitag_103_ab_30.1.06" on device "SDLT" (/dev/nst0), all previous data
lost.
why now????? i can not understand this.
so after i mount the volume manually, he recycled the volume and the
jobs start to run. but why not automatic???
any hints?
thanks
manuel
Arno Lehmann schrieb:
> Hello,
>
> On 4/3/2007 3:14 PM, Manuel Stächele wrote:
>> hi,
>>
>> something goes wrong so i give you first the pool definitions, that you
>> can look in my confs. to understand what im talking about.
>>
>> Pool {
>> Name = Woche
>> Pool Type = Backup
>> Recycle = yes
>> AutoPrune = yes
>> Volume Retention = 5 days
>> Volume Use Duration = 23 hours
>> Accept Any Volume = yes
>> Recycle Current Volume = yes
>> }
>>
>> we have a daily cycle which backup every job full every day ;-)
>> we have the following volumes:
>>
>> mon1, tue1, wed1, thu1, fri1
>> mon2, tue2, wed2, thu2, fri2
>> mon3, tue3, wed3, thu3, fri3
>>
>> it works fine: after volume use duration the volume status changed to
>> "used" no problem!
>>
>> so the problem if bacula want to reuse a volume it looks an tries to
>> prune the volume in the drive. but in the last days it says ever:
>>
>> could not prune all data, cound not recycle because still jobs on the
>> volume.
>>
>> - it worked for about 3-4 weeks perfekt now its broken, an i do not know
>> why.
>> - if i say "mount" in bconsole after bacula send me the error "cound not
>> prune..." than it work often, it prune outstanding jobs and recycle the
>> volume.
>>
>> can you say me whats wrong?
>
> The jobs might 'overtake' your retention periods.
>
> Use the llist command to find out when the volume requested was last
> written to, add the retention time, and then you see when the tape can
> be recycled.
>
> I guess that the job requiring this tape is scheduled to a time before that.
>
> This can happen when your jobs wait a liitle for the tape each day, and
> this time will add up because the retention time only starts after the -
> now postponed - jobs finish.
>
> After some time, the retention delay might become greater than the spare
> time you have set up.
>
> In the end, Bacula can't prune jobs because they are still in the
> retention period when the jobs start.
>
>
>> i know my engish is pretty poor i am sorry and pleas ask me if you dont
>> understand my problem.
>
> Oh, I hope I understood your problem right. A more detailed explanation
> might be possible with some real data. Post the actual messages you get,
> along with the llist output for the volume requested, and also add the
> query results for this tapes jobs to it. I suppose you'll see the reason
> yourself :-)
>
>> greetings manuel
>
> Arno
>
>>
>
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bacula-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/bacula-users
