api script for lvm snapshot
hi i have just installed amanda 2.6.1p1 and i have seen that's there s a script to do a snaphshot of zfs filesystem before backing up. Has someone already done such kind of script for lvm snapshot? Thanks
Re: amrecover problem
Kevin Till a écrit : Axel Seguin wrote: Obviously the client tries to contact the server on port 10080, shouldn't it try to reach the server on port 10082? How can I change that? In ~/.amandahosts on the client I have : server fqdn amanda user on the server amdump Any help would be greatly appreciated. Hi, there is an update on Amanda 2.5.1. To enable different auth mechanism, amandad needs to run on the server. And it will start amindexd and amidxtaped accordingly. Please see http://wiki.zmanda.com/index.php/Configuring_bsd/bsdudp/bsdtcp_authentication well i have seen that but i have a lot of old amanda configuration and i would like to use amoldrecover. when i use that on a remote i got the following message on the amidxtaped.debug more amidxtaped.20070125103831.debug amidxtaped: debug 1 pid 9307 ruid 33 euid 33: start at Thu Jan 25 10:38:31 2007 amidxtaped: version 2.5.1p2 amidxtaped: time 0.000: read error: No such file or directory amidxtaped: time 0.000: pid 9307 finish time Thu Jan 25 10:38:32 2007 on the backup server it works well
problem with amrecover
hi i have some problems with the new framework of security of amanda my server and my client is in the version 2.5.1p2 the amanda-client.conf on the client is this one conf int # your config name index_server backup # your amindexd server tape_server backup # your amidxtaped server #tapedev # your tape device # auth - authentication scheme to use between server and client. # Valid values are bsd, bsdudp, bsdtcp and ssh. # Default: [auth bsdtcp] auth bsdtcp when i run amrecover i got these results amrecover -s backup AMRECOVER Version 2.5.1p2. Contacting server on backup ... [request failed: Connection refused] on the server the debug file amindexd.20070123151619.debug amindexd: debug 1 pid 26735 ruid 33 euid 33: start at Tue Jan 23 15:16:19 2007 amindexd: version 2.5.1p2 close debug file: Bad file descriptor does someone knows how to solve the problem?
Re: problem with amrecover
Jean-Francois Malouin a écrit : * Eric Doutreleau [EMAIL PROTECTED] [20070123 09:23]: hi i have some problems with the new framework of security of amanda my server and my client is in the version 2.5.1p2 the amanda-client.conf on the client is this one conf int # your config name index_server backup # your amindexd server tape_server backup # your amidxtaped server #tapedev # your tape device # auth - authentication scheme to use between server and client. # Valid values are bsd, bsdudp, bsdtcp and ssh. # Default: [auth bsdtcp] auth bsdtcp when i run amrecover i got these results amrecover -s backup AMRECOVER Version 2.5.1p2. Contacting server on backup ... [request failed: Connection refused] on the server the debug file amindexd.20070123151619.debug amindexd: debug 1 pid 26735 ruid 33 euid 33: start at Tue Jan 23 15:16:19 2007 amindexd: version 2.5.1p2 close debug file: Bad file descriptor does someone knows how to solve the problem? What's in your ~amanda/.amandahosts (and check permissions too!) Explained in: http://wiki.zmanda.com/index.php/Configuring_bsd/bsdudp/bsdtcp_authentication hth jf hi my .amandahosts is owned by my backup user and is mode 700 it contains rezo.int-evry.frrootamindexd amidxtaped I guess all is ok for that
Re: problems with index creation
Le samedi 02 juillet 2005 à 13:31 -0400, Jon LaBadie a écrit : On Sat, Jul 02, 2005 at 06:17:11PM +0200, Eric DOUTRELEAU wrote: Hi with changing index to index yes it didn't solved my problem. and the output if the commands give me the same output. the only thing that i can see about the hosts that failed is that they a lot of partition to backup. one has 20 and the othr 36 Selon Jon LaBadie [EMAIL PROTECTED]: On Fri, Jul 01, 2005 at 05:36:18PM +0200, ERic Doutreleau wrote: Indeed i have index yes for almost type except some that are realted to my problems. i will test that that night thanks for your answer Le vendredi 01 juillet 2005 à 07:25 -0400, Jon LaBadie a écrit : On Fri, Jul 01, 2005 at 11:48:38AM +0200, Eric Doutreleau wrote: i have a problem with index creation. i have out the word index on my dumptype but the index created are always empty. Just to confirm, do you have just the word index, or is it index yes? Should be the latter. Do you specify spindle numbers for those DLEs to prevent all 20 and 36 from trying to be backed up at the same time? yes i did the backup are running fine it s only the index the problem I seem to recall some problem with udp packet size and large number of DLEs. well it was what i was thinking of i will search the archive for that.
Re: problems with index creation
Hi with changing index to index yes it didn't solved my problem. and the output if the commands give me the same output. the only thing that i can see about the hosts that failed is that they a lot of partition to backup. one has 20 and the othr 36 Selon Jon LaBadie [EMAIL PROTECTED]: On Fri, Jul 01, 2005 at 05:36:18PM +0200, ERic Doutreleau wrote: Indeed i have index yes for almost type except some that are realted to my problems. i will test that that night thanks for your answer Le vendredi 01 juillet 2005 à 07:25 -0400, Jon LaBadie a écrit : On Fri, Jul 01, 2005 at 11:48:38AM +0200, Eric Doutreleau wrote: i have a problem with index creation. i have out the word index on my dumptype but the index created are always empty. Just to confirm, do you have just the word index, or is it index yes? Should be the latter. I wonder what amadmin config_name disklist hostname dle_name would show for dumptypes with just index? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax) This message was sent using IMP, the Internet Messaging Program.
problems with index creation
i have a problem with index creation.
i have out the word index on my dumptype but the index created are
always empty.
here is some debug
on the client the sendbackup.
we can see in it that the index is created succesfully.
more sendbackup.20050630231107.debug
sendbackup: debug 1 pid 13721 ruid 33 euid 33: start at Thu Jun 30
23:11:07 2005/usr/lib/amanda/sendbackup: version 2.4.4p2
parsed request as: program `DUMP'
disk `/var/spool/imap21'
device `/var/spool/imap21'
level 3
since 2005:6:27:21:57:9
options `|;bsd-auth;compress-fast;index;'
sendbackup: try_socksize: send buffer size is 65536
sendbackup: time 0.001: stream_server: waiting for connection:
0.0.0.0.57878
sendbackup: time 0.001: stream_server: waiting for connection:
0.0.0.0.57879
sendbackup: time 0.001: stream_server: waiting for connection:
0.0.0.0.57880
sendbackup: time 0.001: waiting for connect on 57878, then 57879, then
57880
sendbackup: time 0.003: stream_accept: connection from
157.159.21.10.12394
sendbackup: time 0.003: stream_accept: connection from
157.159.21.10.12395
sendbackup: time 0.003: stream_accept: connection from
157.159.21.10.12396
sendbackup: time 0.003: got all connections
sendbackup: time 0.003: spawning /usr/bin/gzip in pipeline
sendbackup: argument list: /usr/bin/gzip --fast
sendbackup-dump: time 0.004: pid 13723: /usr/bin/gzip --fast
sendbackup: time 0.007: dumping device '/dev/sdc8' with 'ext3'
sendbackup: time 0.012: started index creator: /sbin/restore -tvf -
21 | sed
-e '
s/^leaf[]*[0-9]*[ ]*\.//
t
/^dir[ ]/ {
s/^dir[ ]*[0-9]*[ ]*\.//
s%$%/%
t
}
d
'
sendbackup: time 0.013: spawning /sbin/dump in pipeline
sendbackup: argument list: dump 3usf 1048576 - /dev/sdc8
sendbackup: time 0.099: 93: normal(|): DUMP: Date of this level 3
dump: Thu
Jun 30 23:11:07 2005
sendbackup: time 0.101: 93: normal(|): DUMP: Date of last level 2
dump: Tue
Jun 28 00:01:32 2005
sendbackup: time 0.102: 93: normal(|): DUMP: Dumping /dev/sdc8
(/var/spool/imap21) to standard output
sendbackup: time 0.103: 93: normal(|): DUMP: Excluding inode 8
(journal inode) from dump
sendbackup: time 0.104: 93: normal(|): DUMP: Excluding inode 7
(resize inode) from dump
sendbackup: time 0.711: 93: normal(|): DUMP: Label: none
sendbackup: time 0.713: 93: normal(|): DUMP: Writing 10 Kilobyte
records
sendbackup: time 0.714: 93: normal(|): DUMP: mapping (Pass I)
[regular files]
sendbackup: time 13.240: 93: normal(|): DUMP: mapping (Pass II)
[directories]
sendbackup: time 14.550: 93: normal(|): DUMP: estimated 39683
blocks.
sendbackup: time 14.553: 93: normal(|): DUMP: Volume 1 started with
block 1
at: Thu Jun 30 23:11:21 2005
sendbackup: time 14.575: 93: normal(|): DUMP: dumping (Pass III)
[directories]
sendbackup: time 15.580: 93: normal(|): DUMP: dumping (Pass IV)
[regular files]
sendbackup: time 36.977: 93: normal(|): DUMP: Volume 1 completed at:
Thu Jun 30 23:11:44 2005
sendbackup: time 36.979: 93: normal(|): DUMP: Volume 1 39880 blocks
(38.95MB)
sendbackup: time 36.980: 93: normal(|): DUMP: Volume 1 took 0:00:23
sendbackup: time 36.981: 93: normal(|): DUMP: Volume 1 transfer
rate: 1733 kB/s
sendbackup: time 36.981: 62:size(|): DUMP: 39880 blocks (38.95MB)
sendbackup: time 36.982: 93: normal(|): DUMP: finished in 23
seconds, throughput 1733 kBytes/sec
sendbackup: time 36.990: 93: normal(|): DUMP: Date of this level 3
dump: Thu Jun 30 23:11:07 2005
sendbackup: time 36.991: 93: normal(|): DUMP: Date this dump
completed: Thu Jun 30 23:11:44 2005
sendbackup: time 36.992: index created successfully
sendbackup: time 36.994: 93: normal(|): DUMP: Average transfer rate:
1733 kB/s
sendbackup: time 36.995: 93: normal(|): DUMP: DUMP IS DONE
sendbackup: time 36.995: pid 13721 finish time Thu Jun 30 23:11:44 2005
on the server
in the amdump file
driver: send-cmd time 8298.861 to dumper2: FILE-DUMP
03-00541 /holddisk/disk/20050630/molure._var_spool_imap23.3 molure
feff9ffe0f /var/spool/imap23 NODEVICE 3 2005:6:27:22:0:6 4194304
DUMP 24448 |;bsd-auth;compress-fast;index;
driver: finished-cmd time 8329.237 dumper2 dumped
molure:/var/spool/imap23
driver: send-cmd time 8488.135 to taper: FILE-WRITE
01-00570 /holddisk/disk/20050630/molure._var_spool_imap23.3 molure
feff9ffe0f /var/spool/imap23 3 20050630
driver: startaflush: FIRST molure /var/spool/imap23 2 963920466
driver: finished-cmd time 8488.421 taper wrote molure:/var/spool/imap23
all seems ok but the index file is empty as the dump file is not.
my client is running Fedora core 2.
has anyone seen already that kind of problem?
thanks in advance for any help
Re: problems with index creation
Indeed i have index yes for almost type except some that are realted to my problems. i will test that that night thanks for your answer Le vendredi 01 juillet 2005 à 07:25 -0400, Jon LaBadie a écrit : On Fri, Jul 01, 2005 at 11:48:38AM +0200, Eric Doutreleau wrote: i have a problem with index creation. i have out the word index on my dumptype but the index created are always empty. Just to confirm, do you have just the word index, or is it index yes? Should be the latter.
problems backuping root partition with dump on FC3
i cannot backup / partition with dump on my FC3 machine. I'm using amanda-2.4.4p3-1 on both server and client Steps to Reproduce: i have configured my amanda server to backup a / partition on my FC3 computer. I use the mountpoint / in my disklist file i got the following report sonde / lev 0 FAILED [disk /, all estimate failed] here is some information from the sendize file on the client. sendsize[23903]: time 0.021: calculating for amname '/', dirname '/', spindle 1 sendsize[23903]: time 0.021: getting size via dump for / level 0 sendsize[23903]: time 0.021: calculating for device '/dev/root' with 'ext3' sendsize[23903]: time 0.021: running /sbin/dump 0Ssf 1048576 - /dev/root the /dev/sdb2 is mounted on / partition but instead of using /dev/sdb2 it uses /dev/root for backup here is the right of the two devices brw--- 1 root root 8, 18 avr 1 16:48 /dev/root brw-rw 1 root disk 8, 18 avr 1 16:48 /dev/sdb2 then amanda could use the second on but not the first one. has somebody already had this problem? thank in advance for any help
Re: amrecover with file: driver
Hi That s a bit strange. my amrecover can change tape and find the good. you have to put the following parameter in amanda.conf amrecover_changer /dev/null and to launch amrecover in that way amrecover -d /dev/null then the tape server will use the changer specified in the amanda.conf file to find the good tape. hope that helps Le lun 26/01/2004 09:42, JC Simonetti a crit : amrecover does not change the tape by itself. You have to keep in mind that the chg-disk emulates a robotic with the hard drive. And amrecover (certainly due to security reasons that I won't discuss here) does not automatically search the correct tape in the robot: the tape(s) you want to use when restoring have to be in the tape device when needed. In my case I have 2 xterms, one with amrecover, and the other one where I run amtape to load the right tape when amrecover tells me to do it. On 22 Jan 2004 11:54:11 -0700 Marc Langlois [EMAIL PROTECTED] wrote: Stefan, The settape section of the man page for amrecover says: settape [[server]:][tapedev|default] If you want amrecover to use your changer, the tapedev must be equal to the amrecover_changer setting on the server. I used this setting in amanda.conf: amrecover_changer chg-disk then, in amrecover: settape chg-disk and the extract invokes the chg-disk script and sets the ./data sym-link to the correct slot automatically. Very nice! Marc. It appears that using settape chg-disk in amrecover On Thu, 2004-01-22 at 09:17, Stefan G. Weichinger wrote: Hi, Marc, on Donnerstag, 22. Jnner 2004 at 16:59 you wrote to amanda-users: ML I'm using the chg-disk changer. Does amrecover use the changer script? Good question. There is the parameter amrecover_changer which explicitly sets the changer used. Maybe you try to set this in your conf. ML And would it be possible to modify the script to choose the correct ML slot? As soon as I know it I will tell you ;) Practically YES, it is possible.
Re: advice for archival
Hi Well this question was implicit. I have already did some test and i succeeded to get data back from my tape. Le dim 14/12/2003 à 23:49, Jon LaBadie a écrit : On Sun, Dec 14, 2003 at 11:09:44PM +0100, Eric Doutreleau wrote: Hi We are succesfully backup our amanda configuration to a remote site to an array of cheap IDE disk. It works quite well right now i would like to make some archive of what i have backuped. i want to use the data i have on my array of ide disk. I will describe what i do and i would like to get advice on it. ... do u think all these is ok? I think the key question is: Can you recover/restore from your SI tapes?
advice for archival
Hi We are succesfully backup our amanda configuration to a remote site to an array of cheap IDE disk. It works quite well right now i would like to make some archive of what i have backuped. i want to use the data i have on my array of ide disk. I will describe what i do and i would like to get advice on it. i could post my script too if someone is interested on the list. my main amanda configuration is named INT. i have created a pseudo configuration named SI which contained only a subset of the first one. It s the data i want to archive. my script walk through the data of the first configuration. It search the level 0 file and all the incremental since today. it hardlinks the file in the holddisk on the SI configuration. it hardlinks too the index file from the INT configuration to the SI configuration when it s finish i run the amflush for the SI configuration. do u think all these is ok? thanks for your advice
Re: Error Configuration Tapeless
On Fri, 4 Apr 2003, Audrey BROCHET wrote:
You must use at least the 2.4.3 version of amanda to be able
to backup in a file instead of a tape.
I have followed the next explanation :
http://amanda.sourceforge.net/cgi-bin/fom?auth=ckd2128107166efile=191
But I have many problem to backup
$amchech DailySet1
Amanda Tape Server Host Check
-
amcheck-server: fatal slot 1: file:/stock/web/tape1: not a device file
ERROR: new tape not found in rack
(expecting a new tape)
NOTE: skipping tape-writable test
Server check took 0.158 seconds
Amanda Backup Client Hosts Check
Client check: 1 host checked in 0.031 seconds, 0 problems found
(brought to you by Amanda 2.4.2p2)
A copy out of amanda.conf :
runtapes 1
tpchanger chg-multi
changerfile /etc/amanda/DailySet1/chg-multi.conf
tapedev file:/stock/web/tape1
tapetype HARD-DISK
labelstr ^DailySet1[0-9][0-9]*$
define tapetype HARD-DISK {
comment Hard disk instead of tape
length 1 mbytes
}
define dumptype hard-disk-dump {
comment Back up to hard disk instead of tape - using dump
options index, no-hold
priority high
}
define dumptype hard-disk-tar {
comment Back up to hard disk instead of tape - using tar
options index, no-hold
program GNUTAR
}
A copy out of chg-multi.conf :
multieject 0
gravity 0
needeject 0
ejectdelay 0
statefile /var/lib/amanda/DailySet1/changer-status
firstslot 1
lastslot 2
slot 1 file:/stock/web/tape1
slot 2 file:/stock/web/tape2
--
Eric Doutreleau
I.N.T | Tel : +33 (0) 160764687
9 rue Charles Fourier | Fax : +33 (0) 160764321
91011 Evry France | email : [EMAIL PROTECTED]
Re: No tape
On Wed, 2 Apr 2003, Audrey Brochet wrote: Yes you must run a version posterior of amanda-2.4.3 and use the driver file: in amanda.conf instead of tape device Is it possible to use Amanda with only backup on hard disk but not on tape ?? How does this ?? Thank you - Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Testez le nouveau Yahoo! Mail -- Eric Doutreleau I.N.T | Tel : +33 (0) 160764687 9 rue Charles Fourier | Fax : +33 (0) 160764321 91011 Evry France | email : [EMAIL PROTECTED]
Re: amrecover problem with changer
On Fri, 21 Mar 2003, Jon LaBadie wrote: On Thu, Mar 20, 2003 at 05:30:14PM -0800, Stephen Walton wrote: I am trying a test amrestore of some files after amanda has run for a bit on a RedHat 8.0 system with an HP DDS-3 6-tape changer. The backups are fine, as are the automatic tape changes; I can get at all of my backups manually with dd and tar. However, amrestore is not happy. The details: I'm using amanda 2.4.3 compiled locally (no RedHat RPM for me). 'tapedev 0' appears in amanda.conf since I'm using a changer. You are using a changer to change the tapes. You are still using a tape device to read and write the tapes. amidxtaped.*.debug reveals that amrecover, when used, exec's amrestore -h -p 0 followed by the usual remaining arguments. Of course this fails, since there is no file or device named 0 which amrestore can get at. Have you tried setting tapedev to your tape device? amrecover doesn't use the device that is returned by the changer prior the 28022003 shanpshot ( it s a snapshot after the 2.4.4 release ). Moreover you have to configure this parameter in your amanda.conf amrecover_changer glopglop# amrecover will use the changer if you restore and to lauch amrecover -d glopglop to make amidxtaped use the changer. Hope that helps -- Eric Doutreleau I.N.T | Tel : +33 (0) 160764687 9 rue Charles Fourier | Fax : +33 (0) 160764321 91011 Evry France | email : [EMAIL PROTECTED]
Re: tapeless changer
On 18 Mar 2003, briner wrote: You should follow the instruction that you found in this mail http://groups.yahoo.com/group/amanda-users/message/40286 Morevover u should switch to a version of snapshot after the 20032802 in order to have amrecover use correctly the changer. Hope that help hi, I'm wondering if there is a way in the case where we use amanda with a tapeless system (HD disk), to emulate such a tape-changer that is a script which change the link data to the good HD in my case +amanda.conf has the follwing line: tapedev file:/unige/amanda/bckp/ +ls -l /unige/amanda/bckp/ /unige/amanda/bckp/data - sb03_1/ /unige/amanda/bckp/info /unige/amanda/bckp/sb01_1 - /net/obssb1/export/diskB1/1/ /unige/amanda/bckp/sb01_2 - /net/obssb1/export/diskB1/2/ /unige/amanda/bckp/sb02_1 - /net/obssb2/export/diskB1/1/ /unige/amanda/bckp/sb02_2 - /net/obssb2/export/diskB1/2/ /unige/amanda/bckp/sb03_1 - /net/obssb3/export/diskB1/1/ /unige/amanda/bckp/sb03_2 - /net/obssb3/export/diskB1/2/ /unige/amanda/bckp/sb05_1 - /net/obssb5/export/diskB1/1/ /unige/amanda/bckp/sb05_2 - /net/obssb5/export/diskB1/2/ so as you imagine, i'm changing automatically with a script the link data to one of the tapeDisk. But is there an other smarty way to do this through a special changerdev which will make things much more easier! briner -- Eric Doutreleau I.N.T | Tel : +33 (0) 160764687 9 rue Charles Fourier | Fax : +33 (0) 160764321 91011 Evry France | email : [EMAIL PROTECTED]
Re: amrecover file based backup and rewind
On Thu, 13 Mar 2003, Gregor Ibic wrote: Hi what version of amanda do u use? Do u use it with the pseudo changer device chg-multi ? amanda-2.4.4 can use the changer file with amrecover but it won't use the device sent by the changer device. Therefore it work for all changer except for the chg-multi changer program. This problem is solved in recent snapshot ( after 20030228 version ) You can find them in the following page http://www.iro.umontreal.ca/~martinea/amanda/ Im trying to recover some file from file based backup. Im using the changer for rotating backup folders. The problem is that amrecover wants to rewind the tape, but it tries to rewind the file:/data/Daily instead of file:/data/Daily/backup/Daily03 which is the real file backup tape. If I rewind it manually it still tries to do it and amrecover fail. Regards, Gregor -- Eric Doutreleau I.N.T | Tel : +33 (0) 160764687 9 rue Charles Fourier | Fax : +33 (0) 160764321 91011 Evry France | email : [EMAIL PROTECTED]
Re: Who uses amanda?
On Wed, 12 Mar 2003, Dr. David Kirkby wrote: We are a french university and we use amanda to backup our unix system. here is our configuration. library DLT1 with 10 slots 650Go of backup with 70 hosts our server is a dell poweredge 1650 with a Gigabit Card. Can anyone tell me if they use amanda and are a large commercial company ( 250 employees), a hospital or a university and if so how much it's used (whole institution, small department, single server etc). How many Gb do you back up (don't answer that if you feel its confidential, or you don't know). I don't work in computer support but are aware there is a talk of buying a Veritas backup package at academic discount (around 800 UK pounds or $1300). I wanted to know if amanda would be a viable option. I guess there are going to be issues bought up about support, stability, the importance of backups etc. I'd like to know of big organistations using the software and if they have compared it to Veritas. I looked at using amanda once for my home computer (Sun Ultra 80, about 200 Gb of disk space over 4/5 drives, 40 Gb tape drive), but decided that for such a small system, a couple of unix shell scripts run by cron was all I needed, so never bothered using amanda. I know shell scripts are currently used here but we intend expanding the disk space by quite a lot. So basically: a) I know little about amanda b) Have no intention of using it myself for my home computer, but wonder if its a variable option in a university department (~100 staff). Dr. David Kirkby PhD, Senior Research Fellow, Department of Medical Physics, University College London, 11-20 Capper St, London, WC1E 6JA. Tel: 020 7679 6408 Fax: 020 7679 6269 Internal telephone: ext 46408 e-mail [EMAIL PROTECTED] Web page: http://www.medphys.ucl.ac.uk/~davek -- Eric Doutreleau I.N.T | Tel : +33 (0) 160764687 9 rue Charles Fourier | Fax : +33 (0) 160764321 91011 Evry France | email : [EMAIL PROTECTED]
Re: amrecover: Connection refused
On Wed, 26 Feb 2003, bao wrote: I found it. The installation set the user of amandaidx and amidxtape to amanda, but I dont know why Amanda requires root to run it, which conflicts with the default setting. Amanda run amandaidx and amidxtape under the user amanda. but it s the server part amrecover is the client part and then should run under the identity of root. bao wrote: Hi, I've configured tapeless backup, and trying to verify the data by running amrecover. It says Connection refused I had port in /etc/services, and xinetd enabled; and also an entry lnx200.gibbons.comroot in .amandahosts Server is itself client, and recovery is done on it. Here's the complete message (Amanda 2.4.3) AMRECOVER Version 2.4.3. Contacting server on lnx200.gibbons.com ... amrecover: cannot connect to lnx200.gibbons.com: Connection refused Can anyone help me resolve this? Thanks, -- Eric Doutreleau I.N.T | Tel : +33 (0) 160764687 9 rue Charles Fourier | Fax : +33 (0) 160764321 91011 Evry France | email : [EMAIL PROTECTED]
amrecover and changer with amanda-2.4.4b1
Hi I have seen something very interesting on the changelog of amanda2.4.4b1 it s the ability of amrecover ( and related servers ) to use the changer. i have setup successfully amanda with a tapeless configuration with the chg-multi script. then i m trying to configure the amrecover to use the the changer here s the related portion of file on my configuration amrecover_do_fsf yes amrecover_check_label yes # amrecover will call amrestore with the amrecover_changer changer but when i launch amrecover i got the following error Extracting files using tape drive changer on host backup.int-evry.fr. Load tape DSK05 now Continue [?/Y/n/s/t]? Y EOF, check amidxtaped.debug file on backup.int-evry.fr. amrecover: short block 0 bytes UNKNOWN file amrecover: Can't read file header extract_list - child returned non-zero status: 1 Continue [?/Y/n/r]? r when i look at amidxtaped.debug i see amidxtaped: time 0.351: HEADER amidxtaped: time 0.351: DEVICE=changer amidxtaped: time 0.351: HOST=^molure$ amidxtaped: time 0.351: DISK=^/var/spool/imap1$ amidxtaped: time 0.351: DATESTAMP=20030223 amidxtaped: time 0.351: END amidxtaped: time 0.351: config 'testdisk' valeur DSK05: label 'changer' not found changer: got exit: 0 str: 5 7 1 changer_query: changer return was 7 1 changer_query: searchable = 0 changer_find: looking for DSK05 changer is searchable = 0 changer: got exit: 0 str: 5 file:/var/lib/backuppc/amanda/t5 amidxtaped: time 0.438: slot 5: date 20030223 label DSK05 (exact label match) amidxtaped: time 0.438: label DSK05 found amidxtaped: time 0.438: amrestore_nargs=0 amidxtaped: time 0.438: Ready to execv amrestore with: path = /usr/local/sbin/amrestore argv[0] = amrestore argv[1] = -p argv[2] = -h argv[3] = -l argv[4] = DSK05 argv[5] = -f argv[6] = 16 argv[7] = changer argv[8] = ^molure$ argv[9] = ^/var/spool/imap1$ argv[10] = 20030223 amrestore: could not stat changer: No such file or directory It seems that the changer give the device to use but the daemon amidxtaped didn't used that value. is it supported or should i modify the code to make it work? Thanks in advance. -- Eric Doutreleau I.N.T | Tel : +33 (0) 160764687 9 rue Charles Fourier | Fax : +33 (0) 160764321 91011 Evry France | email : [EMAIL PROTECTED]
problem with cygwin and amanda2.4.4b1
Hello I'm trying to setup amanda2.4.4b1 on a win2000 machine with cygwin. I followed the instruction in the HOWTO for cygwin but have the following problem. i run /usr/sbin/inetd -d on the win2000 machine I run amcheck -c testdisk on my server on my 2000 machine i got the follwoing messages someone wants amanda +closing from 16 848 execl /usr/local/libexec/amandad 848 reaped, status 0x100 restored amanda, fd 16 Has someone already seen that kind of message? Thanks in advance for any help -- Eric Doutreleau I.N.T | Tel : +33 (0) 160764687 9 rue Charles Fourier | Fax : +33 (0) 160764321 91011 Evry France | email : [EMAIL PROTECTED]
Re: problem with cygwin and amanda2.4.4b1
On Fri, 21 Feb 2003, Richard Morse wrote: Hello I'm trying to setup amanda2.4.4b1 on a win2000 machine with cygwin. I followed the instruction in the HOWTO for cygwin but have the following problem. i run /usr/sbin/inetd -d on the win2000 machine I run amcheck -c testdisk on my server on my 2000 machine i got the follwoing messages someone wants amanda +closing from 16 848 execl /usr/local/libexec/amandad 848 reaped, status 0x100 restored amanda, fd 16 Hi! I got these exact same messages (modulo a few numbers). One possibility is that you didn't use tabs in all the correct places in inetd.conf? Also, try seeing how it works if you have inetd set as a service. You can add it as a service with /usr/sbin/inetd --install-as-service, and you can then uninstall it with /usr/sbin/inetd --remove-as-service. I found that the -d option didn't let it work, while it did when running as a service... Ricky Well thanks for your answer but i got exactly the same result. I have to admit i m not an windows2000 guru. But as i run a localized version of win2000 ( french one ) is the value SYSTEM still exact or should i localize too? -- Eric Doutreleau I.N.T | Tel : +33 (0) 160764687 9 rue Charles Fourier | Fax : +33 (0) 160764321 91011 Evry France | email : [EMAIL PROTECTED]
Re: 2.4.2p2/xinetd/linux 2.4 problem ...
On Wed, 13 Nov 2002, Do-Risika RAFIEFERANTSIARONJY wrote:
You shoud upgrade to the last version of xinetd.
I had exactly the same problem before upgrading
Hi all,
I try to run amanda client with xinetd instead of inetd.
But, running amcheck on the amanda server seems to crash the xinetd
process on the client, and to leave a process [amandad defunct]. After
that, amcheck from the server results 'selfcheck timed out'. However,
there is no problem with inetd.
I wonder if it is a problem with the triplet amanda2.4.2p2/xinetd/linux
kernel 2.4, because I use amanda2.4.2p2/xinetd with a kernel 2.2 without
problem ?
Has someone already experienced this ? and how to resolve ?
I put here below :
* my xinetd.conf contents,
* the 2 processes xinetd and amandad defunct,
* and the amandad.debug in /tmp/amanda (in which I do not notice any error).
I use Linux Debian woody, if it could interests.
sokatra:~# cat /etc/xinetd.conf
defaults
{
log_type= FILE /var/log/xinetd.log
log_on_success = PID
log_on_failure = HOST RECORD
}
service amanda
{
socket_type = dgram
protocol= udp
wait= yes
user= backup
group = backup
groups = yes
server = /usr/lib/amanda/amandad
only_from = 192.168.11.1
flags = IPv4
}
sokatra:~#
sokatra:~# ps auxw | egrep '(inet|amanda)'
root 1814 0.0 0.7 2056 892 ?S12:21 0:00
/usr/sbin/xinetd -reuse
backup1818 0.0 0.0 00 ?Z12:22 0:00 [amandad
defunct]
sokatra:~# cat /tmp/amanda/amandad.20021113122216.debug
amandad: debug 1 pid 1818 ruid 34 euid 34 start time Wed Nov 13 12:22:16
2002
amandad: version 2.4.2p2
amandad: build: VERSION=Amanda-2.4.2p2
amandad:BUILT_DATE=Tue Apr 2 21:24:21 UTC 2002
amandad:BUILT_MACH=Linux cyberhq 2.4.18pre2 #1 SMP Tue Jan 8
18:13:43 PST 2002 i686 unknown
amandad:CC=gcc
amandad: paths: bindir=/usr/sbin sbindir=/usr/sbin
amandad:libexecdir=/usr/lib/amanda mandir=/usr/share/man
amandad:AMANDA_TMPDIR=/tmp/amanda AMANDA_DBGDIR=/tmp/amanda
amandad:CONFIG_DIR=/etc/amanda DEV_PREFIX=/dev/
amandad:RDEV_PREFIX=/dev/r DUMP=/sbin/dump
amandad:RESTORE=/sbin/restore SAMBA_CLIENT=/usr/bin/smbclient
amandad:GNUTAR=/bin/tar COMPRESS_PATH=/bin/gzip
amandad:UNCOMPRESS_PATH=/bin/gzip MAILER=/usr/bin/Mail
amandad:listed_incr_dir=/var/lib/amanda/gnutar-lists
amandad: defs: DEFAULT_SERVER=localhost DEFAULT_CONFIG=DailySet1
amandad:DEFAULT_TAPE_SERVER=localhost
amandad:DEFAULT_TAPE_DEVICE=/dev/null HAVE_MMAP HAVE_SYSVSHM
amandad:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE
amandad:AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTS
amandad:CLIENT_LOGIN=backup FORCE_USERID HAVE_GZIP
amandad:COMPRESS_SUFFIX=.gz COMPRESS_FAST_OPT=--fast
amandad:COMPRESS_BEST_OPT=--best UNCOMPRESS_OPT=-dc
got packet:
Amanda 2.4 REQ HANDLE 000-604D0608 SEQ 1037179339
SECURITY USER backup
SERVICE selfcheck
OPTIONS ;
GNUTAR /var/log 0 OPTIONS
|;bsd-auth;compress-fast;index;exclude-list=/lib/amanda/exclude.gtar;
GNUTAR /var/www 0 OPTIONS
|;bsd-auth;compress-fast;index;exclude-list=/lib/amanda/exclude.gtar;
GNUTAR /usr/local/bin 0 OPTIONS
|;bsd-auth;compress-fast;index;exclude-list=/lib/amanda/exclude.gtar;
GNUTAR /etc 0 OPTIONS
|;bsd-auth;compress-fast;index;exclude-list=/lib/amanda/exclude.gtar;
sending ack:
Amanda 2.4 ACK HANDLE 000-604D0608 SEQ 1037179339
bsd security: remote host parasy.backup.simicro.net user backup local
user backup
amandahosts security check passed
amandad: running service /usr/lib/amanda/selfcheck
amandad: sending REP packet:
Amanda 2.4 REP HANDLE 000-604D0608 SEQ 1037179339
OPTIONS ;
OK /var/log
OK /var/www
OK /usr/local/bin
OK /etc
OK /usr/lib/amanda/runtar executable
OK /bin/tar executable
OK /var/lib/amanda/amandates read/writable
OK /var/lib/amanda/gnutar-lists/. read/writable
OK /bin/gzip executable
OK /dev/null read/writable
OK /tmp/amanda has more than 64 KB available.
OK /tmp/amanda has more than 64 KB available.
OK /var/lib has more than 64 KB available.
amandad: got packet:
Amanda 2.4 ACK HANDLE 000-604D0608 SEQ 1037179339
amandad: pid 1818 finish time Wed Nov 13 12:22:16 2002
sokatra:~#
Thanks in advance,
Regards,
--
Eric Doutreleau
I.N.T | Tel : +33 (0) 160764687
9 rue Charles Fourier | Fax : +33 (0) 160764321
91011 Evry France | email : [EMAIL PROTECTED]
backup won't be done on loaded machine
Hi I have quite serious problem for backup up 2 redhat7.3 machine here One is our mail server and the other one is our mail machine who does the distribution of mail. These machines have quite some partitions to backup. The server is undr RH7.3 too with the amanda2.4.3b3 version. The two faulty machine use 2.4.2p2. On these two machine i got the same symptoms. some partition at the beginning of the schedule get backuped but the others not. I got the following message on the report and in the status file aborted:[request timeout when i go to the client machine i found an amandad defunct process which is directly attached to xinetd. I'm really wondering why this process is in defunct state. This process seems to prevent xinetd to spawn another amandad to make the backup As soon as i restart xinetd the problem vanished. This is not really an issue as i can't restart xinetd during night when backup is done. both machine uses the last version of kernel shiped with redhat. I have loook on the debug file on the /tmp/amanda directory but didn't found something noticeable. Well right now i really don't know what i can do to solve that problem. Has someone already see that kind of problem? Thanks in advance for any help. -- Eric Doutreleau I.N.T | Tel : +33 (0) 160764687 9 rue Charles Fourier | Fax : +33 (0) 160764321 91011 Evry France | email : [EMAIL PROTECTED]
amanda is stuck in the middle of backup
I have a strange problem with amanda my server is a Redhat linux 7.3 machine with amanda 2.4.3b3 my client is a redhat7.3 machine with a stock amanda package from redhat version 2.4.2p2 In my report for this client some backup work and some don't I got the message could not connect to molure for some of the partition. Indeed when i ran amcheck this machine coul'nt be check and i got the same message. When i log on this machine all is running except the fact than xinetd didn't spawn the amandad process. when i do a ps i found an amandad process 15933 ?Z 0:00 [amandad defunct] this process is a son of the xinetd process but when i look at amandad file related to this process all seems ok Here is the end of this file got packet: Amanda 2.4 REQ HANDLE 000-F8B70708 SEQ 1031857221 SECURITY USER dumpy SERVICE sendbackup OPTIONS hostname=molure; GNUTAR /var/spool/imap13 0 1970:1:1:0:0:0 OPTIONS |;bsd-auth;compress-fast;index;exclude-list=/usr/local/lib/amanda/exclude.gtar; sending ack: Amanda 2.4 ACK HANDLE 000-F8B70708 SEQ 1031857221 bsd security: remote host backup.int-evry.fr user dumpy local user amanda amandahosts security check passed amandad: running service /usr/lib/amanda/sendbackup amandad: sending REP packet: Amanda 2.4 REP HANDLE 000-F8B70708 SEQ 1031857221 CONNECT DATA 57421 MESG 57422 INDEX 57423 OPTIONS ;compress-fast;bsd-auth;index; amandad: got packet: Amanda 2.4 ACK HANDLE 000-F8B70708 SEQ 1031857221 amandad: pid 15933 finish time Thu Sep 12 22:17:32 2002 But the prcess stuck seems to prevent the launch of the following backup of different partition on the same machine? if i restart xinetd all run fine again but at the next backup i got again this problem. Has someone already seen that kind of problem? Thanks in advance for any help -- Eric Doutreleau I.N.T | Tel : +33 (0) 160764687 9 rue Charles Fourier | Fax : +33 (0) 160764321 91011 Evry France | email : [EMAIL PROTECTED]
Re: Does Amanda runs on Solaris 8 as a server and/or client??
On Fri, 21 Dec 2001, Desaulniers, Annie wrote: Well I m using it with a solaris 8 server and obviously as a client too Then yes it works :) -- Eric Doutreleau I.N.T | Tel : +33 (0) 160764687 9 rue Charles Fourier | Fax : +33 (0) 160764321 91011 Evry France | email : [EMAIL PROTECTED]
problems with with Amanda-2.4.3b1
Hi I'm currently evaluating the first beta of the 2.4.3beta1 version and i have the following problems with the tape changer. Im under solaris and i use the stc driver with the associate changer script. It works quite well on the 2.4.2p2 version but with the 2.4.3b1 version i got the following error on the amdump file driver: hdisk-state time 22984.326 hdisk 0: free 5480521 dumpers 3 taper: writing end marker. [MCI16 ERR kb 35984768 fm 271] changer: opening pipe to: /usr/local/libexec/stc-changer -info changer: got exit: 0 str: 4 10 1 changer_query: changer return was 10 1 changer_query: searchable = 0 changer_find: looking for MCI17 changer is searchable = 0 changer: opening pipe to: /usr/local/libexec/stc-changer -slot current changer: got exit: 0 str: 4 /dev/rmt/0n taper: slot 4: date 20011214 label MCI16 (active tape) changer: opening pipe to: /usr/local/libexec/stc-changer -slot next changer: got exit: 0 str: 5 /dev/rmt/0n taper: slot 5: date Xlabel MCI17 (exact label match) taper: read label `MCI17' date `X' taper: wrote label `MCI17' date `20011214' driver: result time 23208.351 from taper: QUITTING 00-00549 [writing file: short write] driver: driver received unexpected token (2) from taper taper: DONE [idle wait: 7082.735 secs] taper: writing end marker. [MCI17 OK kb 0 fm 0] amdump: end at Sat Dec 15 03:25:50 MET 2001 dumper: error [bad command after RQ-MORE-DISK: 1] error [bad command after RQ-MORE-DISK: 1] dumper: pid 1093 finish time Sat Dec 15 03:37:24 2001 Has someone already seen this problem between driver and taper? The output of taper seems ok but not for driver Neverthless i will go investigate in the source code Thanks in advance for any help -- Eric Doutreleau I.N.T | Tel : +33 (0) 160764687 9 rue Charles Fourier | Fax : +33 (0) 160764321 91011 Evry France | email : [EMAIL PROTECTED]
Re: problems with with Amanda-2.4.3b1
On Tue, 18 Dec 2001, Jean-Louis Martineau wrote: Hi I will tonight I got the amanda-2.4.3b1-20011214 snapshot Thanks for your quick answer Hello Eric, Could you try the latest snapshot available from http://www.iro.umontreal.ca/~martinea/amanda It should fix this problem. Jean-Louis On Tue, Dec 18, 2001 at 09:21:43AM +0100, Eric Doutreleau wrote: Hi I'm currently evaluating the first beta of the 2.4.3beta1 version and i have the following problems with the tape changer. Im under solaris and i use the stc driver with the associate changer script. It works quite well on the 2.4.2p2 version but with the 2.4.3b1 version i got the following error on the amdump file driver: hdisk-state time 22984.326 hdisk 0: free 5480521 dumpers 3 taper: writing end marker. [MCI16 ERR kb 35984768 fm 271] changer: opening pipe to: /usr/local/libexec/stc-changer -info changer: got exit: 0 str: 4 10 1 changer_query: changer return was 10 1 changer_query: searchable = 0 changer_find: looking for MCI17 changer is searchable = 0 changer: opening pipe to: /usr/local/libexec/stc-changer -slot current changer: got exit: 0 str: 4 /dev/rmt/0n taper: slot 4: date 20011214 label MCI16 (active tape) changer: opening pipe to: /usr/local/libexec/stc-changer -slot next changer: got exit: 0 str: 5 /dev/rmt/0n taper: slot 5: date Xlabel MCI17 (exact label match) taper: read label `MCI17' date `X' taper: wrote label `MCI17' date `20011214' driver: result time 23208.351 from taper: QUITTING 00-00549 [writing file: short write] driver: driver received unexpected token (2) from taper taper: DONE [idle wait: 7082.735 secs] taper: writing end marker. [MCI17 OK kb 0 fm 0] amdump: end at Sat Dec 15 03:25:50 MET 2001 dumper: error [bad command after RQ-MORE-DISK: 1] error [bad command after RQ-MORE-DISK: 1] dumper: pid 1093 finish time Sat Dec 15 03:37:24 2001 Has someone already seen this problem between driver and taper? The output of taper seems ok but not for driver Neverthless i will go investigate in the source code Thanks in advance for any help -- Eric Doutreleau I.N.T | Tel : +33 (0) 160764687 9 rue Charles Fourier | Fax : +33 (0) 160764321 91011 Evry France | email : [EMAIL PROTECTED] -- Eric Doutreleau I.N.T | Tel : +33 (0) 160764687 9 rue Charles Fourier | Fax : +33 (0) 160764321 91011 Evry France | email : [EMAIL PROTECTED]
problems with Amanda-2.4.3b1
Hi I'm currently evaluating the first beta of the 2.4.3beta1 version and i have the following problems with the tape changer. Im under solaris and i use the stc driver with the associate changer script. It works quite well on the 2.4.2p2 version but with the 2.4.3b1 version i got the following error on the amdump file driver: hdisk-state time 22984.326 hdisk 0: free 5480521 dumpers 3 taper: writing end marker. [MCI16 ERR kb 35984768 fm 271] changer: opening pipe to: /usr/local/libexec/stc-changer -info changer: got exit: 0 str: 4 10 1 changer_query: changer return was 10 1 changer_query: searchable = 0 changer_find: looking for MCI17 changer is searchable = 0 changer: opening pipe to: /usr/local/libexec/stc-changer -slot current changer: got exit: 0 str: 4 /dev/rmt/0n taper: slot 4: date 20011214 label MCI16 (active tape) changer: opening pipe to: /usr/local/libexec/stc-changer -slot next changer: got exit: 0 str: 5 /dev/rmt/0n taper: slot 5: date Xlabel MCI17 (exact label match) taper: read label `MCI17' date `X' taper: wrote label `MCI17' date `20011214' driver: result time 23208.351 from taper: QUITTING 00-00549 [writing file: short write] driver: driver received unexpected token (2) from taper taper: DONE [idle wait: 7082.735 secs] taper: writing end marker. [MCI17 OK kb 0 fm 0] amdump: end at Sat Dec 15 03:25:50 MET 2001 dumper: error [bad command after RQ-MORE-DISK: 1] error [bad command after RQ-MORE-DISK: 1] dumper: pid 1093 finish time Sat Dec 15 03:37:24 2001 Has someone already seen this problem between driver and taper? The output of taper seems ok but not for driver Neverthless i will go investigate in the source code Thanks in advance for any help -- Eric Doutreleau [EMAIL PROTECTED] Les signatures les plus courtes sont les signatures les meilleures
Re: problems with with Amanda-2.4.3b1
Hi I just tried it and it solve my problem Thank you very much P.S the autoflush feature is really a cool feature Hello Eric, Could you try the latest snapshot available from http://www.iro.umontreal.ca/~martinea/amanda It should fix this problem. Jean-Louis On Tue, Dec 18, 2001 at 09:21:43AM +0100, Eric Doutreleau wrote: Hi I'm currently evaluating the first beta of the 2.4.3beta1 version and i have the following problems with the tape changer. Im under solaris and i use the stc driver with the associate changer script. It works quite well on the 2.4.2p2 version but with the 2.4.3b1 version i got the following error on the amdump file driver: hdisk-state time 22984.326 hdisk 0: free 5480521 dumpers 3 taper: writing end marker. [MCI16 ERR kb 35984768 fm 271] changer: opening pipe to: /usr/local/libexec/stc-changer -info changer: got exit: 0 str: 4 10 1 changer_query: changer return was 10 1 changer_query: searchable = 0 changer_find: looking for MCI17 changer is searchable = 0 changer: opening pipe to: /usr/local/libexec/stc-changer -slot current changer: got exit: 0 str: 4 /dev/rmt/0n taper: slot 4: date 20011214 label MCI16 (active tape) changer: opening pipe to: /usr/local/libexec/stc-changer -slot next changer: got exit: 0 str: 5 /dev/rmt/0n taper: slot 5: date Xlabel MCI17 (exact label match) taper: read label `MCI17' date `X' taper: wrote label `MCI17' date `20011214' driver: result time 23208.351 from taper: QUITTING 00-00549 [writing file: short write] driver: driver received unexpected token (2) from taper taper: DONE [idle wait: 7082.735 secs] taper: writing end marker. [MCI17 OK kb 0 fm 0] amdump: end at Sat Dec 15 03:25:50 MET 2001 dumper: error [bad command after RQ-MORE-DISK: 1] error [bad command after RQ-MORE-DISK: 1] dumper: pid 1093 finish time Sat Dec 15 03:37:24 2001 Has someone already seen this problem between driver and taper? The output of taper seems ok but not for driver Neverthless i will go investigate in the source code
Re: Overland DLT LoaderXpress LXL1B10
On Tue, 28 Aug 2001, Karl, Matthew wrote: Amanda-users, We have an Overland DLT LoaderXpress LXL1B10, and Amanda (latest) is running on Solaris 7. We are unable to get Amanda to work the autoloader. I have just recently started in this area, so please pardon my ignorance as I do not know exactly what to ask. If anyone has any suggestions they would be greatly appreciated. Thanks in advance for your time and assistance. Regards, Matthew Hi I m planning to use the same config than u except the fact that my server will be on solaris 8. But i would like to know if it works before buying the autoloader I had some contact with overland people and one told me that this changer work well with linux and mtx i guess then you should begin by trying to make mtx work on your solaris machine with your autoloader You can get it at the following url http://mtx.sourceforge.net/ That s the first step -- Eric Doutreleau I.N.T | Tel : +33 (0) 160764687 9 rue Charles Fourier | Fax : +33 (0) 160764321 91011 Evry France | email : [EMAIL PROTECTED]
purchasing a new changer
Hello I would like to purchase a new changer and i m wondering what kind of changer is already used by amanda user. I m especially interested in Overland DLT LXL LoadXpress with DLT1 tape Feel free to answer to me and i will summarize your answer to the list Thanks in advance -- Eric Doutreleau I.N.T | Tel : +33 (0) 160764687 9 rue Charles Fourier | Fax : +33 (0) 160764321 91011 Evry France | email : [EMAIL PROTECTED]
