Re: amrecove does not connect
On Tue, 27 Nov 2007 08:11:35 +0100 Marc Muehlfeld [EMAIL PROTECTED] wrote: Charles Stroom schrieb: fiume:~ # amrecover -s fiume AMRECOVER Version 2.5.2p1. Contacting server on fiume ... [request failed: timeout waiting for ACK] Run amcheck and have a look for errors. fiume:/tmp/amanda/client # su - amandabackup -c exec amcheck daily Amanda Tape Server Host Check - Holding disk /work-2/amanda/dumps: 106816016 KB disk space available, using 106713616 KB Opening tapedev /dev/nst0: got error Input/output error. tape_rdlabel: tape open: /dev/nst0: Input/output error (expecting tape daily-07 or a new tape) Server check took 121.756 seconds Amanda Backup Client Hosts Check Client check: 2 hosts checked in 0.483 seconds, 0 problems found (brought to you by Amanda 2.5.2p1) Seems ok to me! No tape (yet) in drive but both PC's respond. Anyhow, backups run normal. Has this anything to do with the 3 files in the xinet.d directory amanda, amandaidx, amidxtape? Are the services running? Check with netstat -taunp | grep :1008. on your backup/index server. fiume:/tmp/amanda/client # netstat -taunp | grep :1008 tcp0 0 0.0.0.0:10080 0.0.0.0:* LISTEN 4415/xinetd tcp0 0 0.0.0.0:10082 0.0.0.0:* LISTEN 4415/xinetd tcp0 0 0.0.0.0:10083 0.0.0.0:* LISTEN 4415/xinetd Seems OK, no? Must a user root added somewhere? No. Amanda runs as user. You configured amandabackup:disk for this. But this is what I don't understand. Amanda backup runs as user amandabackup, but amrecover must run as root! I do not fully understand the xinet workings, but I suppose that it specifies that services (like amindexd) start running if the right user requests its service. But in the 3 xinet.d files (included in my first email), root is not specified as one of the users of the amanda services amanda, amandaidx and amidxtape. If I do an amrecover, and, while it times-out, I do an ps -ef | grep am, I do not see any of these amanda services coming up. Regards, Charles Marc -- Charles Stroom email: charles at no-spam.stremen.xs4all.nl (remove the no-spam.)
Re: add option --occurrence to gnutar amrecover command [Was: Re: Problems accessing my new autoloader]
I tested it, and tar doesn't exit after the first occurrence. Maybe because it read from a pipe. Anyway, amidxtaped will read the complete image from tape, decompress it, send it to amrecover. amrecover will fail because tar would have exited. Jean-Louis Paul Bijnens wrote: On 2007-11-23 09:35, Francis Galiegue wrote: Le Friday 23 November 2007 09:17:01 Marc Muehlfeld, vous avez écrit : One additional info to my last mail (sorry. I just replied to the sender, and not to the list, thats why I let it below): 5 Minutes after I send this mail, the silent amrecover finished it's work and the files where recovered. But why does it take 45 minutes to restore one 45kb file? On the tape were just 9.1 GB in 60 files, so it should be finished fast. Also its a fast LTO3 drive connected to a fast Adaptec 29160 SCSI card Tar will unroll ALL the archive to find your file. Not sure why it doesn't stop if it finds the file at the beginning/middle of the archive though. Because a file can appear multiple times in a tar archive, and the normal semantics says that it needs the last version, unless specified on the command line. In gnutar you may store files multiple times in an archive. e.g. $ gtar -cf /tmpk/multi.tar file1 file1 file1 $ gtar -tf /tmp/multi.tar and note the file appears 3 times. You can even append to an existing archive: $ date file1 $ gtar -rf /tmp/multi.tar file1 and when you restore, you get last version only. Or be more specific about a specific occurrence: $ gtar --occurrence=3 -tvf /tmp/multi.tar Amanda will *not* store multiple files in a tar archive, and we could add indeed the option --occurrence (the default=1) for extracting with amrecover and then, according to the info page, gnutar will terminate without scanning to the end of the archive. This could speed up the restore process considerably for the few files restores, the most frequent requests. So the default restore command would become: gtar --occurrence --numeric-owner --xpGvf - extractlist Patch against 2.5.2p1: file recover-src/extract_list.c: --- extract_list.c_ORIG 2007-11-23 10:17:22.0 +0100 +++ extract_list.c 2007-11-23 10:18:36.0 +0100 @@ -1773,7 +1773,7 @@ #endif case IS_TAR: case IS_GNUTAR: -extra_params = 4; +extra_params = 5; break; case IS_SAMBA_TAR: extra_params = 3; @@ -1824,6 +1824,7 @@ case IS_TAR: case IS_GNUTAR: restore_args[j++] = stralloc(tar); + restore_args[j++] = stralloc(--occurrence); /* do not scan the rest of the archive if file found once */ restore_args[j++] = stralloc(--numeric-owner); restore_args[j++] = stralloc(-xpGvf); restore_args[j++] = stralloc(-); /* data on stdin */
Re: amrecove does not connect
Charles Stroom schrieb: Must a user root added somewhere? No. Amanda runs as user. You configured amandabackup:disk for this. But this is what I don't understand. Amanda backup runs as user amandabackup, but amrecover must run as root! You have to run amrecover as root, to make sure, that not everybody who has a shell account can connect to your backup server and restore files. But the services on your backup server run as $USER/$GROUP. Programs on the server that have to run with root privileges by $USER are set suid. I do not fully understand the xinet workings, but I suppose that it specifies that services (like amindexd) start running if the right user requests its service. When somebody connect to one of the xinetd ports, then xinetd start the configured program. If no one is connected, you will see no amanda processes running in your ps output. But if, then you will. If I do an amrecover, and, while it times-out, I do an ps -ef | grep am, I do not see any of these amanda services coming up. If you don't see any processes (ps) or connection (netstat) on your server, then I guess, the client can't reach the server out of any reasons. Maybe a firewall issue on your client or on a firewall between the machines, that don't allow the connection to your server. Also it could be a name resolution problem and the client doesn't or does wrong resolve your servers name. You can check the amrecover.*.debug logfiles on you client for additional information, too. Marc -- Marc Muehlfeld (Leitung Systemadministration) Zentrum fuer Humangenetik und Laboratoriumsmedizin Dr. Klein und Dr. Rost Lochhamer Str. 29 - D-82152 Martinsried Telefon: +49(0)89/895578-0 - Fax: +49(0)89/895578-78 http://www.medizinische-genetik.de
Re: Trying to backup to disk, getting dump to tape failed, will try again
Jennifer Luisi schrieb: /export/amanda/vtapes/tape1/slots: total 44 lrwxrwxrwx 1 amanda disk 39 Nov 26 13:53 data - /export/amanda/vtapes/tape1/slots/slot4 -rw--- 1 amanda disk 11 Nov 26 13:53 info drwxr-xr-x 2 amanda disk 4096 Nov 26 12:38 slot1 [...] You seem to have mixed some terms, leading to a slightly unusual directory structure. Maybe get this done first. See for example http://www.amanda.org/docs/howto-filedriver.html#id333812 especially Step 6 for an example how the dirs should look like. You have tapedev file:/export/amanda/vtapes/tape1/slots For example: Why call it tape1 ? Your config is called OrgName ... Check amdump.1 for details, you should find it in /export/amanda/adm/BlueFrog (according to your cfg). Post parts of it here if needed. Greets, Stefan
Re: Trying to backup to disk, getting dump to tape failed, will try again
On Tue, Nov 27, 2007 at 09:42:30AM -0500, Jennifer Luisi wrote:
Hi there,
I'm new to Amanda and am trying to get a disk-to-disk backup going.
When I run amcheck, everything seems fine. Then, when I run amdump,
nothing ever gets written to disk (virtual tape). The amanda log file
shows:
SUCCESS taper [hostname] /export/backup 20071126 0 [sec 188.985 kb 0 kps
0.0 {wr: writers 0 rdwait 188.984 wrwait 0.000 filemark 0.000}]
INFO driver [hostname] /export/backup 0 [dump to tape failed, will try
again]
I've googled and read docs and how-to's to get where I am now.
Unfortunately, all the docs and how-to's get me to running amcheck
without errors and then launch into how to start a recovery process. I
guess that means that most people have no problems with amdump. ;-)
I've included config info below, amanda.conf, disklist, etc. Please
take a look and let me know what silly error I've made. I'd really
appreciate it. If I've left out some pertinent info, please tell me and
I'll include it.
Thanks!!
Not sure that any of my comments will fix your problem,
but I just include a few notes.
My amanda.conf file is
org OrgName # your organization name for reports
dumpuser amanda # the user to run dumps under
inparallel 4 # maximum dumpers that will run in parallel
dumpcycle 14 # the number of days in the normal dump cycle
runspercycle 10 # the number of amdump runs in dumpcycle days
etimeout 55 # number of seconds per filesystem for estimates.
55 seconds to do a estimate is VERY short. Some who use tar
and have it traverse the file system need hours (N * 3600)
runtapes 1 # number of tapes to be used in a single run of amdump
tapetype HARDDISK # what kind of tape it is (see tapetypes below)
labelstr ^OrgName-[0-9][0-9]*$ # label constraint regex: all tapes
must match
tapecycle 11
That is a bare minimum. You will essentially have no redundancy.
And if things mess up two days in a row, you will have lost some
of your only full dumps.
tpchanger chg-disk
changerfile /export/amanda/status/chg-disk-status # status files prefix
tapedev file:/export/amanda/vtapes/tape1/slots
infofile /export/amanda/adm/BlueFrog/curinfo # database filename
logdir /export/amanda/adm/BlueFrog # log directory
indexdir /export/amanda/adm/BlueFrog/index# index directory
define tapetype HARDDISK {
comment Dump onto hard disk
length 40960 mbytes
}
11 tapes by 40 GB, I presume this is a 500GB disk?
Maybe external?
define dumptype global {
index yes
program GNUTAR
exclude list /var/lib/amanda/exclude.gtar
# record no
If you don't allow recording, you can't use amrecover
to retrieve individual files convienently.
Whoops, that indexing, ignore above comment.
If you don't record your dumps, amanda will always
think you need a level 0 dump. It will not have a
record of previous dump levels.
}
define dumptype hard-disk-dump {
global
comment Back up to hard disk instead of tape using dump
holdingdisk no
A holding disk is still useful to speed things up by allowing
multiple dumps in parallel to the holding disk. Without a
hold disk, you can only dump one DLE at a time and that may
be speed constrained by the network or other factors.
index yes
priority high
kencrypt no
program GNUTAR
}
define interface vbeb {
comment 10 Mbps ethernet over the vbeb
use 800 kbps
}
And my test disklist file looks like this:
client.host /etc hard-disk-dump -1 vbeb
client.host /export/backup hard-disk-dump -1 vbeb
client.host /export/subversion hard-disk-dump -1 vbeb
client.host /export/httpd/beta-webspaces hard-disk-dump -1 vbeb
client.host /export/httpd/swc.bluefrog hard-disk-dump -1 vbeb
I have my virtual tapes set up and labeled:
[EMAIL PROTECTED] ~]# ls -lR /export/amanda/vtapes/ | more
/export/amanda/vtapes/:
total 4
drwxr-x--- 4 amanda disk 4096 Nov 26 10:41 tape1
/export/amanda/vtapes/tape1:
total 12
drwxr-xr-x 2 amanda disk 4096 Nov 23 13:19 data
-rw--- 1 amanda disk 11 Nov 23 13:19 info
drwxr-xr-x 12 amanda disk 4096 Nov 26 13:53 slots
/export/amanda/vtapes/tape1/data:
total 0
/export/amanda/vtapes/tape1/slots:
total 44
lrwxrwxrwx 1 amanda disk 39 Nov 26 13:53 data -
/export/amanda/vtapes/tape1/slots/slot4
-rw--- 1 amanda disk 11 Nov 26 13:53 info
drwxr-xr-x 2 amanda disk 4096 Nov 26 12:38 slot1
drwxr-xr-x 2 amanda disk 4096 Nov 26 10:51 slot10
drwxr-xr-x 2 amanda disk 4096 Nov 26 13:29 slot2
drwxr-xr-x 2 amanda disk 4096 Nov 26 13:51 slot3
drwxr-xr-x 2 amanda disk 4096 Nov 26 15:12 slot4
drwxr-xr-x 2 amanda disk 4096 Nov 26 10:49 slot5
drwxr-xr-x 2 amanda disk 4096 Nov 26 10:51 slot6
drwxr-xr-x 2 amanda disk 4096 Nov 26 10:51 slot7
drwxr-xr-x 2 amanda disk 4096 Nov 26 10:51 slot8
drwxr-xr-x 2 amanda disk 4096 Nov 26 11:40 slot9
Can you manipulate your vtapes with various sub-commands
of amtape?
--
Jon H.
Re: Trying to backup to disk, getting dump to tape failed, will try again
What's the error message in the email report?
Jennifer Luisi wrote:
Hi there,
I'm new to Amanda and am trying to get a disk-to-disk backup going.
When I run amcheck, everything seems fine. Then, when I run amdump,
nothing ever gets written to disk (virtual tape). The amanda log file
shows:
SUCCESS taper [hostname] /export/backup 20071126 0 [sec 188.985 kb 0
kps 0.0 {wr: writers 0 rdwait 188.984 wrwait 0.000 filemark 0.000}]
INFO driver [hostname] /export/backup 0 [dump to tape failed, will try
again]
What's the dumper result for the disk?
Jean-Louis
Re: IBM 3584 and mtx?
So from the lack of replies I gather that I'm alone on this... jf * Jean-Francois Malouin [EMAIL PROTECTED] [20071123 10:50]: Hi, Really this does not pertain to the amanda list but before I go deeper in my search I was wondering if anyone has any experience and recommendations wrt to an IBM 3584 tape library: is it possible to drive the robot with mtx? Comes with 9 LTO-2 FC tape drives and I could get it cheap... thanks! jf -- ° -- °
Re: amrecove does not connect
your amanda service is configured for bsdtcp auth, which auth are you
using in amrecover, the default is 'bsd', you can set it in
amanda-client.conf or using '-oauth=bsdtcp' as argument to amrecover.
Jean-Louis
Charles Stroom wrote:
Hi all,
today I tried to restore a couple of files, but amrecover failed to
connect to the index server (I believe). This is on my server PC fiume:
fiume:~ # amrecover -s fiume
AMRECOVER Version 2.5.2p1. Contacting server on fiume ...
[request failed: timeout waiting for ACK]
Backups work perfectly with user amandabackup (this is the precompiled
Opensuse 10.2 version). Amrecover was done as root.
Has this anything to do with the 3 files in the xinet.d directory
amanda, amandaidx, amidxtape? Must a user root added somewhere?
Their contents is:
---
amanda
---
# description: amanda backup services
service amanda
{
only_from = fiume.localnet stremen.localnet
socket_type = stream
protocol= tcp
wait= no
user= amandabackup
group = disk
groups = yes
server = /usr/lib/amanda/amandad
server_args = -auth=bsdtcp amdump amindexd amidxtaped
disable = no
}
amandaidx
service amandaidx
{
socket_type = stream
protocol= tcp
wait= no
user= amandabackup
group = disk
groups = yes
server = /usr/lib/amanda/amindexd
}
amidxtape
# $Id: amidxtape,v 1.3 2006/08/04 19:45:50 root Exp $
#
service amidxtape
{
socket_type = stream
protocol= tcp
wait= no
user= amandabackup
group = disk
groups = yes
server = /usr/lib/amanda/amidxtaped
}
-
Any help is appreciated.
Regards,
Re: IBM 3584 and mtx?
Jean-Francois Malouin wrote: So from the lack of replies I gather that I'm alone on this... It probably just means nobody on the list has an IBM 3584. However, the top link on a Google search for IBM 3584 mtx returned a page with this link: http://www.ibm.com/developerworks/forums/message.jspa?messageID=13745192 I reached IBM 3584 functions through mtx prog such as mtx -f /dev/sg1 status (all the other options work fine as well). I compiled kernel 2.6.12 with sg (scsi generic and (scsi tape)st. It works well with amanda backup system. I don't use IBMtape.o. Frank jf * Jean-Francois Malouin [EMAIL PROTECTED] [20071123 10:50]: Hi, Really this does not pertain to the amanda list but before I go deeper in my search I was wondering if anyone has any experience and recommendations wrt to an IBM 3584 tape library: is it possible to drive the robot with mtx? Comes with 9 LTO-2 FC tape drives and I could get it cheap... thanks! jf -- ° -- Frank Smith [EMAIL PROTECTED] Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: Trying to backup to disk, getting dump to tape failed, will try again
I don't know why the backup seems to hang. Nothing say the problem is with the vtape. Post the dumper.*.debug, taper.*.debug, amdump.1 and log.200711... files Alos post the amandad.*.debug file from the client. Jean-Louis Jennifer Luisi wrote: Jean-Louis Martineau wrote: What's the dumper result for the disk? Jean-Louis Where can I find the dumper result? Since the backup just seems to hang with the dump to tape failed errors, I haven't actually been letting it complete. I've given it up to an hour or so and then killed it. The email report says: *** THE DUMPS DID NOT FINISH PROPERLY! again, this is probably because I killed them. How long should amanda be running before it completes? I've got my disklist down to one host and one very small directory and I'm still not able to get any data written to my tape/disk. Thanks, Jen
Re: Trying to backup to disk, getting dump to tape failed, will try again
I think I'm getting closer to the problem. There seems to be a
connection issue between my server and client. If anyone has any input,
I'd appreciate it. I've got iptables on my client set up to accept port
10080 connections from my server, and it's obviously talking a bit since
I have logs on my client. So...?
Taking a closer look at the amdump log on my backup server, I see:
snip
GENERATING SCHEDULE:
ENDFLUSH
DUMP [client.host] feff9ffe0f /etc 20071127 13847 0 1970:1:1:0:0:0
3035 101
reserving 0 out of 0 for degraded-mode dumps
driver: flush size 0
driver: start time 0.099 inparallel 4 bandwidth 3100 diskspace 0 dir
OBSOLETE datestamp 20071127 driver: drain-ends tapeq FIRST big-dumpers ttt
driver: result time 0.099 from taper: TAPER-OK
driver: dumping [client.host]:/etc directly to tape
driver: send-cmd time 0.099 to taper: PORT-WRITE 00-1 [client.host]
feff9ffe0f /etc 0 20071127
taper: try_socksize: receive buffer size is 65536
taper: stream_server: waiting for connection: 0.0.0.0.33284
driver: result time 0.099 from taper: PORT 33284
driver: send-cmd time 0.099 to dumper0: PORT-DUMP 01-2 33284
[client.host] feff9ffe0f /etc NODEVICE 0 1970:1:1:0:0:0 GNUTAR
|;bsd-auth;compress-fast;index;exclude-list=/var/lib/amanda/exclude.gtar;
driver: state time 0.099 free kps: 3070 space: 0 taper: writing
idle-dumpers: 3 qlen tapeq: 0 runq: 0 roomq: 0 wakeup: 86400
driver-idle: not-idle
driver: interface-state time 0.099 if : free 300 if VBEB: free 770 if
ETH0: free 1000 if LOCAL: free 1000
driver: hdisk-state time 0.099
taper: stream_accept: connection from 127.0.0.1.3328dutaper:
try_socksize: receive buffer size is 327dumper: try_socksize: send
buffer size is 65536
dumper: stream_client: connect to 10.0.82.134.53380 failed: Connection
timed out
driver: result time 189.086 from dumper0: TRY-AGAIN 01-2 could not
connect to data port: Connection timed out
On the client-side, I found the following in my sendbackup.*.debug file:
sendbackup: debug 1 pid 30171 ruid 33 euid 33: start at Tue Nov 27
11:49:37 2007/usr/lib/amanda/sendbackup: version 2.4.4p3
parsed request as: program `GNUTAR'
disk `/etc'
device `/etc'
level 0
since 1970:1:1:0:0:0
options
`|;bsd-auth;compress-fast;index;exclude-list=/var/lib/amanda/exclude.gtar;'
sendbackup: try_socksize: send buffer size is 65536
sendbackup: time 0.000: stream_server: waiting for connection: 0.0.0.0.54035
sendbackup: time 0.000: stream_server: waiting for connection: 0.0.0.0.54036
sendbackup: time 0.000: stream_server: waiting for connection: 0.0.0.0.54037
sendbackup: time 0.000: waiting for connect on 54035, then 54036, then 54037
sendbackup: time 29.992: stream_accept: timeout after 30 seconds
sendbackup: time 29.992: timeout on data port 54035
sendbackup: time 59.984: stream_accept: timeout after 30 seconds
sendbackup: time 59.985: timeout on mesg port 54036
sendbackup: time 89.976: stream_accept: timeout after 30 seconds
sendbackup: time 89.977: timeout on index port 54037
sendbackup: time 89.977: pid 30171 finish time Tue Nov 27 11:51:07 2007
The amandad.*.debug file says:
amandad: debug 1 pid 30170 ruid 33 euid 33: start at Tue Nov 27 11:49:37
2007
amandad: version 2.4.4p3
amandad: build: VERSION=Amanda-2.4.4p3
snip
Amanda 2.4 REQ HANDLE 000-F03E6008 SEQ 1196180673
SECURITY USER amanda
SERVICE sendbackup
OPTIONS features=feff9ffe0f;hostname=client.host;
GNUTAR /etc 0 1970:1:1:0:0:0 OPTIONS
|;bsd-auth;compress-fast;index;exclude-list=/var/lib/amanda/exclude.gtar;
amandad: time 0.000: sending ack:
Amanda 2.4 ACK HANDLE 000-F03E6008 SEQ 1196180673
amandad: time 0.002: bsd security: remote host backup.server.com user
amanda local user amanda
amandad: time 0.002: amandahosts security check passed
amandad: time 0.002: running service /usr/lib/amanda/sendbackup
amandad: time 0.006: sending REP packet:
Amanda 2.4 REP HANDLE 000-F03E6008 SEQ 1196180673
CONNECT DATA 54035 MESG 54036 INDEX 54037
OPTIONS features=feff9ffe0f;
amandad: time 0.006: got packet:
Amanda 2.4 ACK HANDLE 000-F03E6008 SEQ 1196180673
amandad: time 0.006: pid 30170 finish time Tue Nov 27 11:49:37 2007
Thanks!!!
Jen
Jennifer Luisi wrote:
Hi there,
I'm new to Amanda and am trying to get a disk-to-disk backup going.
When I run amcheck, everything seems fine. Then, when I run amdump,
nothing ever gets written to disk (virtual tape). The amanda log file
shows:
SUCCESS taper [hostname] /export/backup 20071126 0 [sec 188.985 kb 0
kps 0.0 {wr: writers 0 rdwait 188.984 wrwait 0.000 filemark 0.000}]
INFO driver [hostname] /export/backup 0 [dump to tape failed, will try
again]
I've googled and read docs and how-to's to get where I am now.
Unfortunately, all the docs and how-to's get me to running amcheck
without errors and then launch into how to start
planner timeout
Hi, I have been running into problems that some of my systems are heavily used for long computations making them somewhat less responsive. Last night I ran into the issue that four systems did not send acknowledgments back to the dumper on time during the planning process: planner: ERROR Request to werner.richmond.edu failed: timeout waiting for ACK I looked into allowing more time for that stage, which I believe etimeout should allow, but my amanda.conf has 'etimeout 600' in it while the planner's debug file ends with: security_seterror(handle=0x3038a0, driver=0xa2a0c (BSD) error=timeout waiting for ACK) security_close(handle=0x3038a0, driver=0xa2a0c (BSD)) planner: time 29.898: pid 3734 finish time Tue Nov 27 00:45:36 2007 suggesting that it still only waits for 30 seconds. Am I setting the wrong timeout? I am running Amanda version 2.5.1p1 on RH WS4 systems, with the backup server a Mac OS X box. Any help is appreciated. Cheers, René
Re: Trying to backup to disk, getting dump to tape failed, will try again
Jennifer Luisi schrieb: I think I'm getting closer to the problem. There seems to be a connection issue between my server and client. If anyone has any input, I'd appreciate it. I've got iptables on my client set up to accept port 10080 connections from my server, and it's obviously talking a bit since I have logs on my client. So...? That's important information, having a fw in between ... Amanda needs more ports than only 10080. Maybe this helps: http://www.amanda.org/docs/faq.html#id347232 http://wiki.zmanda.com/index.php/How_To:Set_Up_iptables_for_Amanda For a start you could simply try to dump a DLE on the server itself, this would let you know if your basic vtape-setup/server-setup works, after that solve the fw-issues. Stefan
Re: Trying to backup to disk, getting dump to tape failed, will try again
Okay, I figured out what my silly little problem was. Apparently, you need to turn on amanda on your server before anything will work. It's interesting that there isn't a useful error to point out such a basic lack. Amcheck was happy and the logs just had connection timeout errors. The timeout errors are certainly logical, they just encompass a lot more than, Hey, you, start the software! Anyway, thanks for all the responses. I am going to go enjoy my working amanda config and try to forget the last several hours. :-/ Jen Jennifer Luisi wrote: I think I'm getting closer to the problem. There seems to be a connection issue between my server and client. If anyone has any input, I'd appreciate it. I've got iptables on my client set up to accept port 10080 connections from my server, and it's obviously talking a bit since I have logs on my client. So...? Taking a closer look at the amdump log on my backup server, I see: snip GENERATING SCHEDULE: ENDFLUSH DUMP [client.host] feff9ffe0f /etc 20071127 13847 0 1970:1:1:0:0:0 3035 101 reserving 0 out of 0 for degraded-mode dumps driver: flush size 0 driver: start time 0.099 inparallel 4 bandwidth 3100 diskspace 0 dir OBSOLETE datestamp 20071127 driver: drain-ends tapeq FIRST big-dumpers ttt driver: result time 0.099 from taper: TAPER-OK driver: dumping [client.host]:/etc directly to tape driver: send-cmd time 0.099 to taper: PORT-WRITE 00-1 [client.host] feff9ffe0f /etc 0 20071127 taper: try_socksize: receive buffer size is 65536 taper: stream_server: waiting for connection: 0.0.0.0.33284 driver: result time 0.099 from taper: PORT 33284 driver: send-cmd time 0.099 to dumper0: PORT-DUMP 01-2 33284 [client.host] feff9ffe0f /etc NODEVICE 0 1970:1:1:0:0:0 GNUTAR |;bsd-auth;compress-fast;index;exclude-list=/var/lib/amanda/exclude.gtar; driver: state time 0.099 free kps: 3070 space: 0 taper: writing idle-dumpers: 3 qlen tapeq: 0 runq: 0 roomq: 0 wakeup: 86400 driver-idle: not-idle driver: interface-state time 0.099 if : free 300 if VBEB: free 770 if ETH0: free 1000 if LOCAL: free 1000 driver: hdisk-state time 0.099 taper: stream_accept: connection from 127.0.0.1.3328dutaper: try_socksize: receive buffer size is 327dumper: try_socksize: send buffer size is 65536 dumper: stream_client: connect to 10.0.82.134.53380 failed: Connection timed out driver: result time 189.086 from dumper0: TRY-AGAIN 01-2 could not connect to data port: Connection timed out On the client-side, I found the following in my sendbackup.*.debug file: sendbackup: debug 1 pid 30171 ruid 33 euid 33: start at Tue Nov 27 11:49:37 2007/usr/lib/amanda/sendbackup: version 2.4.4p3 parsed request as: program `GNUTAR' disk `/etc' device `/etc' level 0 since 1970:1:1:0:0:0 options `|;bsd-auth;compress-fast;index;exclude-list=/var/lib/amanda/exclude.gtar;' sendbackup: try_socksize: send buffer size is 65536 sendbackup: time 0.000: stream_server: waiting for connection: 0.0.0.0.54035 sendbackup: time 0.000: stream_server: waiting for connection: 0.0.0.0.54036 sendbackup: time 0.000: stream_server: waiting for connection: 0.0.0.0.54037 sendbackup: time 0.000: waiting for connect on 54035, then 54036, then 54037 sendbackup: time 29.992: stream_accept: timeout after 30 seconds sendbackup: time 29.992: timeout on data port 54035 sendbackup: time 59.984: stream_accept: timeout after 30 seconds sendbackup: time 59.985: timeout on mesg port 54036 sendbackup: time 89.976: stream_accept: timeout after 30 seconds sendbackup: time 89.977: timeout on index port 54037 sendbackup: time 89.977: pid 30171 finish time Tue Nov 27 11:51:07 2007 The amandad.*.debug file says: amandad: debug 1 pid 30170 ruid 33 euid 33: start at Tue Nov 27 11:49:37 2007 amandad: version 2.4.4p3 amandad: build: VERSION=Amanda-2.4.4p3 snip Amanda 2.4 REQ HANDLE 000-F03E6008 SEQ 1196180673 SECURITY USER amanda SERVICE sendbackup OPTIONS features=feff9ffe0f;hostname=client.host; GNUTAR /etc 0 1970:1:1:0:0:0 OPTIONS |;bsd-auth;compress-fast;index;exclude-list=/var/lib/amanda/exclude.gtar; amandad: time 0.000: sending ack: Amanda 2.4 ACK HANDLE 000-F03E6008 SEQ 1196180673 amandad: time 0.002: bsd security: remote host backup.server.com user amanda local user amanda amandad: time 0.002: amandahosts security check passed amandad: time 0.002: running service /usr/lib/amanda/sendbackup amandad: time 0.006: sending REP packet: Amanda 2.4 REP HANDLE 000-F03E6008 SEQ 1196180673 CONNECT DATA 54035 MESG 54036 INDEX 54037 OPTIONS features=feff9ffe0f; amandad: time 0.006: got packet: Amanda 2.4 ACK HANDLE 000-F03E6008 SEQ 1196180673 amandad: time 0.006: pid 30170 finish time Tue Nov 27 11:49:37 2007 Thanks!!! Jen Jennifer Luisi wrote: Hi there, I'm new to Amanda and am trying to get a disk
Re: IBM 3584 and mtx?
* Frank Smith [EMAIL PROTECTED] [20071127 12:05]: Jean-Francois Malouin wrote: So from the lack of replies I gather that I'm alone on this... It probably just means nobody on the list has an IBM 3584. However, the top link on a Google search for IBM 3584 mtx returned a page with this link: good god, I could I miss this one!?! Thanks jf http://www.ibm.com/developerworks/forums/message.jspa?messageID=13745192 I reached IBM 3584 functions through mtx prog such as mtx -f /dev/sg1 status (all the other options work fine as well). I compiled kernel 2.6.12 with sg (scsi generic and (scsi tape)st. It works well with amanda backup system. I don't use IBMtape.o. Frank jf * Jean-Francois Malouin [EMAIL PROTECTED] [20071123 10:50]: Hi, Really this does not pertain to the amanda list but before I go deeper in my search I was wondering if anyone has any experience and recommendations wrt to an IBM 3584 tape library: is it possible to drive the robot with mtx? Comes with 9 LTO-2 FC tape drives and I could get it cheap... thanks! jf -- ° -- Frank Smith [EMAIL PROTECTED] Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501 -- °
Re: [Mtx-general] mtx error, used with amanda
I didn't see any (other) replies from either list but continued to look over the problem myself. What I now have is the following... I'm running the 1.3.7 binary and using a glue script that I have been running for some time, modified by Joe Rhett [EMAIL PROTECTED] to run with mtx 1.2.9 by Eric Lee Green http://mtx.sourceforge.net I modified the shell to use ksh rather than sh, mirroring changes on the box running Solaris 9 with MTX 1.2.17rel and also using both a C2/LTO3 and L9/LTO. The E250, the new amanda server is working correctly with mtx with the exception that I can not use # amtape update with one of the two configurations. Fortunately I seem to be able to use # amcheck, amlabel properly and as long as amdump runs we will be fine, as the C2, where amtape udpate is failing has a static tape pool. I'll let the list know how it all works out. On Mon, Nov 19, 2007 at 04:07:50PM -0500, Brian Cuttler wrote: Craig, On Tue, Nov 20, 2007 at 07:51:00AM +1100, Craig Dewick wrote: On Mon, 19 Nov 2007, Brian Cuttler wrote: Platform, Solaris 9, Amanda 2.4.4, MTX 1.3.9 Nope, not fixed, here are updated logs, any help would be apreciated. Oddly... we seem ok on the C2 jukebox but not the L9, same software on the same machine. Not even matching machines, two amanda configs on the same box (one runs weekdays and the other saturdays). Actually, it seems that mtx is doing its job, and a subsequent command to access the tape or robot shows that things completed successfully, however there is something wrong with amanda or the amanda/mtx interface. (but its the same amanda and glue for both configs...) Could it be some sort of unidentified race condition with the amanda library functions and mtx attempting to access some resource at the same time without any way of preventing overlapping access attempts from colliding into each other along the way? I (successfully) ran the same L9 (apparently the same one you have) on my v280R and the other E250 next to this E250 and had no problems. I'm not running the amanda configs at the same time... I'd think scripts or binaries, but the C2 on the same box is working ok. Just not sure where to look. My tape host system is a similar config (Sol 9 on Ultra 2, Amanda 2.5.2, mtx 1.3.11 talking to a Sun-badged L9 array) and it's been operating fine since all the issues with devices, and configuration were resolved. Craig. PS. I'm getting a new cleaning tape for my L9 this week and wondered if anyone has thought more about how to get cleaning tape usage incorporated into the Amanda schema somehow? I have left a spare slot in the array cartridge for the cleaning tape to sit in. The tape config file in the amanda config directory has options for cleaning slot and tape count between cleanings, is that what you are thinking of ? --- Brian R Cuttler [EMAIL PROTECTED] Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773 --- Brian R Cuttler [EMAIL PROTECTED] Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773 IMPORTANT NOTICE: This e-mail and any attachments may contain confidential or sensitive information which is, or may be, legally privileged or otherwise protected by law from further disclosure. It is intended only for the addressee. If you received this in error or from someone who was not authorized to send it to you, please do not distribute, copy or use it or any attachments. Please notify the sender immediately by reply e-mail and delete this from your system. Thank you for your cooperation.
Re: Trying to backup to disk, getting dump to tape failed, will try again
Jennifer Luisi schrieb: Okay, I figured out what my silly little problem was. Apparently, you need to turn on amanda on your server before anything will work. An interesting observation: software has to be started to work ;) It's interesting that there isn't a useful error to point out such a basic lack. Amcheck was happy and the logs just had connection timeout errors. The timeout errors are certainly logical, they just encompass a lot more than, Hey, you, start the software! Maybe you could let us know what kind of info would have helped you to start the software before contacting the list? It is always possible to improve the documentation. Thanks, Stefan
Re: amrecove does not connect
I tried Jean-Louis's suggestion:
fiume:~ # amrecover -oauth=bsdtcp
AMRECOVER Version 2.5.2p1. Contacting server on localhost ...
[request failed: recv error: Connection reset by peer]
the reply is different now and instantaneous. So I checked a bit
further and my amanda-conf file did have the auth = bsdtcp line
already in. So after some more trials I did:
fiume:~ # amrecover daily
AMRECOVER Version 2.5.2p1. Contacting server on fiume.localnet ...
220 fiume AMANDA index server (2.5.2p1) ready.
Setting restore date to today (2007-11-27)
.
and netstat -taunp | grep :1008 show the established connections.
So, it was the daily argument that was missing and did the trick.
My problem is solved, thanks. I am still a bit puzzled what the line:
conf daily# your config name
means in my amanda-conf file. Would that not set daily as the
default?
Again, thanks for the various replies.
Regards,
Charles
On Tue, 27 Nov 2007 11:13:33 -0500
Jean-Louis Martineau [EMAIL PROTECTED] wrote:
your amanda service is configured for bsdtcp auth, which auth are you
using in amrecover, the default is 'bsd', you can set it in
amanda-client.conf or using '-oauth=bsdtcp' as argument to amrecover.
Jean-Louis
Charles Stroom wrote:
Hi all,
today I tried to restore a couple of files, but amrecover failed to
connect to the index server (I believe). This is on my server PC
fiume:
fiume:~ # amrecover -s fiume
AMRECOVER Version 2.5.2p1. Contacting server on fiume ...
[request failed: timeout waiting for ACK]
Backups work perfectly with user amandabackup (this is the
precompiled Opensuse 10.2 version). Amrecover was done as root.
Has this anything to do with the 3 files in the xinet.d directory
amanda, amandaidx, amidxtape? Must a user root added somewhere?
Their contents is:
---
amanda
---
# description: amanda backup services
service amanda
{
only_from = fiume.localnet stremen.localnet
socket_type = stream
protocol= tcp
wait= no
user= amandabackup
group = disk
groups = yes
server = /usr/lib/amanda/amandad
server_args = -auth=bsdtcp amdump amindexd amidxtaped
disable = no
}
amandaidx
service amandaidx
{
socket_type = stream
protocol= tcp
wait= no
user= amandabackup
group = disk
groups = yes
server = /usr/lib/amanda/amindexd
}
amidxtape
# $Id: amidxtape,v 1.3 2006/08/04 19:45:50 root Exp $
#
service amidxtape
{
socket_type = stream
protocol= tcp
wait= no
user= amandabackup
group = disk
groups = yes
server = /usr/lib/amanda/amidxtaped
}
-
Any help is appreciated.
Regards,
--
Charles Stroom
email: charles at no-spam.stremen.xs4all.nl (remove the no-spam.)
Re: amrecove does not connect
Charles Stroom wrote: I tried Jean-Louis's suggestion: fiume:~ # amrecover -oauth=bsdtcp AMRECOVER Version 2.5.2p1. Contacting server on localhost ... [request failed: recv error: Connection reset by peer] the reply is different now and instantaneous. So I checked a bit further and my amanda-conf file did have the auth = bsdtcp line already in. So after some more trials I did: fiume:~ # amrecover daily AMRECOVER Version 2.5.2p1. Contacting server on fiume.localnet ... 220 fiume AMANDA index server (2.5.2p1) ready. Setting restore date to today (2007-11-27) . and netstat -taunp | grep :1008 show the established connections. So, it was the daily argument that was missing and did the trick. My problem is solved, thanks. I am still a bit puzzled what the line: conf daily# your config name means in my amanda-conf file. Would that not set daily as the default? You can't set the 'conf' in the CONFIG_DIR/daily/amanda-client.conf, because it can't read the file before it knows the config. 'con'f must be set in CONFIG_DIR/amanda-client.conf Jean-Louis
Re: amrecove does not connect
On Tue, 27 Nov 2007 10:53:20 +0100 Charles Stroom [EMAIL PROTECTED] wrote: On Tue, 27 Nov 2007 08:11:35 +0100 Marc Muehlfeld [EMAIL PROTECTED] wrote: Must a user root added somewhere? [in the xinet.d files] No. Amanda runs as user. You configured amandabackup:disk for this. But this is what I don't understand. Amanda backup runs as user amandabackup, but amrecover must run as root! I do not fully understand the xinet workings, but I suppose that it specifies that services (like amindexd) start running if the right user requests its service. But in the 3 xinet.d files (included in my first email), root is not specified as one of the users of the amanda services amanda, amandaidx and amidxtape. If I do an amrecover, and, while it times-out, I do an ps -ef | grep am, I do not see any of these amanda services coming up. Regards, Charles I correct myself, the user in the xinetd.d files has nothing to do with the user requesting the service, but is the user which runs the service when requested. Mea culpa. In the mean time, I have recovered my files straight from the tape without using amrestore. So, for now I am OK. Hoewever, amrestore is still not working! Regards, -- Charles Stroom email: charles at no-spam.stremen.xs4all.nl (remove the no-spam.)
Re: amrecove does not connect
On Tue, 27 Nov 2007 16:51:38 -0500 Jean-Louis Martineau [EMAIL PROTECTED] wrote: You can't set the 'conf' in the CONFIG_DIR/daily/amanda-client.conf, because it can't read the file before it knows the config. 'con'f must be set in CONFIG_DIR/amanda-client.conf Jean-Louis That sounds very logical indeed and moreover it works. One more little mystery out of the way. Charles -- Charles Stroom email: charles at no-spam.stremen.xs4all.nl (remove the no-spam.)
amanda not using smbclient for samba clients?
I've been through the docs a bunch of times to try to figure out what exactly I'm doing wrong but either I'm not doing anything wrong (unlikely) or there's something I keep thinking is right but isn't (more likely). When I run a check on the Amanda setup, it queries the samba client (a Mac OS X computer) but tries to communicate via Amanda ports rather than trying to mount and check the samba share. Here's the output as well as disklist and amanda.conf. I'm guessing that the problem is the disklist but the problem is non-obvious to me. # su - amanda -c amcheck -c Macs Amanda Backup Client Hosts Check WARNING: coralie: selfcheck request failed: timeout waiting for ACK Client check: 1 host checked in 30.000 seconds, 1 problem found (brought to you by Amanda 2.5.2p1) # tcpdump -i en0|grep 192.168.0.32 23:29:59.871691 IP 192.168.0.32.919 192.168.0.61.amanda: UDP, length: 125 23:29:59.871738 IP 192.168.0.61 192.168.0.32: icmp 36: 192.168.0.61 udp port amanda unreachable 23:30:09.870724 IP 192.168.0.32.919 192.168.0.61.amanda: UDP, length: 125 23:30:09.870788 IP 192.168.0.61 192.168.0.32: icmp 36: 192.168.0.61 udp port amanda unreachable 23:30:19.870655 IP 192.168.0.32.919 192.168.0.61.amanda: UDP, length: 125 23:30:19.870731 IP 192.168.0.61 192.168.0.32: icmp 36: 192.168.0.61 udp port amanda unreachable # disklist # Design Resources Mac coralie //coralie/design_resources_archive/ tar-comp-srvbest-ne coralie //coralie/design_resources/ tar-comp-srvbest-ne # amanda.conf org Macs # your organization name for reports mailto amanda [EMAIL PROTECTED] # space separated list of operators at your site dumpuser amanda # the user to run dumps under inparallel 16 # maximum dumpers that will run in parallel (max 63) # this maximum can be increased at compile-time, # modifying MAX_DUMPERS in server-src/driverio.h dumporder sssSsssStttTbbbB# specify the priority order of each dumper # s - smallest size # S - biggest size # t - smallest time # T - biggest time # b - smallest bandwitdh # B - biggest bandwitdh # try BTBTBTBTBTBT if you are not holding # disk constrained taperalgo first # The algorithm used to choose which dump image to send # to the taper.+ # Possible values: # [first|firstfit|largest|largestfit|smallest|last] # Default: first. # first First in - first out. # firstfit The first dump image that will fit # on the current tape. # largest The largest dump image. # largestfitThe largest dump image that will fit # on the current tape. # smallest The smallest dump image. # last Last in - first out. displayunit m # Possible values: k|m|g|t # Default: k. # The unit used to print many numbers. # k=kilo, m=mega, g=giga, t=tera netusage 1 Kbps# maximum net bandwidth for Amanda, in KB per sec dumpcycle 4 weeks # the number of days in the normal dump cycle runspercycle 30 # the number of amdump runs in dumpcycle days # (4 weeks * 5 amdump runs per week -- just weekdays) tapecycle 10 tapes # the number of tapes in rotation # 4 weeks (dumpcycle) times 5 tapes per week (just # the weekdays) plus a few to handle errors that # need amflush and so we do not overwrite the full # backups performed at the beginning of the previous # cycle bumpsize 20 Mb # minimum savings (threshold) to bump level 1 - 2 bumppercent 20 # minimum savings (threshold) to bump level 1 - 2 bumpdays 1 # minimum days at each level bumpmult 4 # threshold = bumpsize * bumpmult^(level-1) etimeout 300# number of seconds per filesystem for estimates. dtimeout 1800 # number of idle seconds before a dump is aborted. ctimeout 30 # maximum number of seconds that amcheck waits # for each client host tapebufs 256# A positive integer telling taper how many # 32k buffers to allocate. The default is 20 usetimestamps yes runtapes 1 # number of tapes to be used in a single run of amdump tapedev /dev/nst0 # the no-rewind tape device to be used rawtapedev
Re: amanda not using smbclient for samba clients?
Dan Brown schrieb: # disklist # Design Resources Mac coralie //coralie/design_resources_archive/ tar-comp-srvbest-ne coralie //coralie/design_resources/ tar-comp-srvbest-ne The first column is the name of the machine who connect to the samba share, not the client. Here's one of my DLEs for example: nucleus.mr.lfmg.de//amplicon/backup$ SMB_Low_Client-Fast Explanation: Nucleus does the connect to my client Amplicon and collect the data. The machine must not be the backupserver itself. E. g. if you have a remote subnet, connected with a slow connection, you can configure a remote linux machine to collect and compact your data and then transfer it from there to your backup server to save bandwidth. It's wasting bandwidth of the WAN connection to transfer the whole samba data to your backup server and do the compact there. Surely you can do this in your local subnet too, to keep the load of your backupserver low. Marc -- Marc Muehlfeld (Leitung Systemadministration) Zentrum fuer Humangenetik und Laboratoriumsmedizin Dr. Klein und Dr. Rost Lochhamer Str. 29 - D-82152 Martinsried Telefon: +49(0)89/895578-0 - Fax: +49(0)89/895578-78 http://www.medizinische-genetik.de
Re: amanda not using smbclient for samba clients?
Stefan G. Weichinger schrieb: The machine must not be the backupserver itself. You mean: The machine does not have to be the backupserver itself Right? Oh hell. Better I go back home. Getting up at 6am doesn't seem to be good for me. :-) Marc -- Marc Muehlfeld (Leitung Systemadministration) Zentrum fuer Humangenetik und Laboratoriumsmedizin Dr. Klein und Dr. Rost Lochhamer Str. 29 - D-82152 Martinsried Telefon: +49(0)89/895578-0 - Fax: +49(0)89/895578-78 http://www.medizinische-genetik.de
Re: amanda not using smbclient for samba clients?
Marc Muehlfeld schrieb: Stefan G. Weichinger schrieb: The machine must not be the backupserver itself. You mean: The machine does not have to be the backupserver itself Right? Oh hell. Better I go back home. Getting up at 6am doesn't seem to be good for me. :-) Same here, same here. The problem is: I *am* at home. ;) Greets, Stefan
