On Friday 08 June 2007 03:10, Ryan Novosielski wrote:
<snip>
>
> I would disagree with that. As far as I know, Use Volume Once has been
> removed for some time.
No I could still set it to yes in this version.
> However, the replacement (Maximum Volume Jobs =
> 1) I use on my system to cause volumes to be marked used after one use.
>
> However, this does not affect recycling in my situation.
>
> I would suggest the original poster may have forgotten to update volumes
> (having created the volume before the current pool directives were in
> place).
>
> Chantal, I'd want to see at a minimum an llist on the volume in
> question, just to verify that at the very least the parameters have made
> it to the volume in the first place.
>
here it is:
MediaId: 31
VolumeName: DefaultVolume-0014
Slot: 0
PoolId: 1
MediaType: DDS
FirstWritten: 2007-06-08 07:26:01
LastWritten: 2007-06-08 07:26:01
LabelDate: 2007-06-08 07:26:01
VolJobs: 0
VolFiles: 0
VolBlocks: 0
VolMounts: 7
VolBytes: 1
VolErrors: 0
VolWrites: 156,381
VolCapacityBytes: 0
VolStatus: Append
Recycle: 1
VolRetention: 7,200
VolUseDuration: 0
MaxVolJobs: 1
MaxVolFiles: 0
MaxVolBytes: 0
InChanger: 1
EndFile: 4
EndBlock: 2,170
VolParts: 0
LabelType: 0
StorageId: 2
status is append at the moment because a backup is running
> In addition: keep in mind that the volume may very well not show
> recycled right after the retention time is up. There are some actions
> that will cause the volume recycling algorithm to be run through -- one
> would be attempting a backup against the volume, and I believe 'status
> dir' might be another. Not sure of specifics. Bacula does not, however,
> throw away the contents of the volume right away on its own -- it
> attempts to keep the data as long as possible.
Any idea how long this takes? Approximately?
I am testing Arno's suggestion now, to use "Maximum Volume
Jobs = 1". I'll let you know what happens.
This morning I noticed another problem, the backup was running for an hour and
then I got this message:
08-Jun 02:05 Server-sd: BackupAll.2007-06-08_01.00.00 Error: block.c:538 Write
error at 4:2171 on device "tape" (/dev/nst0). ERR=Input/output error.
08-Jun 02:06 Server-sd: BackupAll.2007-06-08_01.00.00 Error: Error writing
final EOF to tape. This Volume may not be readable.
dev.c:1542 ioctl MTWEOF error on "tape" (/dev/nst0). ERR=Input/output error.
08-Jun 02:06 Server-sd: End of medium on Volume "DefaultVolume-0014"
Bytes=4,139,734,897 Blocks=64,170 at 08-Jun-2007 02:06.
then bacula requested another tape, what does this mean? Something wrong with
the tape? it is impossible that the tape is full because it's 12G and I
backup 4G, and it was definitely not appending the data.
Chantal
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
