Re: Firewall, amanda client and ports

Morning, Jean-Louis Martineau schrieb: Yes you only need to allow connection to port 10080. This isn't added to the wiki right now, isn't it? At least I didn't saw it there. Just some more questions about that: * destination-port is 10080 udp, thats clear. But from with source ports is

amstatus: no estimate and disk was stranded on waitq

hi guys, I am having problem with my amanda status. Here are the details: [EMAIL PROTECTED] ~]$ amstatus DailySet1 Using /usr/local/etc/amanda/DailySet1/amdump.1 from Thu Jul 19 03:15:13 MYT 2007 domain1.com:/var/lib/mysql 1 549m flushed (3:15:38) domain1.com:/var/lib/mysql 1 1301m

Re: amstatus: no estimate and disk was stranded on waitq

Hi, fedora schrieb: domain4.com:/var/lib/mysql 0 planner: [hmm, disk was stranded on waitq] Try increasing etimeout in amanda.conf if it appears on next backup again. If not, maybe there was just some load on that machine, and sendsize could not finish during the time in etimeout. Marc

Re: Firewall, amanda client and ports

Changes made and backup done this morning, no problems. The client has only 10080 TCP/UDP ports open. Thanks a lot, Charles On Wed, 18 Jul 2007 10:51:21 -0400 Jean-Louis Martineau [EMAIL PROTECTED] wrote: Since you are using amanda-2.5.2p1, I suggest you use the bsdtcp auth. It will

Re: Firewall, amanda client and ports

Marc Muehlfeld wrote: Morning, Jean-Louis Martineau schrieb: Yes you only need to allow connection to port 10080. This isn't added to the wiki right now, isn't it? At least I didn't saw it there. Just some more questions about that: * destination-port is 10080 udp, thats clear. But from

client to server trickles with tape spanning

Hi, A DLE using tape spanning from a client (amanda 2.5.1p3 Debian/Sarge) to server (2.5.2p1 SGI/Irix) just seems to dump **extremely** slowly: so far in ~8hrs not even one chunk of 9GB has made it to tape. All the other DLEs (non-spanning) on that client dump as fast as the network allows and

Amanda 2.5 and HP MSL 4048 Fibre channel

Hello, We just installed a HP MSL 4048 (Fiber Channel). I do not know how to configure amanda.conf because there is several sg created by the library (it has 4 magazines). I suppose that : tapedev /dev/st0 But how about : changerdev changerfile tpchanger In dmesg : qla2xxx :07:01.0:

Re: Amanda 2.5 and HP MSL 4048 Fibre channel

Hello, Can you please post the contents of this file: /proc/scsi/scsi Thanks Pavel Hello, We just installed a HP MSL 4048 (Fiber Channel). I do not know how to configure amanda.conf because there is several sg created by the library (it has 4 magazines). I suppose that : tapedev /dev/st0

tapetype HP DAT160, anyone?

Anyone using a HP DAT160 with Amanda? Would you share your tapetype-definition? Thanks, Stefan

Re: client to server trickles with tape spanning

A DLE using tape spanning from a client (amanda 2.5.1p3 Debian/Sarge) to server (2.5.2p1 SGI/Irix) just seems to dump **extremely** slowly: so far in ~8hrs not even one chunk of 9GB has made it to tape. All the other DLEs (non-spanning) on that client dump as fast as the network allows and