subscribe
subscribe -- This transmission is for the intended addressee only and is confidential information. If you have received this transmission in error, please delete it and notify the sender. The contents of this e-mail are the opinion of the writer only and are not endorsed by the Mincom Group of companies unless expressly stated otherwise.
problems with tape drive?
Hi all,
I'm having some grief with a tape drive that starts backing up, but gets an
error and terminates... In /var/log/messages I see:
Aug 29 22:15:00 osiris kernel: PCI: Enabling device 00:0f.0 (0006 - 0007)
Aug 29 22:15:00 osiris kernel: PCI: Enabling device 00:0f.1 (0006 - 0007)
Aug 29 22:15:00 osiris kernel: scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA
DRIVER, Rev 6.2.4
Aug 29 22:15:00 osiris kernel: Adaptec aic7899 Ultra160 SCSI
adapter
Aug 29 22:15:00 osiris kernel: aic7899: Ultra160 Wide Channel A,
SCSI Id=7, 32/253 SCBs
Aug 29 22:15:00 osiris kernel:
Aug 29 22:15:00 osiris kernel: scsi1 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA
DRIVER, Rev 6.2.4
Aug 29 22:15:00 osiris kernel: Adaptec aic7899 Ultra160 SCSI
adapter
Aug 29 22:15:00 osiris kernel: aic7899: Ultra160 Wide Channel B,
SCSI Id=7, 32/253 SCBs
Aug 29 22:15:00 osiris kernel:
Aug 29 22:15:15 osiris kernel: Vendor: SONY Model: SDT-1
Rev: 0110
Aug 29 22:15:15 osiris kernel: Type: Sequential-Access
ANSI SCSI revision: 02
Aug 29 22:15:15 osiris kernel: (scsi0:A:2): 40.000MB/s transfers (20.000MHz,
offset 15, 16bit)
Aug 29 22:15:22 osiris kernel: st: Version 20020205, bufsize 32768, wrt
30720, max init. bufs 4, s/g segs 16
Aug 29 22:15:22 osiris kernel: Attached scsi tape st0 at scsi0, channel 0,
id 2, lun 0
Aug 29 22:15:22 osiris kernel: st0: Block limits 1 - 16777215 bytes.
Aug 30 01:46:03 osiris kernel: st0: Error on write filemark.
Aug 30 02:00:00 osiris kernel: scsi : 0 hosts left.
Aug 30 02:00:00 osiris kernel: st: Unloaded.
And in the backup report:
These dumps were to tape eng-au002.
*** A TAPE ERROR OCCURRED: [[writing filemark: Input/output error]].
Some dumps may have been left in the holding disk.
Run amflush to flush them to tape.
The next tape Amanda expects to use is: eng-au003.
FAILURE AND STRANGE DUMP SUMMARY:
osiris /dev/hda3 lev 0 FAILED [out of tape]
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:02
Run Time (hrs:min) 0:14
Dump Time (hrs:min)0:11 0:00 0:11
Output Size (meg) 298.64.7 294.0
Original Size (meg) 889.0 19.5 869.5
Avg Compressed Size (%)33.6 23.9 33.8 (level:#disks ...)
Filesystems Dumped3 1 2 (1:2)
Avg Dump Rate (k/s) 447.8 650.0 445.7
Tape Time (hrs:min)0:00 0:00 0:00
Tape Size (meg) 0.00.00.0
Tape Used (%) 0.00.00.0
Filesystems Taped 0 0 0
Avg Tp Write Rate (k/s) -- -- --
NOTES:
planner: Full dump of osiris:/dev/hda3 promoted from 2 days ahead.
planner: Full dump of osiris:/dev/hda1 promoted from 2 days ahead.
taper: tape eng-au002 kb 0 fm 0 writing filemark: Input/output error
driver: going into degraded mode because of tape error.
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -
osiris /dev/hda1 1 899352 39.2 0:13 26.3 N/A N/A
osiris /dev/hda3 0 19943 4768 23.9 0:07 650.0 N/A N/A
osiris /dev/hdb1 1 889470 300672 33.8 11:02 454.1 N/A N/A
(brought to you by Amanda version 2.4.2p2)
--
The /dev/hdb1 file is in the holding disk, but if I try and flush it, it'll
fail again.
in /var/log/amanda/amdump.1 (snipped):
driver: result time 140.611 from dumper0: DONE 00-1 19943 4768 7 [sec
7.335 kb 4768 kps 650.0 orig-kb 19943]
driver: finished-cmd time 140.647 dumper0 dumped osiris:/dev/hda3
driver: send-cmd time 140.647 to taper: FILE-WRITE 00-2
/backup/20020902/osiris._dev_hda3.0 osiris /dev/hda3 0 20020902
driver: state time 140.647 free kps: 3400 space: 27266580 taper: writing
idle-dumpers: 4 qlen tapeq: 0 runq: 2 roomq: 0 wakeup: 7 driver-idle:
start-wait
driver: interface-state time 140.647 if : free 2000 if LE0: free 400 if
LOCAL: free 1000
driver: hdisk-state time 140.647 hdisk 0: free 27266580 dumpers 0
taper: writing end marker. [eng-au002 ERR kb 0 fm 0]
driver: result time 140.654 from taper: TAPE-ERROR 00-2 [writing
filemark: Input/output error]
driver: finished-cmd time 140.654 taper wrote osiris:/dev/hda3
dump of driver schedule before start degraded mode:
osiris /dev/hda1 lv 0 t 180 s 295648 p 0
osiris /dev/hdb1 lv 1 t 638 s 310080 p 2
dump of driver schedule after start degraded mode:
osiris /dev/hdb1 lv 1 t 638 s 310080 p 2
osiris /dev/hda1 lv 1 t 8 s 342 p 0
driver: state time 140.654 free kps: 3400 space: 27266580 taper: DOWN
idle-dumpers: 4 qlen
Re: Testing tapes
I think I'm getting closer to the problem. First off, it seems that ide-tape doesn't work properly with the Colorado drives. I haven't yet had time to test, but I'll install ide-scsi when I next get a chance. Does anyone know of a reference as to the differences between ide-tape/ide and st/ide-scsi/ide? Regards, Brian Jonnes -- Init Systems - Linux consulting 031 767-0139082 769-2320[EMAIL PROTECTED]
Win 2k error with amcheck
Hi, Trying to backup a Win 2k server this is the message i receive from amcheck: Amanda Tape Server Host Check - Holding disk /data/backup: 13496396 KB disk space available, that's plenty ERROR: /dev/nst1: rewinding tape: No medium found (expecting tape SCJM01 or a new tape) NOTE: skipping tape-writable test NOTE: info dir /var/lib/amanda/daily0/curinfo/localhost/_var: does not exist NOTE: info dir /var/lib/amanda/daily0/curinfo/sigfipd1: does not exist NOTE: index dir /var/lib/amanda/daily0/index/sigfipd1: does not exist NOTE: info dir /var/lib/amanda/daily0/curinfo/sfin-ux1: does not exist NOTE: info dir /var/lib/amanda/daily0/curinfo/sfin-ux2: does not exist Server check took 30.379 seconds Amanda Backup Client Hosts Check ERROR: sigfipd1 NAK: execute access to /usr/amanda/libexec/selfcheck denied Client check: 5 hosts checked in 0.791 seconds, 1 problem found (brought to you by Amanda 2.4.2p2) When i look at the server sigfipd1 there is no file /usr/amanda/libexec/selfcheck. I've got and installed amanda-clients-2.5.0-20010628.zip from sourceforge. Could someone help me ? ___ Do You Yahoo!? -- Une adresse yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com
What does -1 mean in disklist
What does the -1 mean in the following disklist line: www /home2 nocomp-user -1 local Thanks in advance Michael Martinez System Administrator Information Systems and Technology Management CSREES - United States Department of Agriculture (202) 720-6223
Amanda-2.4.3b4 and tar exclude lists working?
Hello, I just installed and configured amanda-2.4.3b4-20020829 on a Linux box with an ecrix tape library and I might be stumbling on some bug and/or feature: relative path exclude list don't seem to be used at all... Perusing in the posts for 2.4.3b4 announcement from Jean-Louis I see that this version is supposed to have this fixed... Is this really the case? I can provide debug files on demand. My setup: amandad: version 2.4.3b4-20020829 amandad: build: VERSION=Amanda-2.4.3b4-20020829 amandad:BUILT_DATE=Sun Sep 1 15:21:17 EDT 2002 amandad:BUILT_MACH=Linux blade.bic.mni.mcgill.ca 2.4.9-31 #1 Tue Feb 26 06:53:37 EST 2002 i686 unknown amandad:CC=gcc amandad:CONFIGURE_COMMAND='./configure' '--prefix=/opt/amanda_vxa' '--with-user=amanda' '--with-group=disk' '--with-testing=vxa' '--with-tcpportrange=16384,16896' '--with-udpportrange=700,731' '--with-tape-device=/dev/nst0' '--with-changer-device=/dev/changer' '--with-tape-server=blade' '--with-index-server=blade' '--with-config=vxa' regards, jf -- Cats are intended to teach us that not everything in nature has a function.
RE: Testing tapes
Just make a backup of a few large files, recover them into a temporary directory, and compare the recoverds with the originals using cmp -l. Michael Martinez System Administrator Information Systems and Technology Management CSREES - United States Department of Agriculture (202) 720-6223 -Original Message- From: Dietmar Goldbeck [mailto:[EMAIL PROTECTED]] Sent: Saturday, August 31, 2002 10:20 AM To: Brian Jonnes Cc: [EMAIL PROTECTED] Subject: Re: Testing tapes On Sat, Aug 31, 2002 at 01:45:44PM +0200, Brian Jonnes wrote: Hi, I think I have a faulty tape or two. What is the best recommended way of testing this? Generate a file from /dev/urandom, write it to the tape and md5sum it? If you use software compression with Amanda, one easy way would be amrecover -c /dev/tape gzip -tv *.? This checks the internal gzip CRC on all files. You could also run Amanda without tape, compute the md5sum of all files on the holding disk, flush them and then recover and compare md5. I personally would not just write one large file, because the tape might have some special problem ocurring with Amanda (writing lots of file marks, writing 32k blocks etc.) I always used Amanda itself and checked _all_ gzip CRC. When testing a new Amanda server/new tape drive i also do some real restores on to some spare disk and compare m5sums of the original tree and the restored tree. Also, what is the expected lifetime for Travan 4 tapes (each used once a week)? When should I retire them? I don't have experience with travan. My experience with several DDS and DLT tape drives (and hundreds of tapes) suggests that problems with more than _only_ _one_ tape are probably problems of the drive :-(( -- Alles Gute / best wishes Dietmar GoldbeckE-Mail: [EMAIL PROTECTED] Reporter (to Mahatma Gandhi): Mr Gandhi, what do you think of Western Civilization? Gandhi: I think it would be a good idea.
Re: Backing up only certain directories?
Also Sprach Gene Heskett: On Monday 02 September 2002 21:32, Dale Clapperton (lists) wrote: Hi all Potentially stupid question.. Does AMANDA support backing up only a certain directory on a host (ie /var/log for example) or only whole partitions (ie /var) ?? Sure, but you have to use tar. Some versions of dump such as IRIX/Linux xfsdump allow directory backups which are a subset of the whole partition, but they can only do lev 0's, no incrementals. C. Chan [EMAIL PROTECTED]GPG Public Key registered at pgp.mit.edu Your Pithy Aphorism Here! Or finger [EMAIL PROTECTED]
Re: Amanda-2.4.3b4 and tar exclude lists working?
--On Tuesday, September 03, 2002 10:10:18 -0400 Jean-Francois Malouin [EMAIL PROTECTED] wrote: Hello, I just installed and configured amanda-2.4.3b4-20020829 on a Linux box with an ecrix tape library and I might be stumbling on some bug and/or feature: relative path exclude list don't seem to be used at all... Perusing in the posts for 2.4.3b4 announcement from Jean-Louis I see that this version is supposed to have this fixed... Is this really the case? I can provide debug files on demand. Do you have an exclude list properly defined in your dumptype? Are you using tar? Is the exclude list file in the top level of the directory you're trying to back up and is it in the correct format? Frank -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: What does -1 mean in disklist
On Tuesday 03 September 2002 09:41, Martinez, Michael - CSREES/ISTM wrote: What does the -1 mean in the following disklist line: www /home2 nocomp-user -1 local According to the notes in the sample disklist, its a spindle number placeholder, whatever that is. Something to do with a raid array that allows each disk/spindle to be addressed individually. A method of backup up each single disk in a raid (I think). Possibly usefull to those with raids. Untested here, no raid. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.13% setiathome rank, not too shabby for a WV hillbilly
RE: What does -1 mean in disklist
Actually, it's a performance management thing. If you have several partitions on one physical drive, you can give them all the same spindle number, and AMANDA will only pull one backup from each spindle at a time, to keep from thrashing your drives. I use this on my older firewalls (200MHz or less) to keep the backups from taking over the machine. -Original Message- From: Gene Heskett [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 03, 2002 11:29 AM To: Martinez, Michael - CSREES/ISTM; [EMAIL PROTECTED] Subject: Re: What does -1 mean in disklist On Tuesday 03 September 2002 09:41, Martinez, Michael - CSREES/ISTM wrote: What does the -1 mean in the following disklist line: www /home2 nocomp-user -1 local According to the notes in the sample disklist, its a spindle number placeholder, whatever that is. Something to do with a raid array that allows each disk/spindle to be addressed individually. A method of backup up each single disk in a raid (I think). Possibly usefull to those with raids. Untested here, no raid. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.13% setiathome rank, not too shabby for a WV hillbilly
Re: Amanda-2.4.3b4 and tar exclude lists working?
* Frank Smith ([EMAIL PROTECTED]) [20020903 11:18] thus spake:
--On Tuesday, September 03, 2002 10:10:18 -0400 Jean-Francois Malouin
[EMAIL PROTECTED] wrote:
Hello,
I just installed and configured amanda-2.4.3b4-20020829 on a Linux box
with an ecrix tape library and I might be stumbling on some bug and/or
feature: relative path exclude list don't seem to be used at all...
Perusing in the posts for 2.4.3b4 announcement from Jean-Louis I see
that this version is supposed to have this fixed... Is this really the
case? I can provide debug files on demand.
Do you have an exclude list properly defined in your dumptype?
Are you using tar?
Is the exclude list file in the top level of the directory you're trying
to back up and is it in the correct format?
I've been using amanda for a few years now and I'm fully aware of all
the quirks in setting up exclude lists. I have 3 other servers running
2.4.2p2 with relative exclude lists with tape libraries (exb-200,
adic-218 and stk-L40) with no problems whatsoever. For this one, I
decided to jump ahead with 2.4.3b4...maybe I'll go back to 2.4.2p2.
Anyways, yes, I'm using tar (GNU tar) 1.13.19.
Here are the dumptypes from amanda.conf:
---
amanda.conf
---
define dumptype global {
comment Global definitions
index yes
record yes
}
define dumptype root-tar {
global
program GNUTAR
comment root partitions dumped with tar
compress none
index
priority low
}
define dumptype high-tar-raid-epilepsy {
root-tar
comment partitions dumped with tar
priority high
exclude list .amanda-gnutar-exclude-list.txt
}
---
disklist entry
---
blade /raid/epilepsy high-tar-raid-epilepsy
---
On the host blade (amanda server and client) I created a file called
/raid/epilepsy/.amanda-gnutar-exclude-list.txt:
[root@blade]# cd /raid/epilepsy/
[root@blade]# ls -la .amanda-gnutar-exclude-list.txt
-rw---1 amanda disk 123 Sep 2 08:18
.amanda-gnutar-exclude-list.txt
---
exclude file
---
[root@blade]# cat .amanda-gnutar-exclude-list.txt
./diffusion/
./extra-TLE/
./F_MRI/
./MRI_misc/
./MT/
./neda/
./PREVIOUS/
./relaxo/
./restore/
./samson/
./thalamus/
./TLE/
Frank
--
Frank Smith[EMAIL PROTECTED]
Systems Administrator Voice: 512-374-4673
Hoover's Online Fax: 512-374-4501
Thanks!
jf
--
Cats are intended to teach us that not everything in nature has a function.
RE: What does -1 mean in disklist
muchas gracias senor Michael Martinez System Administrator Information Systems and Technology Management CSREES - United States Department of Agriculture (202) 720-6223 -Original Message- From: Gene Heskett [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 03, 2002 11:29 AM To: Martinez, Michael - CSREES/ISTM; [EMAIL PROTECTED] Subject: Re: What does -1 mean in disklist On Tuesday 03 September 2002 09:41, Martinez, Michael - CSREES/ISTM wrote: What does the -1 mean in the following disklist line: www /home2 nocomp-user -1 local According to the notes in the sample disklist, its a spindle number placeholder, whatever that is. Something to do with a raid array that allows each disk/spindle to be addressed individually. A method of backup up each single disk in a raid (I think). Possibly usefull to those with raids. Untested here, no raid. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.13% setiathome rank, not too shabby for a WV hillbilly
Label Printing. Resolution
Good Day all, I wanted to thank those of you that assisted in my struggle with label printing and Amanda. After some hand to hand combat with amreport I have managed to get the labels printing. Originally I was under the impression that amdump ran amreport for me and just wasn't outputting anything. Wrong, amreport needs to be run separately. flaw in logic number 1 After I cleared that hurdle I defined the correct lbl-templ directive and started running amreport as follows: amreport Backups -l /usr/adm/Backups/logfile name -f /dev/null -p test.ps I noticed that nothing was being created.. until today when I stumbled upon a Backupstest.ps file which contained a sexy looking label with all of my file system information in it. I jumped for joy and asked WTF did I do?. The answer is as follows: From my experimentation amreport APPENDS the text after the -p flag (in this case test.ps) to the current directory name you are in and places the file one directory above your current location. e.g. if you are in /usr/home and you run the command line mentioned above you would get a file called /usr/hometest.ps. I also noticed that if you do not include the Set name in the output name of the -p flag it behaves similarly. Hence to correctly get the labels working do the following: 1) Define the lbl-temp directive in your tapetype definition. 2) Run the amreport command as follows: amreport Set Name -l full path to log file -f /dev/null -p output file inc. set name e.g. amreport Backups -l /usr/adm/amanda/Backups/log.20020903.0 -f /dev/null -p /tmp/Backups-0903.ps This will put the file in a predictable location of /tmp and solve a lot of headaches. This is one thing that the Amanda application is really bad at.. documentation. The application is fabulous.. all it needs is someone to champion the cause of making it easy to use (through documentation).
Re: Amanda-2.4.3b4 and tar exclude lists working?
--On Tuesday, September 03, 2002 11:41:29 -0400 Jean-Francois Malouin
[EMAIL PROTECTED] wrote:
* Frank Smith ([EMAIL PROTECTED]) [20020903 11:18] thus spake:
--On Tuesday, September 03, 2002 10:10:18 -0400 Jean-Francois Malouin
[EMAIL PROTECTED] wrote:
Hello,
I just installed and configured amanda-2.4.3b4-20020829 on a Linux box
with an ecrix tape library and I might be stumbling on some bug and/or
feature: relative path exclude list don't seem to be used at all...
Perusing in the posts for 2.4.3b4 announcement from Jean-Louis I see
that this version is supposed to have this fixed... Is this really the
case? I can provide debug files on demand.
Do you have an exclude list properly defined in your dumptype?
Are you using tar?
Is the exclude list file in the top level of the directory you're trying
to back up and is it in the correct format?
I've been using amanda for a few years now and I'm fully aware of all
the quirks in setting up exclude lists. I have 3 other servers running
2.4.2p2 with relative exclude lists with tape libraries (exb-200,
adic-218 and stk-L40) with no problems whatsoever. For this one, I
decided to jump ahead with 2.4.3b4...maybe I'll go back to 2.4.2p2.
Anyways, yes, I'm using tar (GNU tar) 1.13.19.
Here are the dumptypes from amanda.conf:
---
amanda.conf
---
define dumptype global {
comment Global definitions
index yes
record yes
}
define dumptype root-tar {
global
program GNUTAR
comment root partitions dumped with tar
compress none
index
priority low
}
define dumptype high-tar-raid-epilepsy {
root-tar
comment partitions dumped with tar
priority high
exclude list .amanda-gnutar-exclude-list.txt
}
---
disklist entry
---
blade /raid/epilepsy high-tar-raid-epilepsy
---
On the host blade (amanda server and client) I created a file called
/raid/epilepsy/.amanda-gnutar-exclude-list.txt:
[root@blade]# cd /raid/epilepsy/
[root@blade]# ls -la .amanda-gnutar-exclude-list.txt
-rw---1 amanda disk 123 Sep 2 08:18
.amanda-gnutar-exclude-list.txt
---
exclude file
---
[root@blade]# cat .amanda-gnutar-exclude-list.txt
./diffusion/
./extra-TLE/
./F_MRI/
./MRI_misc/
./MT/
./neda/
./PREVIOUS/
./relaxo/
./restore/
./samson/
./thalamus/
./TLE/
Yes, it looks like you have it set up correctly, maybe it is a 2.4.3b4
thing (I'm still running 2.4.2p2). What issues are you seeing with
the latest version?
Unrelated question:
Doesn't the trailing slash on your exclude list entries mean that only
those directories themselves are skipped and not any subdirectories?
I leave off the slash to prune the directory tree at that point, and
can't think of too many uses for excluding a directory while backing
up its subdirectories. Or possibly my idea of exclude syntax is off.
Frank
--
Frank Smith[EMAIL PROTECTED]
Systems Administrator Voice: 512-374-4673
Hoover's Online Fax: 512-374-4501
Re: Label Printing. Resolution
On Tue, 3 Sep 2002 at 12:26pm, Alex Specogna wrote Originally I was under the impression that amdump ran amreport for me and just wasn't outputting anything. Wrong, amreport needs to be run separately. flaw in logic number 1 No, actually that's the way it should work, and does for me. The only amanda command my nightly script runs is 'amdump', and when I come in every morning the report email is waiting for me and the tape labels are on the printer. I run 2.4.2p2 on Linux. From my experimentation amreport APPENDS the text after the -p flag (in this case test.ps) to the current directory name you are in and places the file one directory above your current location. e.g. if you are in /usr/home and you run the command line mentioned above you would get a file called /usr/hometest.ps. I also noticed that if you do not include the Set name in the output name of the -p flag it behaves similarly. Hence to correctly get the labels working do the following: 1) Define the lbl-temp directive in your tapetype definition. 2) Run the amreport command as follows: amreport Set Name -l full path to log file -f /dev/null -p output file inc. set name e.g. amreport Backups -l /usr/adm/amanda/Backups/log.20020903.0 -f /dev/null -p /tmp/Backups-0903.ps This will put the file in a predictable location of /tmp and solve a lot of headaches. That all sounds *very* odd and not the way it works here. If you could, can you give 2.4.2p2 a shot? Or try upgrading to 2.4.3b4 (just released), which might just become 2.4.3. Are there any strange errors or things missing when you ./configure? That behavior just doesn't sound right. This is one thing that the Amanda application is really bad at.. documentation. The application is fabulous.. all it needs is someone to champion the cause of making it easy to use (through documentation). Actually, between the chapter at backupcentral.com, docs/INSTALL, example/*, the list archives, and F-O-M, all the info really is out there. What you're experiencing isn't the right/planned behavior, which is why, I think, you see it the way you do. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: What does -1 mean in disklist
On Tuesday 03 September 2002 11:53, Martinez, Michael - CSREES/ISTM wrote: muchas gracias senor Michael Martinez System Administrator Information Systems and Technology Management CSREES - United States Department of Agriculture (202) 720-6223 -Original Message- From: Gene Heskett [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 03, 2002 11:29 AM To: Martinez, Michael - CSREES/ISTM; [EMAIL PROTECTED] Subject: Re: What does -1 mean in disklist On Tuesday 03 September 2002 09:41, Martinez, Michael - CSREES/ISTM wrote: What does the -1 mean in the following disklist line: www /home2 nocomp-user -1 local According to the notes in the sample disklist, its a spindle number placeholder, whatever that is. Something to do with a raid array that allows each disk/spindle to be addressed individually. A method of backup up each single disk in a raid (I think). Possibly usefull to those with raids. Untested here, no raid. See Paul Borts corrective message. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.13% setiathome rank, not too shabby for a WV hillbilly
Re: What does -1 mean in disklist
On Tuesday 03 September 2002 11:50, Bort, Paul wrote: Actually, it's a performance management thing. If you have several partitions on one physical drive, you can give them all the same spindle number, and AMANDA will only pull one backup from each spindle at a time, to keep from thrashing your drives. I use this on my older firewalls (200MHz or less) to keep the backups from taking over the machine. Thanks, as you could tell, I was in over my head there. -Original Message- [snip useless blather] -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.13% setiathome rank, not too shabby for a WV hillbilly
tar and one-file-system advice
Greetings, I use amanda 2.4.p2-4 with tar and I have a directory on one of my hosts that has an odd setup. I have seven mount points with seven subdirectories that I need to archive. Some of the sub directories have data at any given time and some do not. The data changes rapidly. My thought was that I could create a directory on / and symlink to the real directories (see below), but that is not working. What is happening is that only the symlinks are getting archived. /newdir/link0 - /mnt_pt0/dir /newdir/link1 - /mnt_pt1/dir /newdir/link2 - /mnt_pt2/dir (etc..etc) I believe that this is because of the one-file-system argument passed to tar by amanda. My question is two fold: 1) Is there any way to disable the one-file-system option? If so can this be done on a single disk list entry, new dumptype? 2) Should I just backup each directory seperate? This make restores confusing, as I have to issue a new amrestore cmd for each mount point. Any other suggestions? Thank you for your time. Andrew
2.4.3b4 gnutar exclude troubles
With 2.4.3b3 I was getting MISSING RESULT errors. the b4 release seems to
have at least fixed that, but it's still not excluding the files/dirs
listed in the exclude list.
Disklist entry:
homer.sistina.com /home/homer comp-user-tar
Dumptype as follows:
define dumptype comp-user-tar {
user-tar
priority medium
compress client best
exclude file ./amanda.exclude
}
./amanda.exclude on homer in /home/homer looks like so:
./blutgens
./llama
./tool
./amandahatesme
./gnutarisbeingapunk
./*/.mozilla/*/*/Cache
The overall size of /home/homer is 37G. My exclude list contains
directories which make up 66% of that space (I have 20Gb tapes, and was
going to break it into 3 pieces) in the report where I learn that it's
failed I see:
In /tmp/amanda/sendsize on homer I see:
endsize[5041]: argument list: /bin/tar --create --file /dev/null --directory
/home/homer --one-file-system --listed-incremental
/etc/amanda/gnutar-lists/homer.sistina.com_home_homer_0.new
--sparse --ignore-failed-read --totals --exclude-from
/tmp/amanda/sendsize._home_homer.20020903112939.exclude .
Which looks odd to me since the file
/tmp/amanda/sendsize._home_homer.20020903112939.exclude contains only
./amanda.exclude
Which i do not believe would work. Shouldn't the file:
sendsize._home_homer.20020903112939.exclude e a copy of
amanda.exclude? or a `cat /path/to/amanda.exclude`
Or am I the only one having a problem with the GNUTAR exclude files?
--
Ben Lutgens | http://people.sistina.com/~blutgens/
System Administrator | http://www.sistina.com/
Sistina Software Inc. |
If you love something set it free, if it doesn't come back to you
hunt it down and set it on fire -- George Carlin
msg14544/pgp0.pgp
Description: PGP signature
Re: 2.4.3b4 gnutar exclude troubles
--On Tuesday, September 03, 2002 13:14:45 -0500 Ben Lutgens [EMAIL PROTECTED]
wrote:
With 2.4.3b3 I was getting MISSING RESULT errors. the b4 release seems
to
have at least fixed that, but it's still not excluding the files/dirs
listed in the exclude list.
Disklist entry:
homer.sistina.com /home/homer comp-user-tar
Dumptype as follows:
define dumptype comp-user-tar {
user-tar
priority medium
compress client best
exclude file ./amanda.exclude
===
Shouldn't that line be:
exclude list ./amanda.exclude
Frank
}
./amanda.exclude on homer in /home/homer looks like so:
./blutgens
./llama
./tool
./amandahatesme
./gnutarisbeingapunk
./*/.mozilla/*/*/Cache
The overall size of /home/homer is 37G. My exclude list contains
directories which make up 66% of that space (I have 20Gb tapes, and was
going to break it into 3 pieces) in the report where I learn that it's
failed I see:
In /tmp/amanda/sendsize on homer I see:
endsize[5041]: argument list: /bin/tar --create --file /dev/null
--directory
/home/homer --one-file-system --listed-incremental
/etc/amanda/gnutar-lists/homer.sistina.com_home_homer_0.new
--sparse --ignore-failed-read --totals --exclude-from
/tmp/amanda/sendsize._home_homer.20020903112939.exclude .
Which looks odd to me since the file
/tmp/amanda/sendsize._home_homer.20020903112939.exclude contains only
./amanda.exclude
Which i do not believe would work. Shouldn't the file:
sendsize._home_homer.20020903112939.exclude e a copy of
amanda.exclude? or a `cat /path/to/amanda.exclude`
Or am I the only one having a problem with the GNUTAR exclude files?
--
Ben Lutgens|
http://people.sistina.com/~blutgens/
System Administrator | http://www.sistina.com/
Sistina Software Inc. |
If you love something set it free, if it doesn't come back to you
hunt it down and set it on fire -- George Carlin
--
Frank Smith[EMAIL PROTECTED]
Systems Administrator Voice: 512-374-4673
Hoover's Online Fax: 512-374-4501
Questions
After much experimentation I have finally succesfully created an amanda backup. But I have not been able to figure if these features are possible. 1) I currently have enabled 4 dumps at a time. What I understand this meaning is the option inparallel does 4 cleint dumps at a time. If I have a disklist of 18 disk does that mean that all 18 disk get backed up to one tape or does that mean that every 4 disk get backed up to tape. 2) When sendszie is executed to estimate how big a directory or disk is is it possible to have sendzie work with the process that dumps to tape to judge if a directory is to big for that tape and load another tape for that backup 3) Is it possible just to do fiolesize estimateions before issueing amdump. What I am trying to accomplish is to do estimations and have amdump pick up were it left off to save time. 4) In regards to number 1 to elevate this problem I have been doing amdump configureationname partition. I am doing this for each disk in my disk list is it possible to have certain disk go to one tape and then push otehr disk to go on the second tape. Thanks for all your help Craig Hancock -- -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9P+Y5awsElDuSDs0RAgxoAJ40NBfXWSP5dwsRK6AWZRXP6fNm+wCgpWf4 MwLEwsq3TDVGR8ntq3+w65k= =qTeY -END PGP SIGNATURE-
Re: Amanda-2.4.3b4 and tar exclude lists working?
* Frank Smith ([EMAIL PROTECTED]) [20020903 12:53] thus spake: [...] --- exclude file --- [root@blade]# cat .amanda-gnutar-exclude-list.txt ./diffusion/ ./extra-TLE/ ./F_MRI/ ./MRI_misc/ ./MT/ ./neda/ ./PREVIOUS/ ./relaxo/ ./restore/ ./samson/ ./thalamus/ ./TLE/ Yes, it looks like you have it set up correctly, maybe it is a 2.4.3b4 thing (I'm still running 2.4.2p2). What issues are you seeing with the latest version? some chunk is way beyond tape capacity, but with the exclude list it should fit nicely. Looking at my logs I see that somehow, when amanda makes the schedule it does not take into account the exclude list, miscalculate the size of the chunk and so complains that it can't be backed up because it's too big: --- amandad debug file contains: --- [...] Amanda 2.4 REQ HANDLE 000-18320808 SEQ 1031029801 SECURITY USER amanda SERVICE sendsize OPTIONS features=feff9f00;maxdumps=1;hostname=blade; [...] GNUTAR /raid/epilepsy 0 1970:1:1:0:0:0 -1 OPTIONS |;auth=bsd;index;exclude-list=.amanda-gnutar-exclude-list.txt; [...] Amanda 2.4 REP HANDLE 000-18320808 SEQ 1031029801 OPTIONS features=feff9f00; /raid/epilepsy 0 SIZE 35162160 --- sendsize debug file contains: sendsize: debug 1 pid 24383 ruid 33 euid 33: start at Tue Sep 3 01:10:00 2002 sendsize: version 2.4.3b4-20020829 sendsize[24383]: time 0.480: waiting for any estimate child sendsize[24510]: time 0.481: calculating for amname '/raid/epilepsy', dirname '/raid/epilepsy', spindle -1 sendsize[24510]: time 0.481: getting size via gnutar for /raid/epilepsy level 0 sendsize[24510]: time 0.492: spawning /opt/amanda_vxa/libexec/runtar in pipeline sendsize[24510]: argument list: /bin/gtar --create --file /dev/null --directory /raid/epilepsy --one-file-system --listed-incremental /opt/amanda_vxa/var/amanda/gnutar-lists/blade_raid_epilepsy_0.new --sparse --ignore-failed-read --totals --exclude-from /tmp/amanda/sendsize._raid_epilepsy.20020903011000.exclude . sendsize[24510]: time 7.731: Total bytes written: 36006051840 (33GB, 4.2GB/s) sendsize[24510]: time 7.732: . sendsize[24510]: estimate time for /raid/epilepsy level 0: 7.240 sendsize[24510]: estimate size for /raid/epilepsy level 0: 35162160 KB sendsize[24510]: time 7.732: waiting for /bin/gtar /raid/epilepsy child sendsize[24510]: time 7.732: after /bin/gtar /raid/epilepsy wait sendsize[24510]: time 7.733: done with amname '/raid/epilepsy', dirname '/raid/epilepsy', spindle -1 sendsize[24383]: time 7.733: child 24510 terminated normally --- Notice above the line Total bytes written: 36006051840 (33GB... --- --- The file from the above output --exclude-from contains my exclude file list: --- [root@blade]# cat /tmp/amanda/sendsize._raid_epilepsy.20020903011000.exclude ./diffusion/ ./extra-TLE/ ./F_MRI/ ./MRI_misc/ ./MT/ ./neda/ ./PREVIOUS/ ./relaxo/ ./restore/ ./samson/ ./thalamus/ ./TLE/ My exclude list! --- --- runtar output --- [root@blade]# cat /tmp/amanda/runtar.20020903011000.debug runtar: debug 1 pid 24519 ruid 33 euid 0: start at Tue Sep 3 01:10:00 2002 /bin/gtar: version 2.4.3b4-20020829 running: /bin/gtar: /bin/gtar --create --file /dev/null --directory /raid/epilepsy --one-file-system --listed-incremental /opt/amanda_vxa/var/amanda/gnutar-lists/blade_raid_epilepsy_0.new --sparse --ignore-failed-read --totals --exclude-from /tmp/amanda/sendsize._raid_epilepsy.20020903011000.exclude . Unrelated question: Doesn't the trailing slash on your exclude list entries mean that only those directories themselves are skipped and not any subdirectories? I leave off the slash to prune the directory tree at that point, and can't think of too many uses for excluding a directory while backing up its subdirectories. Or possibly my idea of exclude syntax is off. I sure don't know! But I suspect that you're right. Actually I shoud rather have something like ./blah/* Thanks for the time, jf Frank -- Thought to justify wrong doings, and speech to conceal thoughts.
RE: Questions
After much experimentation I have finally succesfully created an amanda backup. But I have not been able to figure if these features are possible. Congratulations and welcome to my personal favorite backup system. 1) I currently have enabled 4 dumps at a time. What I understand this meaning is the option inparallel does 4 cleint dumps at a time. If I have a disklist of 18 disk does that mean that all 18 disk get backed up to one tape or does that mean that every 4 disk get backed up to tape. This means that up to four dumps are going from the client to the holding disk at a time (no-holding disks go straight to tape, don't worry about that yet.) All of the disks being backed up will go to tape regardless of the inparallel value. 2) When sendszie is executed to estimate how big a directory or disk is is it possible to have sendzie work with the process that dumps to tape to judge if a directory is to big for that tape and load another tape for that backup AMANDA can't handle any partition that has a level 0 size bigger than one tape. The planner program collects the sizes of all of the backups to be done, and then bumps some up or down a level to (a) make sure all needed level 0 backups are done, and (b) fit as much data as possible on the tape. (This is why an accurate tapetype is important, and hardware compression isn't all it's cracked up to be.) If you set runtapes 2 in amanda.conf, AMANDA will spread the backups over the two tapes. I believe the version in development (2.5) will be able to split a partition across tapes. The current version cannot, and if it runs out of tape during a partition, it starts that partition from the beginning on the next tape, to insure it has a good backup. 3) Is it possible just to do fiolesize estimateions before issueing amdump. What I am trying to accomplish is to do estimations and have amdump pick up were it left off to save time. That doesn't make a lot of sense. Are you trying to run the estimates at 1:00 and the dump at 3:00? What if a large file appears in the meantime? Are you trying to resume a backup that was interrupted because it ran out of tape? The remaining partitions are already stored on the holding disk and can be flushed to the next tape. Are you trying to find out how much tape AMANDA will want tonight? You could run amdump with no tape in the drive, and let it run everything to the holding disk (if you have room). The report will then show the size of the backup, and you can then amflush the backups to tape. (This is also how some people use one tape for more than one days' worth of backups if they are DESPARATELY short on tapes.) Are you trying to use two different sizes of tape in the same AMANDA configuration? You might be better off separating the tapes into separate configurations by size, and using each size in a completely separate AMANDA configuration, backing up separate machines. 4) In regards to number 1 to elevate this problem I have been doing amdump configureationname partition. I am doing this for each disk in my disk list is it possible to have certain disk go to one tape and then push otehr disk to go on the second tape. amdump only takes one parameter, the name of the configuration. I expect your partiion parameter is being ignored. Again, if you use runtapes 2, AMANDA will put backups on two tapes as needed. Thanks for all your help Craig Hancock Glad to help, but if you can run an English-language spell check on your messages before posting, it will save everyone time in reading and replying. Thanks. Regards, Paul
Indexing
Hello list, I am still having problems with indexing. I have read and read thru the list but all I see are questions about this problem with no answers. So anyways here goes: My disklist has an entry like this: host da7s1e comp-user-index #mountpoint comment all my logs and conf files are under /usr/local/etc/amanda/normal logs index and curinfo are also under there in subdirs. Under indexdir i get : hostname/diskname/date_dumplevel.gz When i zcat it all the info looks fine. Now when i cd to the directory I am trying to recover and run amrecover -C normal -s index-server -t tape-server -d tape-device i get this: AMRECOVER Version 2.4.2p2. Contacting server on host.domain.com ...220 rsync AMANDA index server (2.4.2p2) ready.200 Access OKSetting restore date to today (2002-09-03)200 Working date set to 2002-09-03.200 Config set to normal.200 Dump host set to host.domain.com.$CWD '/eight3' is on disk 'da7s1e' mounted at '/eight3'.Scanning /usr/hold...200 Disk set to da7s1e.No index records for disk for specified dateIf date correct, notify system administratorInvalid directory - /eight3amrecover Then i go look at the /tmp/amanda/*.debug and see this amindexd: debug 1 pid 1316 ruid 2 euid 2 start time Tue Sep 3 15:19:40 2002amindexd: version 2.4.2p2 220 rsync AMANDA index server (2.4.2p2) ready. SECURITY USER rootbsd security: remote host host.domain.com user root local user operatoramandahosts security check passed 200 Access OK DATE 2002-09-03 200 Working date set to 2002-09-03. SCNF normal 200 Config set to normal. HOST host.domain.com 200 Dump host set to host.domain.com. DISK /eight3 501 No index records for disk: /eight3. Invalid? DISK da7s1e 200 Disk set to da7s1e. DISK da7s1e 200 Disk set to da7s1e. OISD / 500 No dumps available on or before date "2002-09-03" OISD / 500 No dumps available on or before date "2002-09-03" OISD / 500 No dumps available on or before date "2002-09-03" If I am not mistaken it looks like amrecover wants a "/" directory on "da7s1e" However da7s1e is a disk dedicated to the /eight3 mount point. Is this right? I know it is confusing as hell. As I have said, I have seen this talked about but have never seen the answer. Can anyone help me with this? Thanks in advance greg
FW: [SAGE-AU] Amanda users
Hi, I am experimenting with Amanda on our database servers and have discovered that we backing up our databases is proving to be a challenge using Amanda. Specifically, we need to be able to run some pre/post script before/after backing up certain filesystems within a backup session e.g. if I have the following: /db1 / /usr /var etc I want to be able to run a pre script before /db1 and a post script after /db1, then continue backing up the rest of the filesystems in order. Also, Amanda seems to backup the filesystems according to its own order instead of the order listed in the config file. Is there or will there be a feature that will incorporate pre/post scripts per filesystems and also allow a specific order fo filesystems dump. Thank you. Noel Paul Lead Unix Administrator Mincom Phone: 61-7-3364 9876 Fax : 61-7-3364 9777 Email : [EMAIL PROTECTED] Http : www.mincom.com Mincom. The People. The Experience. The Vision. This transmission is for the intended addressee only and is confidential information. If you have received this transmission in error, please delete it and notify the sender. The contents of this E-mail are the opinion of the writer only and are not endorsed by the Mincom Group of companies unless expressly stated otherwise.
[SAGE-AU] Amanda users
Noel, You can break the process into two steps: 1. Run a cron job which will run the pre-script, copy /db1 to a staging location, and then run the post-script. 2. Have amanda backup the staging area, instead of /db1. Amanda likes to come up with it's own schedule for efficiency reasons, so I find it easiest to just decouple the snapshot from the backup on moving filesystems. Nick Nick Russo email: [EMAIL PROTECTED] phone: 773.702.3438 Computer Science Department The University of Chicago Associate Director of Computing Systems, Systems Lead On Wed, 4 Sep 2002, Noel Paul wrote: Hi, I am experimenting with Amanda on our database servers and have discovered that we backing up our databases is proving to be a challenge using Amanda. Specifically, we need to be able to run some pre/post script before/after backing up certain filesystems within a backup session e.g. if I have the following: /db1 / /usr /var etc I want to be able to run a pre script before /db1 and a post script after /db1, then continue backing up the rest of the filesystems in order. Also, Amanda seems to backup the filesystems according to its own order instead of the order listed in the config file. Is there or will there be a feature that will incorporate pre/post scripts per filesystems and also allow a specific order fo filesystems dump. Thank you. Noel Paul Lead Unix Administrator Mincom Phone: 61-7-3364 9876 Fax : 61-7-3364 9777 Email : [EMAIL PROTECTED] Http : www.mincom.com Mincom. The People. The Experience. The Vision. This transmission is for the intended addressee only and is confidential information. If you have received this transmission in error, please delete it and notify the sender. The contents of this E-mail are the opinion of the writer only and are not endorsed by the Mincom Group of companies unless expressly stated otherwise.
gnutar dies on RedHat 6.2
Hi all, Got a working amanda 2.4.3b2 installation running on a FreeBSD 4.6 server. AFAICS everything is OK except for one thing, backing up RedHat 6.2 systems with gnutar. The only trace of the failure I have is the following in /tmp/amanda/: sendsize: asking killpgrp to terminate sendsize: calculating for amname '/etc', dirname '/etc' sendsize: getting size via gnutar for /etc level 0 and then nothing. Dump is fine from same machine. Grateful for a hint, Per olof
