Exclude list and tar on SUSE OES.
Hello,
I've been struggling with this for a while. I have this defined in lots
of places now:
exclude list /usr/local/amanda/exclude.conf
e.g.
define dumptype root-tar {
global
program GNUTAR
comment root partitions dumped with tar
compress none
index
exclude list /usr/local/amanda/exclude.conf
priority low
}
but it doesn't create the right command :
/bin/tar --create --file /dev/null --directory / --one-file-system
--listed-incremental /var/lib/amanda/gnutar-lists/localhost__0.new
--sparse --ignore-failed-read --totals .
at the client.
Help?
Thanks,
Owen.
Re: Exclude list and tar on SUSE OES.
You did put the exclude file on the
client, didn't you ?
http://www.amanda.org/docs/exclude.html#id2533384
Regards,
Bert De Ridder
PeopleWare NV - Head Office
Cdt.Weynsstraat 85
B-2660 Hoboken
Tel: +32 3 448.33.38
Fax: +32 3 448.32.66
PeopleWare NV - Branch Office Geel
Kleinhoefstraat 5
B-2440 Geel
Tel: +32 14 57.00.90
Fax: +32 14 58.13.25
http://www.peopleware.be
http://www.mobileware.be
Owen Williams [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
19/10/2005 12:21
To
amanda-users@amanda.org
cc
Subject
Exclude list and tar on SUSE
OES.
Hello,
I've been struggling with this for a while. I have this defined
in lots
of places now:
exclude list /usr/local/amanda/exclude.conf
e.g.
define dumptype root-tar {
global
program GNUTAR
comment root partitions dumped with tar
compress none
index
exclude list /usr/local/amanda/exclude.conf
priority low
}
but it doesn't create the right command :
/bin/tar --create --file /dev/null --directory / --one-file-system
--listed-incremental /var/lib/amanda/gnutar-lists/localhost__0.new
--sparse --ignore-failed-read --totals .
at the client.
Help?
Thanks,
Owen.
Error: access as amanda not allowed from [EMAIL PROTECTED]
Hi, I have been surfing the web for an solution for a problem with configuring AMANDA with no luck. I know this may have been questioned here before so please be patient with me asking (again) and my english :-) My problem is: I am configuring an amanda client on a Sun Solaris 2.6 and have done that by the standard ways. When i run amcheck on my amanda-server, I get the access as amanda not allowed from [EMAIL PROTECTED] -error In .amandahosts on the client i have defined: my.amanda.server amanda my.amanda.server root The file is in the amanda user's home directory, and an ls -la here gives: 1 -rw-r--r--1 amanda sys76 Oct 18 16:39 .amandahosts My /etc/inetd.conf looks like this: # AMANDA Backup Service amandadgram udp waitamanda /usr/local/libexec/amandadamandad amandaidx stream tcp nowait amanda /usr/local/libexec/amindexd amindexd amidxtape stream tcp nowait amanda /usr/local/libexec/amidxtaped amidxtaped My /etc/services looks like: amanda 10080/udp # Amanda Backup Service amandaidx 10082/tcp # Amanda Backup Service amidxtape 10083/tcp # Amanda Backup Service I have reloaded this file using SIGHUP. I have checked that I can ssh (as amanda) between the server and client and that works fine. It seems that I have forgotten something, but I cant figure it out. Thanks, I hope anyone can assist me getting the client up and running. Regards Paul Christian
Re: Exclude list and tar on SUSE OES.
Bert, You did put the exclude file on the client, didn't you ? http://www.amanda.org/docs/exclude.html#id2533384 Thanks, but yes. Owen. -- Owen Williams [EMAIL PROTECTED] Work0116 2506349 Home0116 2259109 Mobile 0771 5790631 Senior Computing Officer | Software Engineer Consultant | RedHat Certified Engineer DMU Libraries http://www.blue.dmu.ac.uk/
Amanda for Mainframe ??
Hi We have linux lodged under VM on a Mainframe IBM. We wish to safeguard these linux on material STK (Storagetek). Know if AMANDA can compete with products such as FDR/UPSTREAM or NETBACKUP for this kind of safeguard on large system?? Thanks Raphaël PETITJEAN PSA Peugeot Citroën [EMAIL PROTECTED]
Re: Problem with backup
Thank you all for your help. I solved the problem by reinstalling Amanda. On Tue, October 18, 2005 2:40 pm, Jean-Francois Malouin said: * Robert Tilden [EMAIL PROTECTED] [20051018 15:05]: On Tue, October 18, 2005 12:23 pm, Jean-Francois Malouin said: Hi there, * Robert Tilden [EMAIL PROTECTED] [20051018 13:14]: I'm having a problem with amanda backups on one node in our group of linux boxes. -- Bob Tilden, [EMAIL PROTECTED] High Energy Physics Group Northwestern University
Need help diagnosing hostname problems
I had an amanda setup that worked fine until two weeks ago, when I had to change the network addresses of all my hosts and move them into a separate DMZ, using a different, new DNS. Now, I'm not able to get one host to respond, and the output is puzzling: [EMAIL PROTECTED]:/tmp/amanda-dbg$ amcheck -c DBackup Amanda Backup Client Hosts Check ERROR: www.jhuccp.org: [addr 10.253.192.205: hostname lookup failed] Client check: 2 hosts checked in 0.702 seconds, 1 problem found (brought to you by Amanda 2.4.4p3) [EMAIL PROTECTED]:/tmp/amanda-dbg$ dig www.jhuccp.org ; DiG 9.2.4 www.jhuccp.org ;; global options: printcmd ;; Got answer: ;; -HEADER- opcode: QUERY, status: NOERROR, id: 41347 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;www.jhuccp.org.IN A ;; ANSWER SECTION: www.jhuccp.org. 3600IN A 10.253.192.204 ;; Query time: 2 msec ;; SERVER: 10.23.2.10#53(10.23.2.10) ;; WHEN: Wed Oct 19 11:36:58 2005 ;; MSG SIZE rcvd: 48 [EMAIL PROTECTED]:/tmp/amanda-dbg$ I'm puzzled by the response in amcheck, ERROR: www.jhuccp.org: [addr 10.253.192.205: hostname lookup failed] compared to the correct response in dig, ;; ANSWER SECTION: www.jhuccp.org. 3600IN A 10.253.192.204. The IP address that amcheck responded with, 10.253.192.205, is the IP for the tapehost itself, cn2. Is amcheck complaining that 10.253.192.204 doesn't resolve to www.jhuccp.org (it shouldn't; www.jhuccp.org is 205), or is it complaining that 10.253.192.205 doesn't resolve correctly to the name of the tapehost? I tried to check the debug files generated in /tmp/amanda-dbg/. There were four files generated from 'amcheck -c DBackup', but none of them seemed to contain any information regarding this failure. Thanks for any suggestions or advice in working on this problem. -Kevin Zembower - E. Kevin Zembower Internet Systems Group manager Johns Hopkins University Bloomberg School of Public Health Center for Communications Programs 111 Market Place, Suite 310 Baltimore, MD 21202 410-659-6139
RE: Need help diagnosing hostname problems
I presume you have already checked items such as a host file entry that maybe you made when first installing/debugging Amanda ? Scott R. Burns NETCON Technologies Incorporated Suite 135 - 4474 Blakie Road London, Ontario, Canada N6L 1G7 Voice: +1.519.652.0401 Fax: +1.519.652.9275 Web: www.netcontech.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of KEVIN ZEMBOWER Sent: Wednesday, October 19, 2005 11:57 AM To: amanda-users@amanda.org Subject: Need help diagnosing hostname problems I had an amanda setup that worked fine until two weeks ago, when I had to change the network addresses of all my hosts and move them into a separate DMZ, using a different, new DNS. Now, I'm not able to get one host to respond, and the output is puzzling: [EMAIL PROTECTED]:/tmp/amanda-dbg$ amcheck -c DBackup Amanda Backup Client Hosts Check ERROR: www.jhuccp.org: [addr 10.253.192.205: hostname lookup failed] Client check: 2 hosts checked in 0.702 seconds, 1 problem found (brought to you by Amanda 2.4.4p3) [EMAIL PROTECTED]:/tmp/amanda-dbg$ dig www.jhuccp.org ; DiG 9.2.4 www.jhuccp.org ;; global options: printcmd ;; Got answer: ;; -HEADER- opcode: QUERY, status: NOERROR, id: 41347 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;www.jhuccp.org.IN A ;; ANSWER SECTION: www.jhuccp.org. 3600IN A 10.253.192.204 ;; Query time: 2 msec ;; SERVER: 10.23.2.10#53(10.23.2.10) ;; WHEN: Wed Oct 19 11:36:58 2005 ;; MSG SIZE rcvd: 48 [EMAIL PROTECTED]:/tmp/amanda-dbg$ I'm puzzled by the response in amcheck, ERROR: www.jhuccp.org: [addr 10.253.192.205: hostname lookup failed] compared to the correct response in dig, ;; ANSWER SECTION: www.jhuccp.org. 3600IN A 10.253.192.204. The IP address that amcheck responded with, 10.253.192.205, is the IP for the tapehost itself, cn2. Is amcheck complaining that 10.253.192.204 doesn't resolve to www.jhuccp.org (it shouldn't; www.jhuccp.org is 205), or is it complaining that 10.253.192.205 doesn't resolve correctly to the name of the tapehost? I tried to check the debug files generated in /tmp/amanda-dbg/. There were four files generated from 'amcheck -c DBackup', but none of them seemed to contain any information regarding this failure. Thanks for any suggestions or advice in working on this problem. -Kevin Zembower - E. Kevin Zembower Internet Systems Group manager Johns Hopkins University Bloomberg School of Public Health Center for Communications Programs 111 Market Place, Suite 310 Baltimore, MD 21202 410-659-6139
Re: Need help diagnosing hostname problems
On Wed, Oct 19, 2005 at 11:56:52AM -0400, KEVIN ZEMBOWER enlightened us: I had an amanda setup that worked fine until two weeks ago, when I had to change the network addresses of all my hosts and move them into a separate DMZ, using a different, new DNS. Now, I'm not able to get one host to respond, and the output is puzzling: [EMAIL PROTECTED]:/tmp/amanda-dbg$ amcheck -c DBackup Amanda Backup Client Hosts Check ERROR: www.jhuccp.org: [addr 10.253.192.205: hostname lookup failed] Client check: 2 hosts checked in 0.702 seconds, 1 problem found Slightly misleading, but this is a failure trying to resolve the reverse DNS. You need to have a DNS server answering for 10.253.192.205. Matt -- Matt Hyclak Department of Mathematics Department of Social Work Ohio University (740) 593-1263
Please help?
uname -a Linux hostname 2.4.25 #3 SMP Wed May 5 18:14:59 PDT 2004 i686 GNU/Linux amanda 2.4.4p3-2 Oct 19 12:04:59 hostname kernel: Vendor: EXABYTE Model: VXA 1x10 1U Rev: A105 Oct 19 12:04:59 hostname kernel: Type: Medium Changer ANSI SCSI revision: 04 Oct 19 12:04:59 hostname kernel: Vendor: EXABYTE Model: VXA-2 Rev: 2104 Oct 19 12:04:59 hostname kernel: Type: Sequential-Access ANSI SCSI revision: 02 Oct 19 12:04:59 hostname kernel: st: Version 20040102, bufsize 32768, max init. bufs 4, s/g segs 16 Oct 19 12:04:59 hostname kernel: Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 8 Oct 19 12:04:59 hostname kernel: Attached scsi tape st0 at scsi0, channel 0, id 1, lun 0 Oct 19 12:05:04 hostname kernel: st0: Block limits 1 - 245760 bytes. Oct 19 12:05:04 hostname kernel: st0: Mode 0 options: buffer writes: 1, async writes: 1, read ahead: 1 Oct 19 12:05:04 hostname kernel: st0:can bsr: 0, two FMs: 0, fast mteom: 0, auto lock: 0, Oct 19 12:05:04 hostname kernel: st0:defs for wr: 0, no block limits: 0, partitions: 0, s2 log: 0 Oct 19 12:05:04 hostname kernel: st0:sysv: 0 nowait: 0 Oct 19 12:05:04 hostname kernel: st0: Default block size set to 0 bytes. Oct 19 12:39:51 hostname kernel: scsi: device set offline - command error recover failed: host 0 channel 0 id 1 lun 0 Oct 19 12:39:51 hostname kernel: st0: Error 600 (sugg. bt 0x0, driver bt 0x6, host bt 0x0). Oct 19 12:41:47 hostname kernel: scsi: device set offline - command error recover failed: host 0 channel 0 id 0 lun 0 Why does this leave the tape drive in a state where amtape can no longer see the first slot? mt -f /dev/nst0 status returns /dev/nst0: No such file or directory... what is going on here? Thanks! -- Brad Willson Sr. Computer Specialist UW GeneTests, http://www.genetests.org EM: [EMAIL PROTECTED] W: 206.221.4674, C: 425.891.2732
Re: Need help diagnosing hostname problems
Hi, ERROR: www.jhuccp.org: [addr 10.253.192.205: hostname lookup failed] Client check: 2 hosts checked in 0.702 seconds, 1 problem found That seems like network issue to me, rather than amanda issue. Did you make sure that your amanda server can ping to www.jhuccp.org? After renumbering did you change your DNS server address? Bests, olivier
Tape size problem
I have been using Amanda to automate backups to a Ultrium LTO 2 device
for about a year now. Up until now there have been no issues and the
backups were easily fitting on the tapes. However lately the datasize is
going above 100Gig and for some reason Amanda is reporting it has
reached the end of the device even though it is a 200G native tape.
I've ensure'd hardware compression is off and even running an amtapetype
says the tape is only 100Gig.
amtapetype output:
[EMAIL PROTECTED]:~# amtapetype -e 200G -f /dev/nst0
Writing 512 Mbyte compresseable data: 42 sec
Writing 512 Mbyte uncompresseable data: 45 sec
Estimated time to write 2 * 204800 Mbyte: 36000 sec = 10 h 0 min
wrote 3080192 32Kb blocks in 47 files in 7603 seconds (short write)
wrote 3178496 32Kb blocks in 97 files in 7613 seconds (short write)
define tapetype unknown-tapetype {
comment just produced by tapetype prog (hardware compression off)
length 97792 mbytes
filemark 0 kbytes
speed 13162 kps
}
Is the operating system ( Debian Linux - kernel 2.6.13 ) somehow
limiting the tape device size? Has anybody encountered this before I
have no idea how this is happening.
Thanks for your help.
Lloyd
A few questions including dump larger than tape
Hi.
I have been using Amanda for years in a variety of places.
In the case below I am looking after a small school, so the budget is
minimal and I am using a lot of second hand stuff, in this case
4/8BG Sony's, HP's and so on.
The amanda server backs up itself plus that bastion host.
I use two tape drives in the server, one for the OS related stuff
and one for the user data including the samba stuff.
I have never come up with this problem:
FAILURE AND STRANGE DUMP SUMMARY:
lalalalala /samba lev 1 FAILED [dump larger than tape, 10101550 KB,
skipping incremental]
It is true that 10101550 KB is bigger than the tape size, this is a 4/8GB
Sony SDT-5000 which I have given the following setup:
# MMS TAPE 0 @ ADMINSERVER
define tapetype SONY_SDT-5000 {
comment Internal SONY SDT-5000
length 6000 mbytes
filemark 100 kbytes
speed 500 kps
}
I turned the hardware compression on for the tape drives via the jumper setting
on the drive
and I do not use softwware compression.
I know I should not use hardware compression cause amanda likes to know.
However, since I have a small tape drive only, I decided to use a fairly
generous amount in the compression ratio ( I only told it that it has 6GB)
and it is less CPU intesive to use HW compression.
amtapetype in both drives tells me that HW compression IS enabled.
Executing mt status yields:
[EMAIL PROTECTED] /home/amanda/etc/DailySet1] #mt -f /dev/amandatape1
status
SCSI 2 tape drive:
File number=0, block number=0, partition=0.
Tape block size 512 bytes. Density code 0x13 (DDS (61000 bpi)).
Soft error count since last status=0
General status bits on (4101):
BOT ONLINE IM_REP_EN
[EMAIL PROTECTED] /home/amanda/etc/DailySet1] #mt -f /dev/amandatape2
status
SCSI 2 tape drive:
File number=0, block number=0, partition=0.
Tape block size 512 bytes. Density code 0x13 (DDS (61000 bpi)).
Soft error count since last status=0
General status bits on (4101):
BOT ONLINE IM_REP_EN
So what am I not seeing here?
jobst
APPENDICES:
amanda.conf (this is for one, the other one looks the same, except it refers to
the
other disklist!
org DailySet1
mailto [EMAIL PROTECTED]
dumpuser amanda
inparallel 4
dumporder sssS
netusage 600 Kbps
dumpcycle 9 days
runspercycle 9 days
tapecycle 10 tapes
bumpsize 20 Mb
bumpdays 1
bumpmult 4
etimeout 300
dtimeout 1800
ctimeout 30
tapebufs 20
runtapes 1
tapedev /dev/amandatape1
maxdumpsize -1
tapetype SONY_SDT-5000
labelstr ^Media_S1_[0-9][0-9]*$
amrecover_do_fsf yes
amrecover_check_label yes
amrecover_changer /dev/null
holdingdisk hd1 {
comment Amanda Holding Disk
directory /home/amanda/holdingdisk/DailySet1
use -4 Gb
chunksize 1 Gb
}
reserve 30
autoflush no
infofile /home/amanda/curinfo/DailySet1
logdir /home/amanda/logs/DailySet1
indexdir /home/amanda/index/DailySet1
tapelist /home/amanda/tapelist/DailySet1
# MMS TAPE 0 @ ADMINSERVER
define tapetype SONY_SDT-5000 {
comment Internal SONY SDT-5000
length 6000 mbytes
filemark 100 kbytes
speed 500 kps
}
define dumptype global {
comment Global definitions
index yes
record yes
compress none
program GNUTAR
}
define dumptype root-tar {
global
comment root partitions dumped with tar
exclude list /home/amanda/etc/DailySet1/root_exclude.gtar
}
define dumptype home {
global
comment home partition dumped with tar
exclude list /home/amanda/etc/DailySet1/home_exclude.gtar
}
define dumptype standard {
global
comment Standard Partition (no exclusion list)
}
define interface local {
comment a local disk
use 1000 kbps
}
define interface eth0 {
comment 100 Mbps ethernet
use 1000 kbps
}
define interface eth1 {
comment 100 Mbps ethernet
use 1000 kbps
}
disklists 1
lalalalala / root-tar
lalalalala /boot standard
lalalalala /usrstandard
lslslslslsls / root-tar
lslslslslsls /boot standard
disklists 2
lalalalala /home home
lalalalala /varstandard
lalalalala /samba standard
lslslslslsls /varstandard
--
Don't rejoice in his defeat, You men. For though the world stood up and
stopped the Bastard, the Bitch that bore him is in heat again. - Bertold Brecht.
