Re: Unable to backup clients [possibly fixed!]

ssion.   Good luck and best wishes,   Don Donald L. (Don) Ritchey E-mail:  [EMAIL PROTECTED] -Original Message- From: Mike Heller [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 13, 2004 10:46 AM To: [EMAIL PROTECTED] Subject: Re: Unable to b

Re: Unable to backup clients

t one time). Our options to the configure are: --with-portrange=5,50040 --with-udpportrange=890,899 Best of luck, Don Donald L. (Don) Ritchey E-mail: [EMAIL PROTECTED] -Original Message----- From: Mike Heller [mailto:[EMAIL PROTECTED]] Sent: Monday, January 12, 2004 3:58 PM To: [EMAIL

Re: Unable to backup clients

Jon LaBadie wrote: On Mon, Jan 12, 2004 at 11:32:22AM -0800, Mike Heller wrote: I fixed the problem of the "high server load" by installing amanda version 2.4.4p1 on the server and the clients. ... But the backups fail. Checking the logs in /tmp/amanda (on the clien

Re: Unable to backup clients

Gene, Not if the drive is in the eject (operate handle) status, you can't do anything with the tape at that point. Mike Gene Heskett wrote: On Monday 12 January 2004 14:34, Mike Heller wrote: Note the tape error is because I haven't yet switched the tape, it's n

Re: Unable to backup clients

port expectations and limitations are consistent. We use this configuration here with great success, but you have to install the portlist modifications on both ends of the connection. Don Donald L. (Don) Ritchey E-mail: [EMAIL PROTECTED] -Original Message- From: Mike Heller [mailto

Re: Unable to backup clients

Rebecca Pakish Crum wrote: But the backups fail. Checking the logs in /tmp/amanda (on the clients), I see things like: sendbackup: time 0.000: stream_server: waiting for connection: 0.0.0.0.33011 sendbackup: time 0.001: stream_server: waiting for connection: 0.0.0.0.33012 sendbackup: time 0.001:

Re: Unable to backup clients

Note the tape error is because I haven't yet switched the tape, it's not the cause of the failed backups. Just wanted to clarify that. Thanks, Mike Mike Heller wrote: I fixed the problem of the "high server load" by installing amanda version 2.4.4p1 on the server and t

Unable to backup clients

I fixed the problem of the "high server load" by installing amanda version 2.4.4p1 on the server and the clients. amcheck daily now reports: Amanda Tape Server Host Check - Holding disk /big/backup/amanda/dumps: 1034688 KB disk space available, using 215488 KB ERROR:

Re: VERY high load on server

Paul, reply inline Paul Bijnens wrote: Mike Heller wrote: I have amanda running on serveral servers and last night I tried to back up one more to the tape server. When I arrived this morning, the backups were still running and the new server had an extremely high load Am I correct that

Re: VERY high load on server

Gene Heskett wrote: On Wednesday 07 January 2004 14:55, Joshua Baker-LePain wrote: On Wed, 7 Jan 2004 at 2:40pm, Gene Heskett wrote On Wednesday 07 January 2004 13:21, Mike Heller wrote: I have amanda running on serveral servers and last

VERY high load on server

I have amanda running on serveral servers and last night I tried to back up one more to the tape server. When I arrived this morning, the backups were still running and the new server had an extremely high load on it. It's a RedHat Linux 9.0 server and the load was over 520 (quad Xeon system)

Having problems with remote Linux host

I have amanda running fine on a machine (call it server 1) which backs up to a local tape device. I have a client machine (client 1) that I would like to dump to tape as well. I have tried adding the necessary details of "client 1" to the disklist on "server 1", but there is a problem somewh

getting further

I am getting further with Amanda. I ran a backup last night but had a problem: error [/bin/tar returned 2] This problem has come up in the past (searched the group) but there seems to be no specific reason for this. I'm using tar version: tar (GNU tar) 1.13.11 I'm trying to backup: /boot

selfcheck request timed out

Can't figure this out. I'm using a RedHat 6.1 system with Amanda 2.4.3b3. I have gone through the setup several times and managed to fix most of the issues. I am still having a problem with amcheck. I keep getting the warnign "selfcheck request timed out. Host down?". In /tmp/amanda, I am

permissions

I have compiled and installed amanda twice. In each case, I created a new user "amanda" that belonged to group "disk" or group "sys" (RedHat 6.1). In both cases I have problems with permissions. With "disk", I have problems reading/writing some directories. I altered permissions on some bu

New User, config issues

Hello, I just installed amanda without issue and have been reading the man pages, faq, and egroups archive. I still have some issues. First some details on my setup. I have a Linux server with an internal tape drive. I have 8 tapes (DLT 20/40) and want at least one full backup per week.