lost tapelist question

2004-01-12 Thread Mark Le Noury
Hi, Is there a way to manually re-create the tapelist file? I deleted all the tapelist files out of the wrong config directory today now amrecover says No index records for disk for specified date when I try to do a restore. Is there a way to catalogue the tapes that I have already

Re: Backing up a Windows 2k3 share via Samba using Kerberos

2004-01-12 Thread Toomas Aas
Hi! I want to back up my Windows /home userspace, which is served as part of a dfs volume (//server/dfs/home to be precise) from our Windows 2k3 ADS. Here's what I've done so far on the Amanda linux RH9 box: 1. Installed Samba 3.0 snip However, overnight it ran and failed with the

Unable to backup clients

2004-01-12 Thread Mike Heller
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: Unable to backup clients

2004-01-12 Thread Mike Heller
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 the clients. amcheck daily

RE: Unable to backup clients

2004-01-12 Thread Rebecca Pakish Crum
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

2004-01-12 Thread Mike Heller
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

RE: Unable to backup clients

2004-01-12 Thread donald . ritchey
Mike: Did you install the modified Amanda software on both client and server? They have to match so that their 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.

Re: Unable to backup clients

2004-01-12 Thread Mike Heller
Yes, I used essentially the same config string on both server and clients except on the client side I added: --without-server --without-restore Mike [EMAIL PROTECTED] wrote: Mike: Did you install the modified Amanda software on both client and server? They have to match so that their

Re: Unable to backup clients

2004-01-12 Thread Mike Heller
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 not the cause of

Re: Unable to backup clients

2004-01-12 Thread Jon LaBadie
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 clients), I see things like: sendbackup:

Re: Unable to backup clients

2004-01-12 Thread Mike Heller
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 clients), I see

RE: Unable to backup clients

2004-01-12 Thread donald . ritchey
Mike: There may be a bit of misunderstanding here. The TCP ports may be in the unprivileged range, since the ones we use here are 5-50040. We do have the UDP ports in the range of 890-899. See if you can try a different range on TCP ports and, if possible, allocate a larger range of ports

Re: extremely varied tape write rates?

2004-01-12 Thread Eric Siegerman
On Fri, Jan 09, 2004 at 11:33:26AM -0500, Kurt Yoder wrote: DUMPER STATS TAPER STATS HOSTNAME DISKL ORIG-KBOUT-KB COMP% MMM:SSKB/s MMM:SSKB/s --

Ramifications of dump cycle and number of tapes choices

2004-01-12 Thread Fran Fabrizio
Hello, I was trying to think through what we want our dump cycle and total number of tapes to be, and I realized that I wasn't quite clear on some things. We have a changer with a capacity of 33 tapes. We have Amanda configured for a 7 day dump cycle, backups every night. Our backups currently

Re: Ramifications of dump cycle and number of tapes choices

2004-01-12 Thread Eric Siegerman
On Mon, Jan 12, 2004 at 06:56:25PM -0600, Fran Fabrizio wrote: [Assuming dumpcycle=7, runspercycle=7, runtapes=1, tapecycle=33:] Are the following statements correct? 1. We will have a full dump of any given partition somewhere on the most recent 7 tapes Yes. As you've figured out,

Re: Ramifications of dump cycle and number of tapes choices

2004-01-12 Thread Jon LaBadie
On Mon, Jan 12, 2004 at 10:31:48PM -0500, Eric Siegerman wrote: On Mon, Jan 12, 2004 at 06:56:25PM -0600, Fran Fabrizio wrote: [Assuming dumpcycle=7, runspercycle=7, runtapes=1, tapecycle=33:] Are the following statements correct? 1. We will have a full dump of any given partition