Hi,
The storage daemon crashed last night and restarting it seemed to put
things back to normal (I'm still looking into the cause of the crash).
The first backup job that ran after the crash marked the tape in Error:
====
24-May 10:10 server.domain.com-sd JobId 195: Volume "CSE003L4"
previously written, moving to end of data.
24-May 10:11 server.domain.com-sd JobId 195: Error: Bacula cannot write
on tape Volume "CSE003L4" because:
The number of files mismatch! Volume=113 Catalog=112
24-May 10:11 server.domain.com-sd JobId 195: Marking Volume "CSE003L4"
in Error in Catalog.
====
So, now I have this tape that is in Error state and is 10% full. I was
able to successfully restore from it so the data is accessible and I'm
going to keep the tape.
I'm wondering:
- If a media is marked Error then will voluseduration and
volretention policy apply?
- Should I expect that this media at some point will be purged based
on the retention policy and reused just like any other media?
- Is there anything extra I need to do to deal with the Error state?
====
*llist media=CSE003L4
mediaid: 3
volumename: CSE003L4
slot: 4
poolid: 3
mediatype: LTO-4
firstwritten: 2010-04-24 23:04:59
lastwritten: 2010-05-21 23:07:13
labeldate: 2010-04-24 23:04:59
voljobs: 121
volfiles: 112
volblocks: 1,370,859
volmounts: 30
volbytes: 88,436,920,320
volerrors: 0
volwrites: 1,370,860
volcapacitybytes: 0
volstatus: Error
enabled: 1
recycle: 1
volretention: 5,184,000
voluseduration: 2,592,000
maxvoljobs: 0
maxvolfiles: 0
maxvolbytes: 0
inchanger: 1
endfile: 112
endblock: 2,041
volparts: 0
labeltype: 0
storageid: 2
deviceid: 0
locationid: 0
recyclecount: 0
initialwrite:
scratchpoolid: 0
recyclepoolid: 5
comment:
====
Any suggestions are welcome.
Thank you
Peter
------------------------------------------------------------------------------
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
