-Original Message-
From: Gene Heskett [mailto:[EMAIL PROTECTED]]
Sent: Freitag, 17. Jänner 2003 01:06
To: Michael Lang; [EMAIL PROTECTED]
Subject: Re: Strange Amandad problem using xinetd and RedHat 8.0
On Thursday 16 January 2003 13:17, Michael Lang wrote:
using the default
Hi again.
Quick summary of the thread:
Replaced the tape drive in backup server. After that, got problems with
amrestore:
The backup ran for the first time tonight. The output that amdump sent
me after the backup looked entirely normal, and also I could restore
some files from the tape with
Dear All,
I'd like to ask if anyone managed to configure amanda to work with TL890
(specifically TL892) tape library on RedHat Linux 8.0. I have tried to
use both chg-scsi and chg-multi, but failed with both.
chg-scsi did better though. I could load a tape from any slot to a tape
drive, label
Hi,
I'm setting up amanda on a Compaq Proliant DL380 with three Compaq
DLT8000 tape drives.
Having run tapetype a few times (using DLT IV tapes), I'm getting the
following:
define tapetype unknown-tapetype {
comment just produced by tapetype program
length 38301 mbytes
filemark 23
Leonid,
I've attached the configs I used on Compaq ML370, TL891, DLT8000.
You need mtx installed too.
As an aside: If anyone thinks there's glaring mistakes in my setup...
Its been working well enough for me stop paying for Arkeia though :)
Owen.
On Fri, 17 Jan 2003, Leonid Mamtchenkov
On Fri, 17 Jan 2003 at 10:38am, Hery Zo RAKOTONDRAMANANA wrote
Somehow, I now have this in my kernel messages (which didn't happen
when I only had one SCSI controller):
Jan 16 16:17:09 parasy kernel: st0: Error with sense data: Info fld=0x2, Current
st09:00: sense key Medium Error
Jan 16
Somehow, I now have this in my kernel messages (which didn't happen
when I only had one SCSI controller):
Jan 16 16:17:09 parasy kernel: st0: Error with sense data: Info fld=0x2,
Current st09:00: sense key Medium Error
Jan 16 16:17:09 parasy kernel: Additional sense indicates Write
Hi,
I found a problem with compiling the changer-src:
I run configure with the following parameters:
./configure --prefix=/opt/local/amanda --program-suffix=2.4.3 --with-user=amanda
--with-group=sys --with-config=daily --with-tape-device=/dev/rmt/0n
chg-scsi-chio.c: In function
Owen Williams [EMAIL PROTECTED] wrote:
OW I've attached the configs I used on Compaq ML370, TL891, DLT8000.
Thanks a lot! Those are helpful in proving myself being on the right
track. :)
OW You need mtx installed too.
Stupid me ;) Thanks.
OW As an aside: If anyone thinks there's glaring
On Fri, Jan 17, 2003 at 10:38:43AM +0300, Hery Zo RAKOTONDRAMANANA wrote:
Hi all,
by the way, wish all of you all the best things for this new year.
My problem is that I frequently have these messages:
*** A TAPE ERROR OCCURRED: [reading label: Input/output error].
Thinking this could
Hello Amanda users.
I'm seeing something rather odd in last night's dump attempt,
the amcheck and the attempted (but failed) flush.
I'll include extracts of all three messages - but the short
of it is that some amanda programs see and accept the current
tape in the drive and others don't.
FWIW
Hi,
AFAIK you'll have to rewind the tape explicitly between amdump and
amverify, as neither
amdump nor amverify do that for you.
Christoph
Toomas Aas schrieb:
Hi again.
Quick summary of the thread:
Replaced the tape drive in backup server. After that, got problems with
amrestore:
The
Hi!
Christoph Scheeder wrote:
AFAIK you'll have to rewind the tape explicitly between amdump and
amverify, as neither
amdump nor amverify do that for you.
Christoph
I tried running mt rewind and then amverify from command line.
Still the same errors...
--
Toomas Aas | [EMAIL PROTECTED] |
I can't seem to find thisn in configure --help on .4.3B4, am I missing it?
--
They that would give up essential liberty for temporary safety deserve
neither liberty nor safety.
-- Benjamin Franklin
I'm in the process of upgrading my Amanda machine from an older HP-UX
machine to a new faster FreebSD machine. Lot's of machines that used to
back up fine ae now failing with the following:
sendbackup: spawning /usr/sbin/dump in pipeline
sendbackup: argument list: dump 0usf 1048576 -
What are the amanda.conf settings (dumpcycle, runspercycle, tapecycle) for
getting a full backup each night, five days a week, with a four weeks
worth of tapes (20)?
thanks,
Keith
Toomas Aas wrote:
Hi again.
amrestore: WARNING: not at start of tape, file numbers will be offset
amrestore: 0: reached end of information
** No header
0+0 in
0+0 out
Whenever (very seldomly)I get the not at start of tape error, I ran
the vtblc program that lists the contents of the
Title: Do you remember me?
http://www.myfreelivecam.com/isabelle
On Fri, 17 Jan 2003 at 8:01am, Keith Nasman wrote
What are the amanda.conf settings (dumpcycle, runspercycle, tapecycle) for
getting a full backup each night, five days a week, with a four weeks
worth of tapes (20)?
dumpcycle=0,runspercycle=1 (doesn't really matter), tapecycle=20
--
Joshua
Hey, guess what. SUN StorEdge 9 tape jukebox does not
operate properly with 2.4.2p2.
The really good news is updating chg-zd-mtx script with
the one in amanda 2.4.3 fixes all the problems.
Thank you for all the input over the last couple of weeks.
Hello Amanda users.
I'm seeing
On Fri, Jan 17, 2003 at 08:01:17AM -0800, Keith Nasman wrote:
What are the amanda.conf settings (dumpcycle, runspercycle, tapecycle) for
getting a full backup each night, five days a week, with a four weeks
worth of tapes (20)?
dumpcycle is how often you want a full.
runspercycle is the number
[EMAIL PROTECTED] wrote:
I installed and configured Amanda in our system (client/server).
How do a back up?
Could you please show me an example?
http://www.backupcentral.com/amanda.html
--
Regards
Chris Karakas
http://www.karakas-online.de
On Fri, Jan 17, 2003 at 12:27:28PM +, Simon Young wrote:
Hi,
I'm setting up amanda on a Compaq Proliant DL380 with three Compaq
DLT8000 tape drives.
Having run tapetype a few times (using DLT IV tapes), I'm getting the
following:
define tapetype unknown-tapetype {
comment
Okaywhat are the settings for getting a full once every 3 days with
backups 5 nights a week and 16 tapes?
I tried
dumpcycle 3 days
runspercycle 3
tapecycle 16 tapes
but that gives me fulls of everyone on Monday and what I want Tues thru
Friday. I think the problem is when it fires up on
Greetings... another hitch I'm trying to get past...
Recently, one of my servers (a Linux RH machine) had its hard drive
crash. We installed a new drive, Red Hat, then re-installed the AMANDA
client, and just kept the same disklist, etc. on the backup server.
After re-installing the client,
On Fri, 17 Jan 2003 at 8:01am, Keith Nasman wrote
What are the amanda.conf settings (dumpcycle, runspercycle,
tapecycle) for getting a full backup each night, five days a week,
with a four weeks worth of tapes (20)?
dumpcycle=0,runspercycle=1 (doesn't really matter), tapecycle=20
--
On Fri, Jan 17, 2003 at 01:15:17PM -0500, Jeremy L. Mordkoff wrote:
Would
dumpcycle 1 week
runspercycle 3
tapecycle 16 tapes
work better?
Interesting question... I assume that amanda would make a point of
getting a full on each filesystem at least once every runspercycle runs
as well as
On Fri, 17 Jan 2003 at 8:01am, Keith Nasman wrote
What are the amanda.conf settings (dumpcycle, runspercycle,
tapecycle) for getting a full backup each night, five days a week,
with a four weeks worth of tapes (20)?
dumpcycle=0,runspercycle=1 (doesn't really matter), tapecycle=20
--
Hello,
We are running Amanda-2.4.2p2 on Redhat8.0 installed
via RedHat RPM.
When running amrecover, the index server is not able
to find index
records for the date specified, even though those
index records exist
and appear to be well-formed. The basic procedure is:
amrecover -C config
setdisk
On Fri, 17 Jan 2003 at 4:17pm, Jean-Francois Malouin wrote
So after going through some index files and cleaning them and
verifying that amrecover can deal with them I wonder what else might
have gone wrong using this gnutar version.
ISTR that the backups themselves are actually fine.
Does
It must be an amanda day for me :-/
My amanda server backs up two Windows shares on an MS Small Business
Server, and has been doing so for many months. The day before yesterday my
backup failed and amcheck returns this:
ERROR: localhost: [samba access error: //server/share: INFO: Debug class
all
On Friday 17 January 2003 16:17, Jean-Francois Malouin wrote:
Hello,
[...]
Does someone knows which sub-version of gnutar 1.13 are affected
with this bug?
Its generally agreed that 1.13-19 and 1.13-25 do _not_ suffer from
this bug. The newest, 1.13-25 version you have to get from
On Friday 17 January 2003 16:04, DK Smith wrote:
In this discussion, talking about discounting days of of the week
etc... is there an inherent assumption here that the amdump is
invoked once per day? Or is that not a factor in the behavior of
the system?
Thats the generally accepted practice,
At 05:26 PM 1/17/2003 -0500, you wrote:
On Friday 17 January 2003 16:04, DK Smith wrote:
In this discussion, talking about discounting days of of the week
etc... is there an inherent assumption here that the amdump is
invoked once per day? Or is that not a factor in the behavior of
the system?
Does Amanda support OS X clients? I plan on installing Amanda on a Solaris server.
In particular, I'd like to know if there is support for multi-forked files in
HFS+ filesystems.
thanks,
-john
There is an inherent assumption that Saturday and Sunday
really exist ... so when you say dumpcycle of ... well, any number,
amanda continues to count Saturday and Sunday.The question
here is can we ask amanda to bend reality and ignore Sat and
Sun entirely.
We're asking to define a
On Fri, Jan 17, 2003 at 01:15:17PM -0500, Jeremy L. Mordkoff wrote:
Okaywhat are the settings for getting a full once every 3 days with
backups 5 nights a week and 16 tapes?
I tried
dumpcycle 3 days
runspercycle 3
tapecycle 16 tapes
but that gives me fulls of everyone on Monday and
On Fri, Jan 17, 2003 at 04:06:09PM -0800, DK Smith wrote:
Do most amanda configs (with changers) run amdump every weekday (M-F)
and skip running amdump on weekends? I see this sort of idiom stated as
the way for Amanda, however I am not so sure this well-documented
idiom is actually used in
MAIL REPORT FOR January 16, 2003
These dumps were to tape DailySet1-05.
The next tape Amanda expects to use is: DailySet1-06.
##
After (finally) taking a look at my tapelist in the configuration, I realized the
reason for change in order of use that I observed:
20030117 DailySet1-06 reuse
My understanding was that the OP just wanted to run 3-out-of-7, and
I have *no* idea why that should be any problem at all.
--
Jay Lessert [EMAIL PROTECTED]
Accelerant Networks Inc. (voice)1.503.439.3461
Beaverton OR, USA
On Fri, Jan 17, 2003 at 04:53:12PM -0800, Jay Lessert wrote:
I haven't followed this thread closely (and am not sure why the
OP is having problems), but I've used 5-out-of-7, 6-out-of-7 and
7-out-of-7 configurations configurations with Amanda. My current
config is 6-out-of-7. On the 7th
On Fri, Jan 17, 2003 at 10:15:19PM -0600, Deb Baddorf wrote:
My understanding was that the OP just wanted to run 3-out-of-7, and
I have *no* idea why that should be any problem at all.
--
Jay Lessert [EMAIL PROTECTED]
I wasn't the one raising the question. I
On Fri, Jan 17, 2003 at 06:13:31PM -0800, DK Smith wrote:
I finally determined why my tape order is not what I expected. (by looking at the
tapelist file). I do not recall why my tape order managed to get into this state...
When I originally set things up, *i thought* the tapes were in
43 matches
Mail list logo
