Hi all,
Is there a way to tell amanda to not re-use a tape more than X number of times?
I'd like to limit my tape re-use to something like 7 times or so before I
remove it from the configuration and replace it with a new one.
Thanks,
--
Seeya,
Paul
I'm in shape, my shape
The starttime option works for making sure a backup occurs AFTER a
certain time, but how can you make sure one occurs BEFORE a time?
Do you have to specify a later starttime for every disk except
the one you want to get backed up first?
For example, if amanda starts running at 10pm, and
Is there a way to tell amanda to not re-use a tape more than X number of times
?
Not yet. My planned output rewrite will maintain attributes for each
output media and this could go along with that.
Paul
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Looking at the amstatus code in 2.4.2 indicates the output you indicated
*is* displayed if you pass the --stats option.
Thanks. I used to have a mix of 2.4.1p1 and 2.4.2 and I don't think
this arg used to be needed.
However, I don't see any way to get that output using 2.4.1p1.
I don't
... My job last night was on tape 16, and according to the report,
expects tape 1 tonight. ...
Could you post the exact message? Also, the result of:
amadmin config tape
My amanda.conf says there are 25 tapes in cycle. ...
Do you mean you have "tapecycle 25"?
Did you change this before
... What does it
mean "Block size for 'b' option must be a positive integer multiple of
4" ...
That's a message from your restore program. Because Amanda is having it
read the image from a pipeline, some versions of restore get confused if
they get what's called a "short read". Amanda is
Load tape DEIMOS02 now
Continue? [Y/n]:
timeout waiting for amrestore
increase READ_TIMEOUT in recover-src/extract_list.c if your tape is slow
amrecover: error reading tape: Success
extract_list - child returned non-zero status: 1
Continue? [Y/n]:
On the /tmp/amanda/amidxtaped.debug I get:
...
Hello,
I want to check the level 1 sizes that AMANDA reports. For 3 filesystems
I continue to get the right size for level 0, but quite a large one for
level 1 (50-90% of level 0). I am quite sure that they did not change
the last days. I even forced a full dump without any effect to this
Hi all,
I have amanda configured on an Intel box (PIII) running RedHat 6.1, kernel 2.2.12-20.
I compiled version 2.4.2-19991216-beta1 and am not using RPMs. My tape drive is a VXA.
I do incrementals Monday through Thursday and a full backup every Friday. My
incrementals work fine, unelss
"John R. Jackson" wrote:
Load tape DEIMOS02 now
Continue? [Y/n]:
timeout waiting for amrestore
increase READ_TIMEOUT in recover-src/extract_list.c if your tape is slow
amrecover: error reading tape: Success
extract_list - child returned non-zero status: 1
Continue? [Y/n]:
On the
Frank Smith wrote:
The starttime option works for making sure a backup occurs AFTER a
certain time, but how can you make sure one occurs BEFORE a time?
I suppose AMANDA polls the current time and starts dumping as soon as
the "starttime" is in the past. In this case, if the polling interval
Denise Ives wrote:
Can anyone please explain to me what Amanda did here after the full dump
to tape daily118 on Tuesday 7 Nov 2000 ? To me it looks like Amanda did a
level 1 dump on Wednesday am to the holding disk, then another level 1
dump on Thursday am, then another level 1 on Friday
Hi all, could someone please explain what this error means?
[root@amanda amanda]# amrecover -d /dev/st0
AMRECOVER Version 2.4.2. Contacting server on amanda ...
220 amanda AMANDA index server (2.4.2) ready.
200 Access OK
Setting restore date to today
Hi all, could someone please explain what this error means?
...
amrecover: Unexpected server end of file
Any idea what "file" came to an unexpected end?
The network connection to amindexd on the server.
What's in /tmp/amanda/amindexd*debug on the server (at least the last
several
Title: RE: Where are instructions for setting up amandad on clients?
The instructions are there, but not in the way you were expecting.
It says somewhere near the beginning of the server install that the client install is similar.
Here's the quick run-down of what you need to do on the
Never mind, I was stupid, I forgot the config name :)
Which obviously should be better handled, i.e. an explicit message back
to amrecover. So it wasn't exactly all your falut :-).
I already have a note to myself to fix this.
Paul
John R. Jackson, Technical Software Specialist, [EMAIL
In a message dated: Fri, 10 Nov 2000 16:51:33 EST
"John R. Jackson" said:
Never mind, I was stupid, I forgot the config name :)
Which obviously should be better handled, i.e. an explicit message back
to amrecover. So it wasn't exactly all your falut :-).
I already have a note to myself to fix
AMANDA uses a block size of 32768 when writing to tape. Your tape device
should be prepared with this block size *before* you try to acces it for
restore (and each time after you load a new tape) with the command:
mt -f /dev/yourtapedevice setblk 32768
I prefer variable blocking, i.e. "setblk
... To me it looks like Amanda did a
level 1 dump on Wednesday am to the holding disk, then another level 1
dump on Thursday am, then another level 1 on Friday am.
Yes, exactly. Your AMANDA works fine, where is the problem?
The problem is that off line of discussions on this list, I
On Nov 10, 2000, Chris Karakas [EMAIL PROTECTED] wrote:
*if* the problem is really
the buffer size of the pipe that AMANDA uses (being too small)
That's a symptom, not the problem. The problem is (or appears to be,
from the given description) that Amanda doesn't handle the possibility
of the
On Nov 9, 2000, "Robert L. Harris" [EMAIL PROTECTED] wrote:
nose.incyte.agency.com:c1t6d0s6 0 6380292k dumping to tape
I put in a new tape, commented the rest of the disks out of my table
and started amdump. It's been sitting there for about an hour now.
It may take a while to
On Nov 10, 2000, "John R. Jackson" [EMAIL PROTECTED] wrote:
... To me it looks like Amanda did a
level 1 dump on Wednesday am to the holding disk, then another level 1
dump on Thursday am, then another level 1 on Friday am.
The problem is that off line of discussions on this list, I
22 matches
Mail list logo
