Question about dumporder

Hello, I have a question about the dumporder parameter. To what are the two bandwidth options (B and b) related? Client/Server connection (e. g. 1Gbit)? Or the real bandwith between server and client? I have a client that is connected by a 1Gbit LAN-card to it's subnet in our branch office.

Re: can't repeat Mesg read: Connection reset by peer

Hi all I'm sorry if you understand my English.I have the pleasure of writing to you again. I examine why this log Mesg read: Connection reset by peer is output. To want to repeat it, I executed the following commands on the server. - amdump daily - iptables -A INPUT -p tcp -d IPaddress of the

RE: dump hangs at getting estimates

Hi all, I am still having problems with my backups. Tonight the backup failed again with the error planner: ERROR Request timeout waiting for ACK. Yet when I run amcheck -c for the client everything looks fine. [EMAIL PROTECTED]:/opt/amanda]#amcheck -c Weekly Amanda Backup Client Hosts Check

Re: can't repeat Mesg read: Connection reset by peer

Takashi Kurakata wrote: Hi all I'm sorry if you understand my English.I have the pleasure of writing to you again. I examine why this log Mesg read: Connection reset by peer is output. To want to repeat it, I executed the following commands on the server. - amdump daily - iptables -A

Re: Question about dumporder

Jean-Louis Martineau schrieb: bandwidth estimation is done using the previous backup of the DLE, You can get the 'dump rates' with: amadmin config info Would be cool if this short info could be added to the dumporder option of the amanda.conf manpage. I didn't found this information. Thanks

Re: Question about dumporder

bandwidth estimation is done using the previous backup of the DLE, You can get the 'dump rates' with: amadmin config info Jean-Louis Marc Muehlfeld wrote: Hello, I have a question about the dumporder parameter. To what are the two bandwidth options (B and b) related? Client/Server connection

Re: Probably very stupid question about chg-disk

On Fri, 16 Nov 2007, Francis Galiegue wrote: Is the holding disk still necessary? My guess is no, but then I may be mistaken. The documentation is not clear on this point. It only says not to put holding disks in the same place than vtapes... Which doesn't really mean you WILL still need a

Probably very stupid question about chg-disk

Hello list, The internal tape drive on our Amanda backup server has fried the motherboard and itself, so as a result I had to salvage what I could on a new machine which now does disk backups using chg-disk. I pretty much took over the configuration files and adapted it according to the

tape_splitsize Problem: Resulting Splits Are Too Small

I added tape_splitsize to a DLE, like so: define dumptype comp-root-tar-charlesc-home { comp-root-tar tape_splitsize 3 Gb comment Root partitions with compression, special for charlesc:/home exclude list /etc/amanda/DailySet1/excludes.charlesc.home } The dump is to cirtual tapes

Re: amadmin force question

Marc Muehlfeld wrote: Hi, I saw a interesting behavier when I use amadmin to force a level 0. While a force to the root file system just set this one to level 0: # amadmin KDD force genome / amadmin: genome.mr.lfmg.de:/ is set to a forced level 0 at next run. a force to a mountpoint that

Re: Probably very stupid question about chg-disk

Le Friday 16 November 2007 18:29:57 Geert Uytterhoeven, vous avez écrit : On Fri, 16 Nov 2007, Francis Galiegue wrote: Is the holding disk still necessary? My guess is no, but then I may be mistaken. The documentation is not clear on this point. It only says not to put holding disks in the

Re: amadmin force question

* Francis Galiegue [EMAIL PROTECTED] [20071116 15:03]: Le Friday 16 November 2007 20:40:36 Jean-Francois Malouin, vous avez écrit : [...] adadmin conf force [ hostname [ disks ]* ]+ ^ this is a regex so you have to write /$ otherwize

Re: amadmin force question

* Marc Muehlfeld [EMAIL PROTECTED] [20071116 14:33]: Hi, I saw a interesting behavier when I use amadmin to force a level 0. While a force to the root file system just set this one to level 0: # amadmin KDD force genome / amadmin: genome.mr.lfmg.de:/ is set to a forced level 0 at next run

