Arno,
Thanks again. Excellent explanation, especially getting through my
thick skull! (lol) Although I am making progress, I am still having
some issues. Last night, my incremental worked except those that were
blocked by the catalog backup that did not work. After I cancelled
the
Hello,
On 1/4/2006 4:57 PM, John Hayden wrote:
Arno,
Thanks again. Excellent explanation, especially getting through my
thick skull! (lol)
I see you're working in a medical institution - have you started your
career in radiology and still carry around the lead protection?
;-P
Hi.
Image you have a tape with 3 jobs on it.
Now you purge all _jobs_ via bconsole (or job retention time).
After that Bacula considers the tape as useless cause it has no clue
whats stored on it. All job information (files backuped on the tape) were
purged, so it frees the tape.
Greetings,
Michael,
These are brand new tapes that I just labeled and add to the pool.
Then a few seconds/minutes later, they are marked as purged and I
have no tapes again
John Hayden
On Jan 3, 2006, at 3:41 PM, Michael Scherer wrote:
Hi.
Image you have a tape with 3 jobs on it.
Now
Hi John.
a) the tapes aren't deleted, just marked as purged so they can
be used for an upcoming job, you can check that with
list media pool=PoolName in bconsole
b) might be the default behaviour atm, cause well, a new tape has no
jobs attached to it and therefor gets marked as purged
Hello,
On 1/3/2006 9:44 PM, John Hayden wrote:
Michael,
... no, but still...
These are brand new tapes that I just labeled and add to the pool.
Then a few seconds/minutes later, they are marked as purged and I have
no tapes again
No, it's not that you have no available tapes.
John Hayden wrote:
Hope everyone had a god New Years!
In my continuing saga of a retrograde, any volume I label and add
to a pool almost immediately gets marked as purged with the following
message:
03-Jan 15:46 rosalind-dir: There are no Jobs associated with Volume
Mutation0020.
Arno,
If that is expected behavior, then I think that when I run the
status command in bconsole and ask for the status of the director, I
should not get the following:
*status
Using default Catalog name=MyCatalog DB=bacula
Status available for:
1: Director
2: Storage
3:
Hi,
On 1/3/2006 11:15 PM, John Hayden wrote:
Arno,
If that is expected behavior,
Expected behaviour... well, it's what I got used to. Usually, I'd expect
a new volume to start with status unused or purged, but append is kind
of... funny.
then I think that when I run the
status
