disk offline
amanda email output,
FAILURE AND STRANGE DUMP SUMMARY:
kascha sdb2 lev 0 FAILED [disk sdb2 offline on kascha?]
kascha sdb1 lev 0 FAILED [disk sdb1 offline on kascha?]
kascha sda1 lev 0 FAILED [disk sda1 offline on kascha?]
Since these are my boot disk and /usr disk they arnt off
line.
:}
Im using GNUTAR (or tryng to) using the options below,
tar version is 1.13.17-2 (latest Debian 2.2r2+)
amanda.conf8><
org "DailySet1" # your organization name for reports
mailto "[EMAIL PROTECTED]" # space separated list of mail ssj
#12
dumpuser "backup" # the user to run dumps under
dumpcycle 1 #ssj added
#tapedev /dev/nst0 #ssj added disabled as per man page
inparallel 4# maximum dumpers that will run in parallel
netusage 6000 # maximum net bandwidth for Amanda, in KB persec
# a filesystem is due for a full backup once every days
#ssj dumpcycle 4 weeks # the number of days in the normal dump cycle
tapecycle 8 tapes # the number of tapes in rotation
#25
bumpsize 20 MB # minimum savings (threshold) to bump level 1 ->
2
bumpdays 1 # minimum days at each level
bumpmult 4 # threshold = bumpsize * (level-1)**bumpmult
#runtapes 9 # explained in WHATS.NEW
#tpchanger "no-changer" # the tape-changer glue script, see
TAPE.CHANGERS
tapedev "/dev/nst0" # Linux @ tuck, important: norewinding
# tapedev "/dev/nrst8" # or use the (no-rewind!) tape device directly
tapetype DEC-DAT# ssj what kind of tape it is
(seetapetypesbelow) dec-tk88
labelstr "^kaitlin[0-9][0-9]*$" # label constraint regex: all tapes
diskdir "/home/amanda" # where the holding disk is (dev/sdc1)
disksize 3000 MB# how much space can we use on
8><
define tapetype DEC-DAT {
comment "DAT tape drives"
length 25000 mbytes # these numbers are not accurate
filemark 100 kbytes # but you get the idea
speed 500 kbytes
}
-8><
}
#ssj my option for linux boxes
define dumptype gnutar-full {
comment "Full dump of this filesystem always"
options compress-fast
priority high
dumpcycle 0
maxcycle 0
}
disklist8><
#start with kascha
kascha sda1 gnutar-full
kascha sdb1 gnutar-full
kascha sdb2 gnutar-full
last log file
amdump: start at Tue Mar 27 07:58:01 NZST 2001
planner: pid 537 executable /usr/lib/amanda/planner version 2.4.1p1
planner: build: VERSION="Amanda-2.4.1p1"
planner:BUILT_DATE="Mon Jun 12 23:14:52 MDT 2000"
planner:BUILT_MACH="Linux rover 2.2.15pre15 #1 Thu Mar 23
02:22:27 MST 2000 i686 unknown"
planner:CC="gcc"
planner: paths: bindir="/usr/sbin" sbindir="/usr/sbin"
planner:libexecdir="/usr/lib/amanda" mandir="/usr/share/man"
planner:CONFIG_DIR="/etc/amanda" DEV_PREFIX="/dev/"
planner:RDEV_PREFIX="/dev/" DUMP="/sbin/dump"
planner:RESTORE="/sbin/restore"
SAMBA_CLIENT="/usr/bin/smbclient"
planner:GNUTAR="/bin/tar" COMPRESS_PATH="/bin/gzip"
planner:UNCOMPRESS_PATH="/bin/gzip" MAILER="/usr/bin/Mail"
planner:listed_incr_dir="/var/lib/amanda/gnutar-lists"
planner: defs: DEFAULT_SERVER="localhost" DEFAULT_CONFIG="DailySet1"
planner:DEFAULT_TAPE_SERVER="localhost"
planner:DEFAULT_TAPE_DEVICE="/dev/null" HAVE_MMAP HAVE_SYSVSHM
planner:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE BSD_SECURITY
planner:USE_AMANDAHOSTS CLIENT_LOGIN="backup" FORCE_USERID
HAVE_GZIP
planner:COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast"
planner:COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc"
READING CONF FILES...
driver: pid 538 executable /usr/lib/amanda/driver version 2.4.1p1
driver: send-cmd time 0.003 to taper: START-TAPER 20010327
startup took 0.005 secs
SETTING UP FOR ESTIMATES...
setting up estimates for kascha:sda1
kascha:sda1 overdue 11408 days for level 0
setup_estimate: kascha:sda1: command 0, options:
last_level -1 next_level0 -11408 level_days 0
getting estimates 0 (0) -1 (-1) -1 (-1)
setting up estimates for kascha:sdb1
kascha:sdb1 overdue 11408 days for level 0
setup_estimate: kascha:sdb1: command 0, options:
last_level -1 next_level0 -11408 level_days 0
getting estimates 0 (0) -1 (-1) -1 (-1)
setting up estimates for kascha:sdb2
kascha:sdb2 overdue 11408 days for level 0
setup_estimate: kascha:sdb2: command 0, options:
last_level -1 next_level0 -11408 level_days 0
getting estimates 0 (0) -1 (-1) -1 (-1)
setting up estimates took 0.000 secs
GET
Re: Backing up incrementals onto hard disk
thanks for your reply. The thing is - I am not sure exactly what you mean - can u explain to me further please? Thanx again Ben Kochie wrote: > you are a bit mistaken as to how amanda works, amanda automaticaly > decides if it should do a full or incremental backup each day of the > backup cycle. if you only want to change tapes once a week, but have > backup every night, here is what you could do. > > have a dump disk big enough to handle all backups for one week, and on > weekends, run amflush to dump those disks to tape. > > mnk wrote: > >> Hello, >> I was wondering - how does one back up dail incrementals onto a hard >> disk while the weekly backups are on tape? >> Thanks. >> Mohammed >
two dumps in one day
hi I have a directory that I must backup sometimes more than once a day... the problem is that when I try to amrecover it I only get the file list of the last dump I made ... what can I do to correct this ? thanks -Miguel
Re: Backing up incrementals onto hard disk
also - how do i recover from the hard disk backup if something goes wrong? Thanks again! mnk wrote: > thanks for your reply. > The thing is - I am not sure exactly what you mean - can u explain to > me further please? > Thanx again > > Ben Kochie wrote: > >> you are a bit mistaken as to how amanda works, amanda automaticaly >> decides if it should do a full or incremental backup each day of the >> backup cycle. if you only want to change tapes once a week, but have >> backup every night, here is what you could do. >> >> have a dump disk big enough to handle all backups for one week, and on >> weekends, run amflush to dump those disks to tape. >> >> mnk wrote: >> >>> Hello, >>> I was wondering - how does one back up dail incrementals onto a hard >>> disk while the weekly backups are on tape? >>> Thanks. >>> Mohammed >> >> > >
Re: more with ADIC-1200 + SunOS 5.8 'sgen' driver and mtx problems
On Mon, 26 Mar 2001, Urban Petry wrote: > > Which device driver are you using under Linux? The equivalent of Sun's > > 'sgen' driver? I am going to try the 'sst' driver supplied with Amanda > > today and see if I get a different result. According to the manual, the > > factory defaults are ID 0 for the drive and ID 3 for the robotics. > > I would say so, since it's the "scsi generic" driver that I use (/dev/sg1) Sounds like it's very similar to Sun's 'sgen' driver in principle. I've checked Sunsolve and there is a patch for the 'sgen' package, but it doens't apply to my platform. I have installed the Solaris 8 Maintenance Update 3 patch package today, but to no avail since the 'sgen' driver is still giving problems. Will try the 'sst' driver out and report on it's performance after I have some sleep! 8-) Regards, Craig. -- Craig Dewick. Send email to "[EMAIL PROTECTED]" Point your web client at "www.sunshack.org" or "www.sunshack.net" to access my archive of Sun technical information and links to other places. For info about Sun Ripened Kernels, go to "www.sunrk.com.au" or "www.sun-surplus.com"
Please help!!
Hi! Basically, it's about amanda tells me there is no tape but guys from company that collocation server told me there is a tape loaded. They check twice. Also, I'm 100% it's not a joke or something like this, but a serios situation I don't know how to manage. [root@server /root]# date Tue Mar 27 10:00:55 EST 2001 [root@server /root]# su amanda -c "amcheck wmw" Amanda Tape Server Host Check - Holding disk /tmp: 366404 KB disk space available, using 212804 KB ERROR: /dev/nst0: rewinding tape: No medium found (expecting tape my_tape_1 or a new tape) NOTE: skipping tape-writable test Server check took 30.107 seconds Amanda Backup Client Hosts Check Client check: 1 host checked in 0.017 seconds, 0 problems found (brought to you by Amanda 2.4.2p1) But from the company that collocate the server I got right now the following message: Date: 27 Mar 2001 09:59:52 -0500 From: <[EMAIL PROTECTED]> To: Radu Filip <[EMAIL PROTECTED]> Subject: Re: Tape Hi Radu We have checked the server.mydomain.com and it has the tape #1 tape in the drive. Best regards [signature] I'm located in Romania and server is in State. I've tried to use mt: [root@server /root]# mt -f /dev/nst0 rewind /dev/nst0: No medium found Last backup was performed succesfully on March 24 and until now there was absolutly no problem with both Amanda and tape. Tape drive is (from dmesg): Detected scsi disk sda at scsi0, channel 0, id 0, lun 0 Vendor: OnStream Model: ADR50 Drive Rev: 2.20 Type: Sequential-Access ANSI SCSI revision: 02 Also, I checked the /var/messages and I got only this lines: [root@server /root]# less /var/log/messages.1.gz | grep st0 Mar 20 05:44:29 server2 kernel: st0: Error with sense data: [valid=0] Info fld=0x0, Current st09:00: sense key Unit Attention Mar 20 06:09:59 server2 kernel: st0: Error with sense data: [valid=0] Info fld=0x0, Current st09:00: sense key Unit Attention but this was *before* my last succesfully backup (March 24): Subject: MY AMANDA MAIL REPORT FOR March 24, 2001 These dumps were to tape my_tape_3. The next tape Amanda expects to use is: my_tape_1. My server is an dual Intel PIII/800 Mhz, with RedHat 6.2 and Kernel 2.2.14-5.0smp. Module for st is loaded: [root@server /root]# lsmod Module Size Used by eepro100 16080 1 (autoclean) st 24656 0 dpt_i2o97248 5 Please tell what could happen here on my server, what to try and what can I do in this strange situation. Thank you in advance, Radu Filip -- Radu Filip Network Administrator @ Technical University of Iasi [EMAIL PROTECTED] Information Technology and Communication Center http://socrate.tuiasi.ro/ [EMAIL PROTECTED] | http://www.ccti.tuiasi.ro/
Re: Backing up incrementals onto hard disk
I think you need to read the amanda documentation. download the source to amanda, and look in the docs directory. also read this document: http://www.backupcentral.com/amanda.html you restore from disk, exactly the same way you restore from tape, please read the documents on how amanda works, they explain it much better than I do. Abu 'Abdis-Salam wrote: > > also - how do i recover from the hard disk backup if something goes wrong? > Thanks again! > > mnk wrote: > > > thanks for your reply. > > The thing is - I am not sure exactly what you mean - can u explain to > > me further please? > > Thanx again > > > > Ben Kochie wrote: > > > >> you are a bit mistaken as to how amanda works, amanda automaticaly > >> decides if it should do a full or incremental backup each day of the > >> backup cycle. if you only want to change tapes once a week, but have > >> backup every night, here is what you could do. > >> > >> have a dump disk big enough to handle all backups for one week, and on > >> weekends, run amflush to dump those disks to tape. > >> > >> mnk wrote: > >> > >>> Hello, > >>> I was wondering - how does one back up dail incrementals onto a hard > >>> disk while the weekly backups are on tape? > >>> Thanks. > >>> Mohammed > >> > >> > > > > -- Ben Kochie | [EMAIL PROTECTED] IMA Systems Office | 400 Lind Hall, 207 Church St. SE http://www.ima.umn.edu | Minneapolis, MN 55455-0463
Re: Please help!!
If "mt" says there is no tape, there isn't any tape. Amanda has nothing to do with it. -- Or the tape drive isn't connected to the SCSI bus. -- Or the power cable isn't plugged in. -- Or the media is defective. -- Or the drive needs cleaning. -- Or the tape drive is buggy. I see that the drive is an OnStream. Haven't there been significant problems reported on this list, with those? For remote backups I prefer to keep a local mirror, using ssh and rsync, and back up from that. When tape drive problems develop, and they usually do sooner or later, I'm not depending on all too often ill-trained and overworked ISP sysadmins to do my troubleshooting for me. Instead, I do the troubleshooting with my own ill-trained and overworked self (chortle) !!! Another option might be changing colocation providers. On Tue, Mar 27, 2001 at 06:15:58PM +0300, Radu Filip wrote: > > Hi! > > Basically, it's about amanda tells me there is no tape but guys from > company that collocation server told me there is a tape loaded. They check > twice. Also, I'm 100% it's not a joke or something like this, but a serios > situation I don't know how to manage. > > [root@server /root]# date > Tue Mar 27 10:00:55 EST 2001 > [root@server /root]# su amanda -c "amcheck wmw" > Amanda Tape Server Host Check > - > Holding disk /tmp: 366404 KB disk space available, using 212804 KB > ERROR: /dev/nst0: rewinding tape: No medium found >(expecting tape my_tape_1 or a new tape) > NOTE: skipping tape-writable test > Server check took 30.107 seconds > > Amanda Backup Client Hosts Check > > Client check: 1 host checked in 0.017 seconds, 0 problems found > > (brought to you by Amanda 2.4.2p1) > > > But from the company that collocate the server I got right now the > following message: > > Date: 27 Mar 2001 09:59:52 -0500 > From: <[EMAIL PROTECTED]> > To: Radu Filip <[EMAIL PROTECTED]> > Subject: Re: Tape > > Hi Radu > > We have checked the server.mydomain.com and it has the tape #1 tape in the > drive. > > Best regards > [signature] > > > I'm located in Romania and server is in State. I've tried to use mt: > [root@server /root]# mt -f /dev/nst0 rewind > /dev/nst0: No medium found > > Last backup was performed succesfully on March 24 and until now there was > absolutly no problem with both Amanda and tape. > > Tape drive is (from dmesg): > Detected scsi disk sda at scsi0, channel 0, id 0, lun 0 > Vendor: OnStream Model: ADR50 Drive Rev: 2.20 > Type: Sequential-Access ANSI SCSI revision: 02 > > Also, I checked the /var/messages and I got only this lines: > [root@server /root]# less /var/log/messages.1.gz | grep st0 > Mar 20 05:44:29 server2 kernel: st0: Error with sense data: [valid=0] Info > fld=0x0, Current st09:00: sense key Unit Attention > Mar 20 06:09:59 server2 kernel: st0: Error with sense data: [valid=0] Info > fld=0x0, Current st09:00: sense key Unit Attention > > but this was *before* my last succesfully backup (March 24): > > Subject: MY AMANDA MAIL REPORT FOR March 24, 2001 > These dumps were to tape my_tape_3. > The next tape Amanda expects to use is: my_tape_1. > > My server is an dual Intel PIII/800 Mhz, with RedHat 6.2 and Kernel > 2.2.14-5.0smp. Module for st is loaded: > > [root@server /root]# lsmod > Module Size Used by > eepro100 16080 1 (autoclean) > st 24656 0 > dpt_i2o97248 5 > > > Please tell what could happen here on my server, what to try and what can > I do in this strange situation. > > Thank you in advance, > Radu Filip > > -- > Radu Filip >Network Administrator @ Technical University of Iasi > [EMAIL PROTECTED] Information Technology and Communication Center > http://socrate.tuiasi.ro/ [EMAIL PROTECTED] | http://www.ccti.tuiasi.ro/ > > > > -- - Dan Wilder <[EMAIL PROTECTED]> Technical Manager & Correspondent SSC, Inc. P.O. Box 55549 Phone: 206-782-7733 x123 Seattle, WA 98155-0549 URLhttp://www.linuxjournal.com/ -
./configure on AIX 4.3.3
I'm getting the following error running ./configure as root:
# ./configure
creating cache ./config.cache
checking host system type... powerpc-ibm-aix4.3.3.0
checking target system type... powerpc-ibm-aix4.3.3.0
checking build system type... powerpc-ibm-aix4.3.3.0
checking cached system tuple... ok
checking for a BSD compatible install... config/install-sh -c
checking whether build environment is sane... yes
checking for mawk... no
checking for gawk... no
checking for nawk... nawk
checking whether make sets ${MAKE}... yes
checking for working aclocal... missing
checking for working autoconf... missing
checking for working automake... missing
checking for working autoheader... missing
checking for working makeinfo... missing
checking for gnutar... no
checking for gtar... no
checking for tar... tar
configure: error: *** --with-user=USER is missing
Re: Please help!!
Hi! On Tue, 27 Mar 2001, Dan Wilder wrote: > If "mt" says there is no tape, there isn't any tape. > Amanda has nothing to do with it. Ok. > -- Or the tape drive isn't connected to the SCSI bus. > -- Or the power cable isn't plugged in. It must be connected because the server is up & running since 13 for now: [root@server /root]# uptime 11:08am up 13 days, 22:08, 3 users, load average: 0.29, 0.17, 0.06 and last succesful backup was on three days ago (on March 24). So I guess it cannot be those two. > -- Or the media is defective. There are only three tapes there and I start using them two weeks ago. Last time tape 1 was uses was on Subject: WMW AMANDA MAIL REPORT FOR March 20, 2001 These dumps were to tape wmw_tape_1. Could that tape be defective so soon? > -- Or the drive needs cleaning. It is a new drive. Entire system is a new one. There are only 4 weeks since he was delivered and installed. It is hosted in a seriuos collocation company from Canada. They have special climatized rooms for servers, with air conditiones, dust filters, etc, all features. > -- Or the tape drive is buggy. Is there any way to check this? I was never using tape drives before in my life. > I see that the drive is an OnStream. Haven't there been significant > problems reported on this list, with those? I'm a new user of Amanda so I'm not subscribed for a long time. Maybe another OnStreaem user could tell me. > For remote backups I prefer to keep a local mirror, using ssh and > rsync, and back up from that. There is no remote backup: only I work remotelly, but backup is performed on the same machine. There is no others machines that I do backup for. Only for that server from that server. > When tape drive problems develop, and they usually do sooner or > later, I'm not depending on all too often ill-trained and overworked > ISP sysadmins to do my troubleshooting for me. I am the system administrator of that server, but as I said, I work remotelly. Peoples on that company can help me but I must told them what to do first. They already check twice and told me there is a drive in the tape. This is all I know. > Another option might be changing colocation providers. I don't thinks this is related to my problem. Since I'm root for that server I have to handle this problem somehow, but first I need to figure out what's really going on. Thanks, Radu Filip -- Radu Filip Network Administrator @ Technical University of Iasi [EMAIL PROTECTED] Information Technology and Communication Center http://socrate.tuiasi.ro/ [EMAIL PROTECTED] | http://www.ccti.tuiasi.ro/
changerfile
Hi all, I am setting up the amanda.conf file, and have come to the point where I am setting up the tape device. I am setting the tpchanger to "chg-multi" so I can take advantage of the 2 DLTs I have attached to the host. The DLTs are /dev/(n)st0 and /dev/(n)st1. In reading the TAPE.CHANGERS file I found out the tapedev varible is ignored as is the changerdev. So the question arises as to how to configure the changer.conf file. Here were my thoughts, and advice is more than welcome: # cat chg-multi.conf multieject 0 gravity 1 needeject 1 ejectdelay 0 statefile /var/log/amanda/DailySet1/changer-status firstslot 1 lastslot 2 slot 1 /dev/nst0 slot 2 /dev/nst1 Thanks. Find the best deals on the web at AltaVista Shopping! http://www.shopping.altavista.com
changerfile
Hi all, I am setting up the amanda.conf file, and have come to the point where I am setting up the tape device. I am setting the tpchanger to "chg-multi" so I can take advantage of the 2 DLTs I have attached to the host. The DLTs are /dev/(n)st0 and /dev/(n)st1. In reading the TAPE.CHANGERS file I found out the tapedev varible is ignored as is the changerdev. So the question arises as to how to configure the changer.conf file. Here were my thoughts, and advice is more than welcome: # cat chg-multi.conf multieject 0 gravity 1 needeject 1 ejectdelay 0 statefile /var/log/amanda/DailySet1/changer-status firstslot 1 lastslot 2 slot 1 /dev/nst0 slot 2 /dev/nst1 Thanks. Find the best deals on the web at AltaVista Shopping! http://www.shopping.altavista.com
Re: Please help!!
Dan Wilder <[EMAIL PROTECTED]> writes: [...] > I see that the drive is an OnStream. Haven't there been > significant problems reported on this list, with those? According to the SCSI newsgroups they are out of buisness. Johannes Niess
Re: Please help!!
On Tue, Mar 27, 2001 at 06:55:46PM +0200, Johannes Niess wrote: > Dan Wilder <[EMAIL PROTECTED]> writes: > > [...] > > > I see that the drive is an OnStream. Haven't there been > > significant problems reported on this list, with those? > > According to the SCSI newsgroups they are out of buisness. > > Johannes Niess That's a significant problem! -- Dan Wilder <[EMAIL PROTECTED]>
Strange error: amlabel: no label found ...
Several months ago I set up Amanda under Slackware Linux 7.0 (now using kernel 2.41) and had everything running fine, without issues. A few days ago, I started getting messages saying Amanda was unable to run.. -- ERROR: /dev/st0: not an amanda tape (expecting a new tape) -- So I tried re-labelling several new tapes using AMLABEL, but it did failed with the following error:. -- root@monitor:/usr/local/sbin# su amanda -c './amlabel amanda.conf w2obackup01' rewinding, reading label, not an amanda tape rewinding, writing label w2obackup01, checking label amlabel: no label found, are you sure /dev/st0 is non-rewinding? -- Let me re-iterate, the configuration has not been changed since the day I installed it and had it working for 3 months. Now this error occurs, and I'm at the end of my rope. I've checked the archives to no avail. I am using the latest version of Amanda. I tried switching the device to non-rewinding (/dev/nst0 as opposed to /dev/st0) and it errors out telling me the tape is write-protected - which it is not. If anyone can point me in the right direction, I'd really appreciate it. -- Steve.
Re: Strange error: amlabel: no label found ...
>ERROR: /dev/st0: not an amanda tape (expecting a new tape) That's the wrong device name. It must be /dev/nst0 to get the no-rewind semantics. >Let me re-iterate, the configuration has not been changed since the day I >installed it and had it working for 3 months. ... Then you've been damned lucky. >... I tried switching the device to >non-rewinding (/dev/nst0 as opposed to /dev/st0) and it errors out telling >me the tape is write-protected - which it is not. Are you sure the permissions on /dev/nst0 allow read/write access to the Amanda user? Put another way, make sure they are the same as the ones on /dev/st0, since that sort of works. If that's not it, then my guess would be a hardware problem. Sorry. You might try power cycling the drive, etc. >-- Steve. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: changerfile
>Here were my thoughts, and advice is more than welcome: ># cat chg-multi.conf >... Looks OK to me. I might have used firstslot 0, lastslot 1 and slot 0, slot 1, but that's just the C programmer in me :-). Counting from 1 worked for Fortran :-). John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: ./configure on AIX 4.3.3
>I'm getting the following error running ./configure as root: First, most people recommend configuring and building as non-root just in case the process goes weird. The install step is usually the only thing that has to be done as root. ># ./configure >... >configure: error: *** --with-user=USER is missing Please read the documentation that came with Amanda (docs/INSTALL in particular) and http://www.backupcentral.com/amanda.html. They cover this most basic question and get you started on the ton of other things you're going to need to make decisions about before using Amanda. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
amrestore/tar problem
I'm trying to do a full level 0 restore of a directory on our largest backed up partition. Amanda (2.4.1p1, BSDI 4.1, Seagate DDS4 drive) is using gtar to back it up because I have to exclude a bunch of stuff. The problems I've had are as follows. I successfully used the amrecover technique to have Amanda restore off of the level 0 and all of the subsequent days, however I could tell that not everything got restored. Trying to use "amrestore -p .. | tar ivf -" failed, but now I realize that was because it was the default tar and not gtar (oops). However, after reading the gtar info pages, it seems that their interactive mechanism is not very easy to manipulate. e.g. restore[25]# amrestore -p /dev/nrst0 lou /dev/sd0g | /usr/local/bin/tar xwvf - amrestore: 0: skipping start of tape: date 20010313 label VOL12 amrestore: 1: skipping amrestore: 2: skipping amrestore: 3: skipping amrestore: 4: skipping amrestore: 5: skipping amrestore: 6: skipping amrestore: 7: skipping amrestore: 8: skipping amrestore: 9: skipping amrestore: 10: skipping amrestore: 11: restoring lou_dev_sd0g.20010313.0 extract 07253617211/./?q My only other option was to do a complete image restore using amrestore and then use gtar to untar the entire image. Am I missing something? As an aside, is there a way to force Amanda to accept two disklist entries for the same partition, but with different options? I tried once and it complained, but I'd like to backup "/logs" on one entry and everything else on the other. The tape can't back up everything (it's a DDS4 tape and the partition is 50Gb). Thanks! -- ~ Doug Silver 619 235-2665 Quantified Systems, Inc ~
Re: disk offline
>FAILURE AND STRANGE DUMP SUMMARY: > kascha sdb2 lev 0 FAILED [disk sdb2 offline on kascha?] > kascha sdb1 lev 0 FAILED [disk sdb1 offline on kascha?] > kascha sda1 lev 0 FAILED [disk sda1 offline on kascha?] > >Since these are my boot disk and /usr disk they arnt off >line. That's a generic statement for some kind of access problem. Running amcheck is always the first thing to do in cases like this. It reports much more specific information. If that doesn't help, look at /tmp/amanda/sendsize*debug on kascha. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Strange error: amlabel: no label found ...
On Tue, 27 Mar 2001, John R. Jackson wrote: > Are you sure the permissions on /dev/nst0 allow read/write access to > the Amanda user? Put another way, make sure they are the same as the > ones on /dev/st0, since that sort of works. Thanks for the info John. You were right, it was a permissions problem with /dev/nst0. I had read, but no write. What bothers me is that I made no configuration changes, and no changes to the system that would cause this problem to develop. It worked fine using /dev/st0 for 3 months, then it stops - and will only work using /dev/nst0. Very odd. Steve.
Re: finding disks
OK, When I changed the disklist on the server to the mount points instead of the devices (eg. /usr/local instead of hda6 or /dev/hda6), it works fine. So first of all, thanks a LOT! Is the reason for this: a) because the computer we just fixed is running RedHat 7.0 as opposed to Redhat 6.1 on the other b) because somehow when I compiled the client software I told it to use gnu-tar instead of dump (compression is being done on the client side) c) None of the above. I'd like to know because I would like to keep the conventions consistent if that's possible, and it looks bad to have a disklist where one linux box has drive labels listed and the other has mount points. Thanks for your efforts John, much *much* appreciated. -Darrel On Mon, 26 Mar 2001, you wrote: > >Yes there is, and it is /dev/hda6, and amanda uses the default "/dev/" > > I'm not sure what you mean by "amanda uses the default". > > Are you using the system dump program or GNU tar for these disks? Is > hda6 (in some form :-) listed in /etc/fstab? > > What happens here is Amanda takes any of three forms in the disklist file > (/some/mount/point, hda6 or /dev/hda6) and converts that into whatever > is needed. For dump it is the disk name (/dev/hda6). For GNU tar it > would be the mount point. I'm guessing something is going wrong with > that conversion. > > >I think the reason this machine is failing is because the last guy tried to > >upgrade the client-side software on it to 2.4.2, but he could never get it to > >work, so i inherited his problem. > > If you're running a new version of Linux that uses /proc/mounts in > preference to /etc/fstab, you'll have to get a recent version of Amanda > to get the patches that make it aware of that. > > And unless you just happen to see the problem, to debug this much further > you'll have to be able to regenerate some form of client side software, > either what you're running or go ahead and get 2.4.2p1 and try it again. > > The first thing I'd do is: > > cd client-src > make getfsent > ./getfsent hda6 > > That will try several standard Amanda conversions plus the one(s) you > put on the command line and log the results. > > >-darrel > > John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
amrecover: Unexpected server end of file
Yes I know this is a popular error message.
# amrecover -C Weekly -s clark -t clark -d /dev/nst0
AMRECOVER Version 2.4.2p1. Contacting server on clark ...
amrecover: Unexpected server end of file
In this case the command was executed on the host "clark"
clark happens to be the amanda server, tape server and index server.
clark is also a client. However I get the same error when this command
is executed from the other clients.
I have been reading hundreds of posts on this, as well as the
suspected DNS problem outlined in the FAQ.
Often the response to these posts is,
"What does your /tmp/amanda/amindexd*debug file say?"
This is my fundamental problem. I don't have a amindexd*debug file.
I have all the other debug files:
amandad.debug amrecover.debug killpgrp.debugsendsize.debug
amcheck.debug amtrmidx.debug selfcheck.debug
amlabel.debug amtrmlog.debug sendbackup.debug
Can anyone help me to start logging to a amindexd*debug file?
Then I can start to trouble shoot the real problem
"amrecover: Unexpected server end of file"
phbrannigan
Here is my environment info:
OS = RedHat 7.0
Amanda = amanda-2.4.2p1
built with:
./configure --with-user=amanda --with-group=disk
# netstat -a | grep am
tcp0 0 *:amidxtape *:*
LISTEN
tcp0 0 *:amandaidx *:*
LISTEN
udp0 0 *:amanda*:*
xinetd.d info:
service amanda
{
socket_type = dgram
protocol = udp
wait = yes
user = amanda
group = disk
server = /usr/local/libexec/amandad
disable = no
}
service amandaidx
{
socket_type = stream
protocol= tcp
wait= yes
user= operator
group = disk
server = /usr/lib/amanda/amindexd
disable = no
}
service amidxtape
{
socket_type = stream
protocol= tcp
wait= no
user= operator
group = disk
server = /usr/lib/amanda/amidxtaped
disable = no
}
disklist file:
...
#
# clark
#
clark /dev/hda1 linux0
amanda.conf file
...
define dumptype linux0 {
comment "Linux dump level 0"
program "DUMP"
dumpcycle 0
index yes
}
...
begin:vcard
n:Brannigan;Paul
tel;fax:303-245-1025
tel;work:303-245-1045
x-mozilla-html:TRUE
adr:;;3434 47th St.;Boulder;Colorado;80301;USA
version:2.1
email;internet:[EMAIL PROTECTED]
title:Support Engineer
x-mozilla-cpt:;0
fn:Paul Brannigan
end:vcard
Re: amrestore/tar problem
>I'm trying to do a full level 0 restore of a directory on our largest >backed up partition. ... >I successfully used the amrecover technique to have Amanda restore off of >the level 0 and all of the subsequent days, however I could tell that not >everything got restored. ... Amrecover is not really set up for full restores. Those often (as you discovered) need other options to the restore program. >... However, after reading the gtar info pages, it seems that >their interactive mechanism is not very easy to manipulate. This came up here recently. Because I don't know much about GNU tar, it did not get covered well enough in "the chapter". I'm reviewing that at the moment and will try to improve the text. Not that it helps you at the moment ... :-) >restore[25]# amrestore -p /dev/nrst0 lou /dev/sd0g | /usr/local/bin/tar xwvf - >... >amrestore: 11: restoring lou_dev_sd0g.20010313.0 >extract 07253617211/./?q Uh, oh. That big number on the front may spell serious trouble. What version of GNU tar are you using? Pretty much everything up to 1.13.17 had bad problems (as has been discussed on this list numerous times). Do you have indexing turned on? Do the index files look like the above, i.e. have a big number at the front of every line? I don't know that there is any way out of this either. I don't recall what the problem was with GNU tar or whether it was something that could be "reversed". Sorry. I'm sure that's not exactly going to be the bright point of your day. If you gather some more information, such as poking around in the index files or generating new catalogues (gtar -t) of the dumps, we might be able to come up with a solution. >As an aside, is there a way to force Amanda to accept two disklist entries >for the same partition, but with different options? ... Since you're using GNU tar, you can use "logs" for one and "logs/." for the other. >Doug Silver John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: amrecover: Unexpected server end of file
>Often the response to these posts is, >"What does your /tmp/amanda/amindexd*debug file say?" > >This is my fundamental problem. I don't have a amindexd*debug file. >I have all the other debug files: >... The amindexd is dieing right away, before it can even open the debug file. What happens if you do this: # su operator -c /usr/lib/amanda/amindexd It should die right away with a message something like this: amindexd: getpeername: Socket operation on non-socket but it should also create the amindexd*debug file. >phbrannigan John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: amrestore/tar problem
Hi John -
gtar version:
/usr/local/bin/tar --version
tar (GNU tar) 1.13
Oh well, I'm currently doing a 'gtar -xvf' on the entire image, and there
is that large number in front of everything, but it seems to be restoring
files properly. However I just noticed that it is restoring files I
thought were being excluded, so perhaps that's due to this version of
tar?
07247144107/./logs/smalltest (from current job process)
As for the duplicate partitions, that's not working, here's my entries
from amanda.conf and disklist:
define dumptype comp-user {
comment "Non-root partitions on reasonably fast machines"
options compress-fast
priority medium
index yes
program "GNUTAR"
exclude "./logs/"
}
define dumptype comp-logs {
comment "Amanda dump partition"
options compress-fast
priority low
index yes
program "GNUTAR"
exclude "./home"
and in disklist:
lou /dev/sd0g comp-user #/export exclude ./logs
lou /dev/sd0g comp-logs #/export just ./logs
daily[47]# amcheck -c daily
"disklist", line 21: duplicate disk record, previous on line 20
amcheck-clients: could not load "disklist"
(brought to you by Amanda 2.4.1p1)
I'll update gtar -- I had previously read not to update, but it sounds
like gtar+Amanda is now fixed in the current versions. Do I need to
update Amanda too (I know, loaded question!).
Thanks for the quick reply!
-doug
On Tue, 27 Mar 2001, John R. Jackson wrote:
> >I'm trying to do a full level 0 restore of a directory on our largest
> >backed up partition. ...
> >I successfully used the amrecover technique to have Amanda restore off of
> >the level 0 and all of the subsequent days, however I could tell that not
> >everything got restored. ...
>
> Amrecover is not really set up for full restores. Those often (as you
> discovered) need other options to the restore program.
>
> >... However, after reading the gtar info pages, it seems that
> >their interactive mechanism is not very easy to manipulate.
>
> This came up here recently. Because I don't know much about GNU tar,
> it did not get covered well enough in "the chapter". I'm reviewing that
> at the moment and will try to improve the text.
>
> Not that it helps you at the moment ... :-)
>
> >restore[25]# amrestore -p /dev/nrst0 lou /dev/sd0g | /usr/local/bin/tar xwvf -
> >...
> >amrestore: 11: restoring lou_dev_sd0g.20010313.0
> >extract 07253617211/./?q
>
> Uh, oh. That big number on the front may spell serious trouble.
>
> What version of GNU tar are you using? Pretty much everything up to
> 1.13.17 had bad problems (as has been discussed on this list numerous
> times).
>
> Do you have indexing turned on? Do the index files look like the above,
> i.e. have a big number at the front of every line?
>
> I don't know that there is any way out of this either. I don't recall
> what the problem was with GNU tar or whether it was something that could
> be "reversed".
>
> Sorry. I'm sure that's not exactly going to be the bright point of
> your day.
>
> If you gather some more information, such as poking around in the index
> files or generating new catalogues (gtar -t) of the dumps, we might be
> able to come up with a solution.
>
> >As an aside, is there a way to force Amanda to accept two disklist entries
> >for the same partition, but with different options? ...
>
> Since you're using GNU tar, you can use "logs" for one and "logs/."
> for the other.
>
> >Doug Silver
>
> John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
>
--
~
Doug Silver
619 235-2665
Quantified Systems, Inc
~
Re: amrecover: Unexpected server end of file
> > Here is what I get after I run # su operator -c /usr/lib/amanda/amindexd > > amindexd: open debug file "/tmp/amanda/amindexd.debug": Permission denied > > Ok Now I opened up permissions on /tmp/amanda. I re ran the command with the following results # su operator -c /usr/lib/amanda/amindexd amindexd: getpeername: Socket operation on non-socket Indeed. There is now a amindexd.debug file We are getting there... Now after I run amrecover I get this: [root@clark /root]# amrecover -C Weekly -s clark -t clark -d /dev/nst0 AMRECOVER Version 2.4.2p1. Contacting server on clark ... 220 clark AMANDA index server (2.4.1p1) ready. 500 Access not allowed: [access as operator not allowed from [EMAIL PROTECTED]] Here is my new amindexd.debug file: < 220 clark AMANDA index server (2.4.1p1) ready. > SECURITY USER root bsd security: remote host clark.xxx.com user root local user operator check failed: [access as operator not allowed from [EMAIL PROTECTED]] < 500 Access not allowed: [access as operator not allowed from [EMAIL PROTECTED]] < 200 Good bye. amindexd: pid 2973 finish time Tue Mar 27 13:41:45 2001 It is looking like I should adjust my /etc/xinetd.d/amandaidx and / or amidxtape file(s) begin:vcard n:Brannigan;Paul tel;fax:303-245-1025 tel;work:303-245-1045 x-mozilla-html:TRUE adr:;;3434 47th St.;Boulder;Colorado;80301;USA version:2.1 email;internet:[EMAIL PROTECTED] title:Support Engineer x-mozilla-cpt:;0 fn:Paul Brannigan end:vcard
Re: two dumps in one day
>I have a directory that I must backup sometimes more than once a day... the >problem is that when I try to amrecover it I only get the file list of the >last dump I made ... what can I do to correct this ? I can think of two things. You could take over the development project to make Amanda use time stamps instead of datestamps. Oh, well. I thought I'd ask :-). Or you could just "know" that amrecover lies and whatever tape it tells you to load, go back to your reports and load the "right" tape. The amrestore than amidxtaped calls searches for the image by name anyway. It doesn't check that you loaded the tape amrecover told you to. >-Miguel John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: amrecover: Unexpected server end of file
"John R. Jackson" wrote: > > The amindexd is dieing right away, before it can even open the debug > file. What happens if you do this: > > # su operator -c /usr/lib/amanda/amindexd > > It should die right away with a message something like this: > > amindexd: getpeername: Socket operation on non-socket > > but it should also create the amindexd*debug file. > First of all, Thank you John for responding. I am enjoying your work and Alexandre's as I read and re-read the O'Reilly book. I hope you get a big piece of my $39.95 ;-) Here is what I get after I run # su operator -c /usr/lib/amanda/amindexd amindexd: open debug file "/tmp/amanda/amindexd.debug": Permission denied phbrannigan begin:vcard n:Brannigan;Paul tel;fax:303-245-1025 tel;work:303-245-1045 x-mozilla-html:TRUE adr:;;3434 47th St.;Boulder;Colorado;80301;USA version:2.1 email;internet:[EMAIL PROTECTED] title:Support Engineer x-mozilla-cpt:;0 fn:Paul Brannigan end:vcard
RE: amrecover: Unexpected server end of file
I just ran into this. On the tape server machine you need to add clark.xxx.com root to your .amandahosts file You also need to verify that the user that runs the service is setup correctly. I say this because in your first post you have both amanda and operator as the users for your services. Also in this last post you mention [EMAIL PROTECTED] James -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Paul Brannigan Sent: Tuesday, March 27, 2001 12:49 PM To: amanda group Subject: Re: amrecover: Unexpected server end of file > > Here is what I get after I run # su operator -c /usr/lib/amanda/amindexd > > amindexd: open debug file "/tmp/amanda/amindexd.debug": Permission denied > > Ok Now I opened up permissions on /tmp/amanda. I re ran the command with the following results # su operator -c /usr/lib/amanda/amindexd amindexd: getpeername: Socket operation on non-socket Indeed. There is now a amindexd.debug file We are getting there... Now after I run amrecover I get this: [root@clark /root]# amrecover -C Weekly -s clark -t clark -d /dev/nst0 AMRECOVER Version 2.4.2p1. Contacting server on clark ... 220 clark AMANDA index server (2.4.1p1) ready. 500 Access not allowed: [access as operator not allowed from [EMAIL PROTECTED]] Here is my new amindexd.debug file: < 220 clark AMANDA index server (2.4.1p1) ready. > SECURITY USER root bsd security: remote host clark.xxx.com user root local user operator check failed: [access as operator not allowed from [EMAIL PROTECTED]] < 500 Access not allowed: [access as operator not allowed from [EMAIL PROTECTED]] < 200 Good bye. amindexd: pid 2973 finish time Tue Mar 27 13:41:45 2001 It is looking like I should adjust my /etc/xinetd.d/amandaidx and / or amidxtape file(s)
Re: amrestore/tar problem
>Oh well, I'm currently doing a 'gtar -xvf' on the entire image, and there
>is that large number in front of everything, but it seems to be restoring
>files properly. ...
Really? They are not going into a directory with that big number on
the front?
Whatever. If it's working, you win :-).
>However I just noticed that it is restoring files I
>thought were being excluded, so perhaps that's due to this version of
>tar?
That might be the case.
>As for the duplicate partitions, that's not working ...
>and in disklist:
>lou /dev/sd0g comp-user #/export exclude ./logs
>lou /dev/sd0g comp-logs #/export just ./logs
You can't do what you want by listing the disk name (/dev/sd0g).
You need to list the mount point, and then you can put a "/." on the
tail end of one of them. For instance, if /dev/sd0g is mounted on /var,
then you could do:
lou /var comp-user #/export exclude ./logs
lou /var/. comp-logs #/export just ./logs
If you don't do anything special, Amanda will think these are new disks.
You could go into your curinfo directory and rename _dev_sd0g to the
appropriate mount point name ('/' becomes '_'). Ditto for the index area.
>I'll update gtar -- I had previously read not to update, but it sounds
>like gtar+Amanda is now fixed in the current versions. Do I need to
>update Amanda too (I know, loaded question!).
You **always** need to update Amanda :-).
No, you don't really need to. Certainly not to match GNU tar. All the
problems were in GNU tar itself. Amanda had nothing to do with it,
other than trying to use the features.
>-doug
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
unsubscribe
unsubscribe
Re: finding disks
>When I changed the disklist on the server to the mount points instead of the >devices (eg. /usr/local instead of hda6 or /dev/hda6), it works fine. Great! >Is the reason for this: >a) because the computer we just fixed is running RedHat 7.0 as opposed to >Redhat 6.1 on the other This is my best guess. They obviously changed some of the system calls for looking up mount point information, but since I don't run Linux, this is just guesswork on my part. >... it looks bad to have a disklist where one linux box has >drive labels listed and the other has mount points. Personally, I prefer mount points instead of disk names anyway. They are more likely to be persistent. But that's just my own opinion. >-Darrel John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: finding disks
> >When I changed the disklist on the server to the mount points instead of the > >devices (eg. /usr/local instead of hda6 or /dev/hda6), it works fine. > > Great! > > >Is the reason for this: > >a) because the computer we just fixed is running RedHat 7.0 as opposed to > >Redhat 6.1 on the other > this come probably from the new format for the /etc/fstab where disk disk names are not specified LABEL=/tmp /tmpext2defaults 1 2 LABEL=/usr /usrext2defaults1 2 > > This is my best guess. They obviously changed some of the system calls > for looking up mount point information, but since I don't run Linux, > this is just guesswork on my part. > > >... it looks bad to have a disklist where one linux box has > >drive labels listed and the other has mount points. > > Personally, I prefer mount points instead of disk names anyway. They > are more likely to be persistent. But that's just my own opinion. > > >-Darrel > > John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Exabyte Mammoth 2 users take note
As of firmware upgrade 8ck3v03a (8ch3v03a for HVD drives), Exabyte have fixed a major problem with premature EOT errors. I have just upgraded and was able to do a full level 0 dump for the first time without getting inconsistent EOTs. So if you're getting this kind of error, it may be worth a trip to http://www.exabyte.com/support/online/downloads/firmware_tape.cfm Regards. -- +-+---+ | Ross Johnson| | "Come down off the cross | Management & Technology |___| We can use the wood" - Tom Waits | Building 11 | | University of Canberra | eMail: [EMAIL PROTECTED] | ACT2601 | WWW: http://public.ise.canberra.edu.au/~rpj/ | AUSTRALIA | +-+
Re: two dumps in one day
* John R. Jackson <[EMAIL PROTECTED]> (Tue, Mar 27, 2001 at 04:01:42PM -0500) > Or you could just "know" that amrecover lies and whatever tape it > tells you to load, go back to your reports and load the "right" tape. > The amrestore than amidxtaped calls searches for the image by name anyway. > It doesn't check that you loaded the tape amrecover told you to. So if the morning tape has the disk I need as file image 3 and the evening tape (that amrecover expects) has the disk as file image 94 it will simply fsf until it finds the named image (image 3 in this case) in stead of blindly fsf-ing to image 94 ? Now that is a handy feature .. Kind regards, -- Gerhard den Hollander Phone +31-10.280.1515 Technical Support Jason Geosystems BV Fax +31-10.280.1511 (When calling please note: we are in GMT+1) [EMAIL PROTECTED] POBox 1573 visit us at http://www.jasongeo.com 3000 BN Rotterdam JASON...#1 in Reservoir CharacterizationThe Netherlands This e-mail and any attachment is/are intended solely for the named addressee(s) and may contain information that is confidential and privileged. If you are not the intended recipient, we request that you do not disseminate, forward, distribute or copy this e-mail message. If you have received this e-mail message in error, please notify us immediately by telephone and destroy the original message.