Re: amadmin force question

man amanda Look at the HOST DISK EXPRESSION section. Jean-Louis Francis Galiegue wrote: Le Friday 16 November 2007 20:40:36 Jean-Francois Malouin, vous avez écrit : [...] adadmin conf force [ hostname [ disks ]* ]+ ^ this is a regex so you have to

amadmin force question

Hi, I saw a interesting behavier when I use amadmin to force a level 0. While a force to the root file system just set this one to level 0: # amadmin KDD force genome / amadmin: genome.mr.lfmg.de:/ is set to a forced level 0 at next run. a force to a mountpoint that contains other, forces

Re: Probably very stupid question about chg-disk

Geert Uytterhoeven wrote: On Fri, 16 Nov 2007, Francis Galiegue wrote: Is the holding disk still necessary? My guess is no, but then I may be mistaken. The documentation is not clear on this point. It only says not to put holding disks in the same place than vtapes... Which doesn't really

Re: tape_splitsize Problem: Resulting Splits Are Too Small

Charles Curley schrieb: The dump is to cirtual tapes on a hard drive. The resulting splits are all 10 MB in size. E.g.: How do I change that to a more reasonable size, like 3 Gb? The parameters fallback_splitsize default is 10M, if you don't set it. Maybe the conditions descripted inside the

Re: amadmin force question

Marc Muehlfeld wrote at 20:32 +0100 on Nov 16, 2007: Hi, I saw a interesting behavier when I use amadmin to force a level 0. While a force to the root file system just set this one to level 0: # amadmin KDD force genome / amadmin: genome.mr.lfmg.de:/ is set to a forced level 0 at

Re: amadmin force question

Le Friday 16 November 2007 21:10:33, vous avez écrit : man amanda Look at the HOST DISK EXPRESSION section. Uh, yeah, indeed, these are not regexes at all :p It smells a lot like shell globbing though. Bah, anyway. That's nitpicking. Sorry ;) -- Francis Galiegue, [EMAIL PROTECTED] -

Re: amadmin force question

Le Friday 16 November 2007 20:40:36 Jean-Francois Malouin, vous avez écrit : [...] adadmin conf force [ hostname [ disks ]* ]+ ^ this is a regex so you have to write /$ otherwize it will match all DLEs on that host that start with / jf Hmm, if

Re: tape_splitsize Problem: Resulting Splits Are Too Small

You must defined a split_diskbuffer if the dump go directly to tape without using a holding disk. In this case, there is no advantage to use a tape_splitsize bigger than your memory size. Also, on a 32 bit system, it is limited to below 2Gb. Jean-Louis Charles Curley wrote: I added

Re: amadmin force question

Chris Hoogendyk schrieb: Can't say for sure, but suppose you tried /shares/ instead of /shares? No. I used it like i copy/pasted it to my first mail (without slash in the end). # amadmin KDD force genome /shares But the solution to my question was given by Jean-Louis Martineau in an other

Re: amadmin force question

Jean-Louis Martineau schrieb: man amanda Look at the HOST DISK EXPRESSION section. EXPRESSION WILL MATCH WILL NOT MATCH // any other disk /usr /usr /usr/opt /usr$/usr/usr/opt Ok. / is handled a different.

Re: New Development in Amanda poster available

On Mon, 2007-11-12 at 11:17 -0600, Dustin J. Mitchell wrote: P.S. If anyone would like a copy of the Amanda logo in SVG format, let me know. Or you could take it out back behind the woodshed and retire it already. :-) If I haven't said it enough yet, I'm _really_ sorry about that logo,

Amanda and WORM

Hi all, I'm not new to Amanda, but I'm new to Amanda WORM LTO-3. I've a HP Ultrium 1/8 G2 Autoloader with LTO-3 WORM, the changer is /dev/sg1 and the drive is /dev/sg0: I receive always Input/Output error when I run amdump DailySet1. This is my amanda.conf: # amanda-server-2.5.0p2-4