RE: RedHat, amanda, and permission denied
Hi Peter, Redhat setup everything for amanda using user amanda. So if you use user amanda to run your backups, you'll be fine. You don't specify the backup type you use. (GNU)Tar is recommended for Linux systems. I guess you added /dev/sda1 to your disklist. I think you should add /boot and /usr (diretory names instead of device names) to your disklist. Succes, Edwin -- From: Peter Seebach[SMTP:[EMAIL PROTECTED]] Reply To: Peter Seebach Sent: Thursday, July 25, 2002 6:40 AM To: [EMAIL PROTECTED] Subject:RedHat, amanda, and permission denied I'm trying to set Amanda up on a redhat system. I'm using an account operator, which I moved into group disk, the group listed as having r/w access to the disk devices. If I run: su operator -c amcheck config I get a slew of /dev/sda?: permission denied messages. If I do: su - operator $ dd if=/dev/sda1 of=/dev/null bs=1k count=1 it works fine. So, I have permission to read the disk. What am I doing wrong? -s
amanda-2.4.3b3 and tapeless backup
hi all, i'm trying to do tapeless backup with the amanda-2.4.3b3 The tapedevice is set as follow: runtapes 1 tapedev file:/home/amanda/backup if /home/amanda/backup is empty i get... ]$ amcheck config #Amanda Tape Server Host Check #- #Holding disk /home/amanda/backup: 60136384 KB disk space available, #that's plenty #ERROR: file:/home/amanda/backup: rewinding tape: Input/output error # (expecting a new tape) #NOTE: skipping tape-writable test #Server check took 0.001 seconds if i create the subdirectory data i get the following error: ]$ amcheck config #Amanda Tape Server Host Check #- #Holding disk /home/amanda/backup: 60136380 KB disk space available, #that's plenty #ERROR: file:/home/amanda/backup: not an amanda tape # (expecting a new tape) #NOTE: skipping tape-writable test #Server check took 0.000 seconds i'm wondering what should contain the /home/amanda/backup/ directory to emulate a tape .? -- Pierre-yves Verdon Wanadoo Portails (FRANCE) -- First they ignore you Then they laugh at you Then they fight you Then you win --Mahatma Gandhi
status of cygwin and amanda
Hi all- I know there is a amanda gui client and applications for win32; but I have a working cygwin build on several systems primarily to use some mail tools like mutt. I also read in the archive that some folks have attempted or perhaps completed a port of the amanda-client to cygwin. I use cygwin on windows 2000 pro here. The cygwin mailing list points to a finished amanda-client port but I cannot find the software anywhere after the initial announcement by the person that did the port. Can anyone direct me to a location for a download of a ported amanda or perhaps give me some information on getting amanda-client working on cygwin? Thanks! -- Michael Perry [EMAIL PROTECTED]
help, amrecover connection refused
I have an amanda server s6a.server.com and I backed up clients s2a.client.com /home to the server. On the server amanda user is amanda on the client amanda user is root when I log on to the client and type amrecover -s s6a.server.com -t s6a.server.com I get amrecover: cannot connect to s6a.server.com: Connection refused I have a .amandahosts on both sides in amanda home directory on server and root home directory on client. any help would be greatly appreciated __ Do You Yahoo!? Yahoo! Autos - Get free new car price quotes http://autos.yahoo.com
Re: RedHat, amanda, and permission denied
In message [EMAIL PROTECTED], Edwin Hakkennes writes: Hi Peter, Redhat setup everything for amanda using user amanda. So if you use user amanda to run your backups, you'll be fine. I could find no trace of a user amanda in the system. -s
Re: RedHat, amanda, and permission denied
In message [EMAIL PROTECTED], Martin Hepworth writes: Peter Did you configure amanda with the --with-user=operator config option? I think so; if nothing else, that's in amanda.conf. -s
Re: RedHat, amanda, and permission denied
On Thu, 2002-07-25 at 16:24, Peter Seebach wrote: In message [EMAIL PROTECTED], Martin Hepworth writes: Peter Did you configure amanda with the --with-user=operator config option? I think so; if nothing else, that's in amanda.conf. Are you using an Officially released version of Amanda from RedHat? If so it automatically uses --with-user=amanda. So user is: amanda and group is :disk Try installing the default RH rpms. I'm running 7.3 and that ships with: amanda-2.4.2p2-7 Mark -- --- To steal ideas from one person is plagiarism; to steal from many is research.
RE: status of cygwin and amanda
It's been discussed, a couple of people have it working, but we don't have a set of patches suitable for public consumption yet. Since my SAMBA backups are 99% working, I haven't put a lot of time into this lately. It is possible to go there, but there isn't a map yet. -Original Message- From: Michael Perry [mailto:[EMAIL PROTECTED]] Sent: Thursday, July 25, 2002 10:43 AM To: [EMAIL PROTECTED] Subject: status of cygwin and amanda Hi all- I know there is a amanda gui client and applications for win32; but I have a working cygwin build on several systems primarily to use some mail tools like mutt. I also read in the archive that some folks have attempted or perhaps completed a port of the amanda-client to cygwin. I use cygwin on windows 2000 pro here. The cygwin mailing list points to a finished amanda-client port but I cannot find the software anywhere after the initial announcement by the person that did the port. Can anyone direct me to a location for a download of a ported amanda or perhaps give me some information on getting amanda-client working on cygwin? Thanks! -- Michael Perry [EMAIL PROTECTED]
Re: RedHat, amanda, and permission denied
On Thursday 25 July 2002 11:24, Peter Seebach wrote: In message [EMAIL PROTECTED], Martin Hepworth writes: Peter Did you configure amanda with the --with-user=operator config option? I think so; if nothing else, that's in amanda.conf. -s That is only for the mail receiver. the --with-user etc stuff is a configure tme option only, and compiled in from that. If you are using the rpms from RH, then you are required to use amanda as the user, and disk as the group IIRC. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.08% setiathome rank, not too shabby for a WV hillbilly
Re: RedHat, amanda, and permission denied
In message 1027611162.2658.46.camel@stimpy, Mark Cooke writes: On Thu, 2002-07-25 at 16:24, Peter Seebach wrote: In message [EMAIL PROTECTED], Martin Hepworth writes: Peter Did you configure amanda with the --with-user=operator config option? I think so; if nothing else, that's in amanda.conf. Are you using an Officially released version of Amanda from RedHat? If so it automatically uses --with-user=amanda. No... I looked around, and there wasn't one, so I assumed I'd be fine just downloading and compiling. I guess I need to find the RPM. -s
Re: RedHat, amanda, and permission denied
In message [EMAIL PROTECTED], Martin Hepworth writes: Ok so when you compiled did to specify the user and group or not give theses params to configure ?? I don't remember now. I'll have to check. If you didn't you'll need to rerun configure with them in (I recommend and makle clean before hand). Thanks, if I can't easily find the Amanda RPM's, I'll do that. -s
Re: RedHat, amanda, and permission denied
Peter Seebach wrote: In message 1027611162.2658.46.camel@stimpy, Mark Cooke writes: On Thu, 2002-07-25 at 16:24, Peter Seebach wrote: In message [EMAIL PROTECTED], Martin Hepworth writes: Peter Did you configure amanda with the --with-user=operator config option? I think so; if nothing else, that's in amanda.conf. Are you using an Officially released version of Amanda from RedHat? If so it automatically uses --with-user=amanda. No... I looked around, and there wasn't one, so I assumed I'd be fine just downloading and compiling. I guess I need to find the RPM. -s Peter Ok so when you compiled did to specify the user and group or not give theses params to configure ?? If you didn't you'll need to rerun configure with them in (I recommend and makle clean before hand). -- Martin
Index search script
Hello everyone.
I was recently in need of a way to search through my Amanda indexes, so
I wrote a bash script to do just that. I have seen a few other people
on this list looking for a way to search the index, to I figured I'd
post my script. It works well for me, but YMMV.
I'm just going to attach the script to this message, since it isn't very
large, but for future reference, is there a better way to post this sort
of thing?
Anthony Valentine
#!/bin/bash
### Start of Script
###
amindexsearch - Searches through and Amanda index directory searching
for specified patterns and (optionally) a date
---
begin: Thu Jul 25 09:02:56 AKDT 2002
copyright: (C) 2002 by Anthony Valentine
email: [EMAIL PROTECTED]
###
###
# #
# This program is free software; you can redistribute it and/or modify #
# it under the terms of the GNU General Public License as published by #
# the Free Software Foundation; either version 2 of the License, or #
# (at your option) any later version. #
# #
###
### This next line is needed on my systems to set certain environment
### variables. Everyone else should leave it commented out.
#. /etc/profile.gemini
## Turn on debugging
DEBUG=off
if [ ! ${DEBUG} = off ]; then
set -x
fi
if [ $# -lt 2 ] || [ ${1} = --help ] || [ ${1} = -h ]; then
echo
echo Usage: `basename $0` configname [-d datestring] pattern1 [pattern2] ... [paternN]
echo
echo Where: configname is an Amanda configuration name.
echo datestring is a string in MMDD format (ex. 20020725).
echo patternX are the grep regexp patterns to search for.
echo
echo Note that Config name is case sensitive, but the search patterns are not.
echo
echo
exit 1
fi
### Set TEMPFILE variables; remove the files before we start
TEMPFILE1=/tmp/amindextmp1.$$
rm -f ${TEMPFILE1}
### Find the amanda home directory in the password file
AMANDAHOME=`cat /etc/passwd |grep ^amanda: | cut -d: -f 6`
### Check for a valid config directory
if [ -d ${AMANDAHOME}/${1} ]; then ### Check first in Amanda's home dir (that's where I keep mine)
AMCONFIG=${AMANDAHOME}/${1}
elif [ -d /usr/local/etc/amanda/${1} ]; then ### Then check default location
AMCONFIG=/usr/local/etc/amanda/${1}
else
echo
echo Invalid Config Name ### If not found, exit with an error
echo
exit 2
fi
### Check for datestring; note that DATESTRING is NOT validated as an actual date
if [ ${2} = -d ]; then
DATESTRING=${3}
shift 2
else
DATESTRING=.
fi
### Get the index directory from the amanda.conf file
INDEXDIR=`cat ${AMCONFIG}/amanda.conf | grep ^indexdir | awk '{print $2}' | sed 's///g'`
### Create a file of search patterns entered on the command line
shift 1
while [ $# -gt 0 ]
do
echo ${1} ${TEMPFILE1}
shift 1
done
### Print a header
echo LVL HOST DATE DISK FILE
echo --- - -
### Search through index dir for matches.
cd ${INDEXDIR}
for INDEX in `find . -print`
do
### Search inside each compressed index file;
for FILE in `zcat ${INDEX} 2/dev/null | grep -if ${TEMPFILE1} 2/dev/null`
do
### get the HOST and pad it out to 10 chars long (for neater printing)
SETHOSTTMP=`echo ${INDEX} | awk -F/ '{print $2}'`
SETHOST=`echo ${SETHOSTTMP}'' | sed 's/^\(..\).*$/\1/'`
### get the DISKLIST and pad it out to 25 chars (for neater printing)
SETDISKTMP=`echo ${INDEX} | awk -F/ '{print $3}' | sed 's/_/\//'`
SETDISK=`echo ${SETDISKTMP}'' | sed 's/^\(.\).*$/\1/'`
### get the DATE and BACKUP LEVEL
DATELEVEL=`echo ${INDEX} | awk -F/ '{print $4}'`
SETDATE=`echo ${DATELEVEL} | awk -F_ '{print $1}'`
LEVEL=`echo ${DATELEVEL} | awk -F_ '{print $2}' | awk -F. '{print $1}'`
### Print all that, the name of the file and replace the pad char with spaces
echo ${LEVEL} ${SETHOST}${SETDATE} ${SETDISK}${FILE}| sed 's/\/ /g' | grep ${DATESTRING}
done
done
### Clean up
rm ${TEMPFILE1}
### End of Script
exit 0
RE: RedHat, amanda, and permission denied
The Redhat 7.2 distribution contained an RPM that was only the client and not the complete package. Needless to say that didn't work for me. I had the best luck doing the compile. Just an FYI Doug -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, July 25, 2002 12:50 PM To: [EMAIL PROTECTED] Subject: Re: RedHat, amanda, and permission denied In message [EMAIL PROTECTED], Martin Hepworth writes: Ok so when you compiled did to specify the user and group or not give theses params to configure ?? I don't remember now. I'll have to check. If you didn't you'll need to rerun configure with them in (I recommend and makle clean before hand). Thanks, if I can't easily find the Amanda RPM's, I'll do that. -s
Re: RedHat, amanda, and permission denied
Doug Johnson wrote: The Redhat 7.2 distribution contained an RPM that was only the client and not the complete package. Needless to say that didn't work for me. I had the The complete package consists of 4 RPMs: amanda, amanda-client, amanda-server (only needed on the server), and amanda-devel (only needed for development work). They should all be on your distribution CDs. John Dalbec OT: How are the IOCCC results coming along? best luck doing the compile. Just an FYI Doug -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, July 25, 2002 12:50 PM To: [EMAIL PROTECTED] Subject: Re: RedHat, amanda, and permission denied In message [EMAIL PROTECTED], Martin Hepworth writes: Ok so when you compiled did to specify the user and group or not give theses params to configure ?? I don't remember now. I'll have to check. If you didn't you'll need to rerun configure with them in (I recommend and makle clean before hand). Thanks, if I can't easily find the Amanda RPM's, I'll do that. -s
Re: RedHat, amanda, and permission denied
On Thursday 25 July 2002 12:07, Peter Seebach wrote:
In message 1027611162.2658.46.camel@stimpy, Mark Cooke writes:
On Thu, 2002-07-25 at 16:24, Peter Seebach wrote:
In message [EMAIL PROTECTED], Martin Hepworth
writes:
Peter
Did you configure amanda with the --with-user=operator config
option?
I think so; if nothing else, that's in amanda.conf.
Are you using an Officially released version of Amanda from
RedHat? If so it automatically uses --with-user=amanda.
No... I looked around, and there wasn't one, so I assumed I'd be
fine just downloading and compiling. I guess I need to find the
RPM.
Not required. Building from sources is the prefered method to the
majority of this group's readers.
However, with the rather lengthy options one should give the
configure program, I find it easy to keep from making mistakes as I
build each newer snapshot by doing the configuration with a script.
As pointed out in the readme's, one should do certain things to
build amanda properly. And because amanda isn't built while being
root, its normally built in
/home/amanda/amanda-version-snapshot-date
instead of /usr/src.
1. As user amanda, in the /home/amanda directory, unpack the tar.gz.
2. su - to get root privs and cd back to /home/amanda, and do
#chown -R amanda:disk amanda-version-snapshot-date
3. exit back to user amanda and cd into this directory.
4. run this script after editing things to suit your setup:
#!/bin/sh
make clean
rm -f config.status config.cache
./configure \
--with-user=amanda \
--with-group=disk \
--with-owner=amanda \
--with-tape-device=/dev/nst0 \
--with-changer-device=/dev/sg1 \
--with-gnu-ld --prefix=/usr/local \
--with-debugging=/tmp/amanda-dbg/ \
--with-tape-server=IP.OF.MACHINE.WITH-drive \
--with-amandahosts \
--with-configdir=/usr/local/etc/amanda
---
which for obvious reasons I call gh.cf, set the exec bits and
#./gh.cf
and watch it run.
If you don't have a changer, remove that line from the above script
and fix other things to fit your system too.
5. when its done;
#make
6. su - to get root privs again, and
#make install
The installer will take care of setting all the perms. Only the
user 'amanda' can run amanda, and amanda takes care of getting root
priviledges when she needs to automaticly, and in fact most of it
won't run when you are root. When you're happy that it will run,
then you, as user amanda, make up the crontab entries that are in
the docs, and which will run amanda from then on.
7. At this point you are ready to start setting up your own
/usr/local/etc/amanda/configname/amanda.conf.
And from there its all in the details.
Make yourself a disklist with only a couple of entries to get
started, more can be added later.
Repeated runs of 'amcheck configname', making dirs, touching files
and such until you are down to the 'host down' error, which means
that inetd.conf, or xinetd is miss-configured, if you system runs
inetd, see the docs. If its running xinetd, then you'll have an
/etc/xinetd.d directory, and you'll need this file, named 'amanda'
to be installed in the above directory:
-
# default = off
#
# description: Part of the Amanda server package
# This is the list of daemons such it needs
service amanda
{
disable = no
socket_type = dgram
protocol= udp
wait= yes
user= amanda
group = disk
groups = yes
server = /usr/local/libexec/amandad
}
service amandaidx
{
disable = no
socket_type = stream
protocol= tcp
wait= no
user= amanda
group = disk
groups = yes
server = /usr/local/libexec/amindexd
}
service amidxtape
{
disable = no
socket_type = stream
protocol= tcp
wait= no
user= amanda
group = disk
groups = yes
server = /usr/local/libexec/amidxtaped
}
--
Don't forget to chown this file to amanda:disk
This should get you there, if not, come and yell at one of us and
we'll 'have another go' at it.
--
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz 512M
99.08% setiathome rank, not too shabby for a WV hillbilly
dumpcycle 0 not using holding space
I am running an Amanda configuration intended to do a full backup every 2
weeks on 2 tapes. I need 2 tapes because I know at least one of the
partitions will not fit on the tape. I intend to run amflush to get the
last partition on the second tape. My problem is that with the current
configuration, Amanda never leaves anything in the holding space! I have
plenty of room, but there is never anything left there. The backup report
clearly states:
*** A TAPE ERROR OCCURRED: [[writing file: No space left on device]].
Some dumps may have been left in the holding disk. Run amflush to flush
them to tape.
But there is nothing in the holding disk! Can anyone help me out?
I have the following configuration for an archival backup setup:
amanda.conf:
dumpcycle 0
runspercycle 2
tapecycle 2 tapes
define dumptype comp-root-full {
comment Root partitions with compression
compress client fast
priority low
record no
index yes
}
define dumptype comp-user-full {
global
comment Non-root partitions on reasonably fast machines
compress client fast
priority medium
record no
index yes
}
disklist:
server02.ctsda1 comp-root-full 1
server02.ctsda2 comp-user-full 1
server02.ctsdb1 comp-user-full 2
Thank you,
Cory Visi
Re: RedHat, amanda, and permission denied
On Thu, 2002-07-25 at 19:02, Gene Heskett wrote: Not required. Building from sources is the prefered method to the majority of this group's readers. I personally prefer to use the source, but it really depends upon what you want. The RedHat prebuilt rpms from RH themselfs are perfectly ok and are prebuilt with all the correct permissions set. Also it really depends upon you're software accounting (the company I work for require me to make rpm.specs if I happen to want to install any programs that are not rpms, as they can easily remove or upgrade them with only 1 easy line.) But if *you* want control, then do as Gene says and use the source or Download the amanda rpms from RH. If you are using up2date then just issue: /usr/sbin/up2date amanda-server amanda-client. (this gets them all and will allow you to backup you're tape server as well, for the clients, just get amanda-client) or get them from here: ftp://ftp.mirror.ac.uk/sites/ftp.redhat.com/pub/redhat/linux/7.3/en/os/i386/RedHat/RPMS/ (just alter you're Distro number) Mark -- --- To steal ideas from one person is plagiarism; to steal from many is research.
Re: dumpcycle 0 not using holding space
At 02:35 PM 7/25/2002 -0400, Cory Visi wrote: I am running an Amanda configuration intended to do a full backup every 2 weeks on 2 tapes. I need 2 tapes because I know at least one of the partitions will not fit on the tape. I intend to run amflush to get the last partition on the second tape. My problem is that with the current configuration, Amanda never leaves anything in the holding space! I have plenty of room, but there is never anything left there. Look at the comments about holding disk, in the config file. By default, all the space is reserved for incremental backups, and no fulls are stored on the holding disk (once the first tape is full, I mean). Here's the section: # If amanda cannot find a tape on which to store backups, it will run # as many backups as it can to the holding disks. In order to save # space for unattended backups, by default, amanda will only perform # incremental backups in this case, i.e., it will reserve 100% of the # holding disk space for the so-called degraded mode backups. # However, if you specify a different value for the `reserve' # parameter, amanda will not degrade backups if they will fit in the # non-reserved portion of the holding disk. reserve 30 # percent ## (this is MY value) # This means save at least 30% of the holding disk space for degraded # mode backups. --- Deb Baddorf [EMAIL PROTECTED] 840-2289 You can't help getting older, but you don't have to get old. - George Burns IXOYE
Peer review for chg-scsi usage document
Hello, I am in the process of documenting in a bit more detail chg-scsi. I would love it if you all would tell me what you thought so far. I would eventually like to expand it to include some of amanda's actual interactions, etc. --jason -- ~~~ Jason Brooks ~ (503) 641-3440 x1861 Direct ~ (503) 924-1861 System / Network Administrator Wind River Systems 8905 SW Nimbus ~ Suite 255 Beaverton, Or 97008 chg-scsi.doc Description: MS-Word document
RE: dumpcycle 0 not using holding space
weeks on 2 tapes. I need 2 tapes because I know at least one of the partitions will not fit on the tape. I intend to run amflush AMANDA can't split a partition across tapes, so if you're saying what I think you're saying, and one of your partitions is bigger than one of your tapes, you have a bigger problem than holding disk use. You'll need to split the partition into several tar-able chunks.
amlabel error
O' gurus, I initially labeled 10 tapes for my rotation and now I am labeling another 10. My first couple of tapes got labeled fine but now I'm getting this: [root@presto DailySet1]# su amanda -c amlabel DailySet1 DailySet113 rewinding, reading label, reading label: Cannot allocate memory rewinding, writing label DailySet113, checking label, done. I assume that the tape got labeled correctly. Can anyone enlighten me on the memory error? Thanks, Keith
Re: Peer review for chg-scsi usage document
On Thursday 25 July 2002 15:22, Jason Brooks wrote: Hello, I am in the process of documenting in a bit more detail chg-scsi. I would love it if you all would tell me what you thought so far. I would eventually like to expand it to include some of amanda's actual interactions, etc. --jason I use it here, Jason, and this looks ok so far. Some better than the help in the files comments actually. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.08% setiathome rank, not too shabby for a WV hillbilly
Re: amlabel error
On Thursday 25 July 2002 15:40, Keith Nasman wrote: O' gurus, I initially labeled 10 tapes for my rotation and now I am labeling another 10. My first couple of tapes got labeled fine but now I'm getting this: [root@presto DailySet1]# su amanda -c amlabel DailySet1 DailySet113 rewinding, reading label, reading label: Cannot allocate memory rewinding, writing label DailySet113, checking label, done. I assume that the tape got labeled correctly. Can anyone enlighten me on the memory error? Hummm, not brand new tapes? Maybe a tape that was used with another backup util, probably proprietary? What it sounds like is that when amanda tried to read the initial header from the tape, its encountering a totally humungous value the tapes block size and can't allocate that much memory. My best guess... Anyway, dd can retrieve the tape label with this pair of commands: #mt -f /dev/tape_device rewind #dd if = /dev/tape_device count = 1 which should disgorge the first block of 512 bytes to the screen, showing you the label as written. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.08% setiathome rank, not too shabby for a WV hillbilly
Re: Peer review for chg-scsi usage document
On Thursday 25 July 2002 16:05, Anthony A. D. Talltree wrote: I would love it if you all would tell me what you thought so far Encrypting the document makes it kinda tough to read. What email agent are you using? Kmail showed it to me in plain text, and also saved it that way, in 2 seperate actions. The header didn't show any mimetype specs either, which essentially tells me it was plain text, not even base64'd for transport. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.08% setiathome rank, not too shabby for a WV hillbilly
Re: Peer review for chg-scsi usage document
What email agent are you using? You've never heard of it, and it doesn't matter. The header didn't show any mimetype specs either --cmJC7u66zC7hs+87 Content-Type: application/msword Content-Disposition: attachment; filename=chg-scsi.doc Since it appeared to be encrypted, I hadn't tried to look at it. Lo and behold, it's a text document after all.
tape error???
Hello,
I need help with figuring out why
amanda is giving me tape errors. First off I am using Sony 20/40G dgd 150p tapes
on a Dell powervault 120T DDS-4 autoloader on RedHat 7.2. Being that the tapes I
am using were not in the tapelist I ran the command
# tapetype -f /dev/nst0 -t DDS-4
and the output after several hours was
define tapetype DDS-4 {
comment "just produced by
tapetype program"
length 16323
mbytes
filemark 190
kbytes
speed 1264
kps
}
So I put this info in my amanda.conf file and
defined tapetype as DDS-4.
So then I ran the command
bash-2.05$ /usr/sbin/amcheck DailySet1
as the user amanda and I get the output
of
Amanda Tape Server Host Check
-
ERROR: /dev/nst0: not an amanda tape
(expecting a new tape)
NOTE: skipping tape-writable test
NOTE: info dir /var/lib/amanda/DailySet1/curinfo: does not exist
NOTE: it will be created on the next run
Server check took 5.000 seconds
Amanda Backup Client Hosts Check
Client check: 1 host checked in 0.015 seconds, 0 problems found
(brought to you by Amanda 2.4.2p2)
I have also sent a copy of my amanda.conf as an attatchment. If anyone can
help I would highly appreciate it.
Thanks,
Chris Bourne
Chris BourneSystems/Network
AdministratorXapnet Phone (510)655-9771Fax (510)655-9775http://www.xapnet.com
amanda.conf
Description: Binary data
Re: tape error???
At 01:49 PM 7/25/2002 -0700, Chris Bourne wrote: Hello, I need help with figuring out why amanda is giving me tape errors. . bash-2.05$ /usr/sbin/amcheck DailySet1 - ERROR: /dev/nst0: not an amanda tape (expecting a new tape) amanda wants you to label each tape before use: amlabel DailySet1 DailySet101 #for example tape name is specified here, from your config file: labelstr ^DailySet1[0-9][0-9]*$ # label constraint regex: all tapes must match Deb
Re: Peer review for chg-scsi usage document
Hello, You know, I think I typed the .doc extension by habit: It's a plain text file. I used vim to type it. Sorry for the mixup. Were there actually any headers in it other than the name of the file? On Thu, Jul 25, 2002 at 01:05:02PM -0700, Anthony A. D. Talltree wrote: I would love it if you all would tell me what you thought so far Encrypting the document makes it kinda tough to read. -- ~~~ Jason Brooks ~ (503) 641-3440 x1861 Direct ~ (503) 924-1861 System / Network Administrator Wind River Systems 8905 SW Nimbus ~ Suite 255 Beaverton, Or 97008
Re: amlabel error
On Thu, 25 Jul 2002, Gene Heskett wrote: On Thursday 25 July 2002 15:40, Keith Nasman wrote: [root@presto DailySet1]# su amanda -c amlabel DailySet1 DailySet113 rewinding, reading label, reading label: Cannot allocate memory rewinding, writing label DailySet113, checking label, done. I assume that the tape got labeled correctly. Can anyone enlighten me on the memory error? Hummm, not brand new tapes? Maybe a tape that was used with another backup util, probably proprietary? These are not brand new tapes. Leftovers from ArcServe for NT. What it sounds like is that when amanda tried to read the initial header from the tape, its encountering a totally humungous value the tapes block size and can't allocate that much memory. My best guess... Anyway, dd can retrieve the tape label with this pair of commands: #mt -f /dev/tape_device rewind #dd if = /dev/tape_device count = 1 which should disgorge the first block of 512 bytes to the screen, showing you the label as written. Hmmm, this is what I get. [root@presto amanda]# mt -f /dev/nst0 rewind [root@presto amanda]# dd if=/dev/nst0 count=1 dd: reading `/dev/nst0': Cannot allocate memory 0+0 records in 0+0 records out yet, I get this output from amcheck [root@presto amanda]# su amanda -c amcheck DailySet1 Amanda Tape Server Host Check - Holding disk /var/tmp: 127389 KB disk space available, that's plenty NOTE: skipping tape-writable test Tape DailySet114 label ok so it looks like the tape label is fine. shrug Keith
Re: amlabel error
On Thursday 25 July 2002 17:44, Keith Nasman wrote: On Thu, 25 Jul 2002, Gene Heskett wrote: On Thursday 25 July 2002 15:40, Keith Nasman wrote: [root@presto DailySet1]# su amanda -c amlabel DailySet1 DailySet113 rewinding, reading label, reading label: Cannot allocate memory rewinding, writing label DailySet113, checking label, done. I assume that the tape got labeled correctly. Can anyone enlighten me on the memory error? Hummm, not brand new tapes? Maybe a tape that was used with another backup util, probably proprietary? These are not brand new tapes. Leftovers from ArcServe for NT. What it sounds like is that when amanda tried to read the initial header from the tape, its encountering a totally humungous value the tapes block size and can't allocate that much memory. My best guess... Anyway, dd can retrieve the tape label with this pair of commands: #mt -f /dev/tape_device rewind #dd if = /dev/tape_device count = 1 which should disgorge the first block of 512 bytes to the screen, showing you the label as written. Hmmm, this is what I get. [root@presto amanda]# mt -f /dev/nst0 rewind [root@presto amanda]# dd if=/dev/nst0 count=1 dd: reading `/dev/nst0': Cannot allocate memory 0+0 records in 0+0 records out Odd indeed, this is what you should have gotten provided the tape was rewound. [root@coyote root]# dd if=/dev/st0 bs=512 count=1 AMANDA: TAPESTART DATE 20020725 TAPE DailySet1-11 1+0 records in 1+0 records out yet, I get this output from amcheck [root@presto amanda]# su amanda -c amcheck DailySet1 Amanda Tape Server Host Check - Holding disk /var/tmp: 127389 KB disk space available, that's plenty NOTE: skipping tape-writable test Tape DailySet114 label ok so it looks like the tape label is fine. That it does indeed, so I'm scratching my aging head as it doesn't make 100% sense. Any other guesses I'd make ATM would be a very poor version of a (S)WAG. shrug Keith -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.08% setiathome rank, not too shabby for a WV hillbilly
