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.

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

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,

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

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

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

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

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

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:

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

Re: Trying to backup to disk, getting dump to tape failed, will try again

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

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:

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

Re: Trying to backup to disk, getting dump to tape failed, will try again

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

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

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

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

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

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

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.

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

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

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

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

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.