Re: amanda not using smbclient for samba clients?
Marc Muehlfeld wrote: 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 of my DLEs for example: nucleus.mr.lfmg.de//amplicon/backup$ SMB_Low_Client-Fast Explanation: Nucleus does the connect to my client Amplicon and collect the data. The machine must not be the backupserver itself. E. g. if you have a remote subnet, connected with a slow connection, you can configure a remote linux machine to collect and compact your data and then transfer it from there to your backup server to save bandwidth. It's wasting bandwidth of the WAN connection to transfer the whole samba data to your backup server and do the compact there. Surely you can do this in your local subnet too, to keep the load of your backupserver low. It can't be the backup server itself or shouldn't? I was following the 15 minute setup example on zmanda.com and it used the backup server itself. Isn't that the point of having --with-smbclient in the compile script? It doesn't really matter how loaded down the backup server is, as long as the computers with the shares I am backing up don't experience a huge load. Out of curiosity I've changed it to the backup server itself: ministryofinformation //coralie/design_resources_archive/ tar-comp-srvbest-ne but now on the target computer I see no connection attempts at all via tcpdump. These computers are all on the same subnet and are qualified addresses of an internal domain (although it's FQDN would be ministryofinformation.thezoo). --- Dan Brown
Amanda with Debian Etch and Sarge
I am in the process of learning Amanda and I am hoping someone can help me
with a problem I am having.
I have been using this website as a starting point:
http://www.howtoforge.com/disk_based_backups_amanda_debian_etch
We have a Debian etch machine as a server and 2 clients and everything is
working but now we want to add a Debian sarge machine as a client and the
result is: selfcheck request failed: timeout waiting for ACK
Amanda on the Sarge machine is installed from backports.org and is the
same version as on the etch machines.
From the Sarge machine
service amanda
{
disable = no
socket_type = stream
protocol= tcp
wait= no
user= backup
group = backup
groups = yes
server = /usr/lib/amanda/amandad
# server_args = -auth=bsd amdump amindexd amidxtaped
server_args = -auth=bsdtcp amdump
}
I have tried different server_args to see if I can make it work, but the
result is always
more amcheck.20071128151818.debug
amcheck: debug 1 pid 8229 ruid 34 euid 0: start at Wed Nov 28 15:18:18 2007
amcheck: debug 1 pid 8229 ruid 34 euid 34: rename at Wed Nov 28 15:18:18 2007
security_getdriver(name=BSD) returns 0xb7f330e0
security_handleinit(handle=0x805e6c0, driver=0xb7f330e0 (BSD))
amcheck-clients: time 0.001: bind_portrange2: Try port 860: Available -
Success
amcheck-clients: time 0.001: dgram_bind: socket bound to 0.0.0.0.860
amcheck-clients: dgram_send_addr(addr=0xbf959f00, dgram=0xb7f34084)
amcheck-clients: time 0.003: (sockaddr_in *)0xbf959f00 = { 2, 10080,
192.168.10.24 }
amcheck-clients: dgram_send_addr: 0xb7f34084-socket = 4
changer_query: changer return was 5 1
changer_query: searchable = 0
changer_find: looking for NULL changer is searchable = 0
amcheck-clients: dgram_send_addr(addr=0xbf959df0, dgram=0xb7f34084)
amcheck-clients: time 10.005: (sockaddr_in *)0xbf959df0 = { 2, 10080,
192.168.10.24 }
amcheck-clients: dgram_send_addr: 0xb7f34084-socket = 4
amcheck-clients: dgram_send_addr(addr=0xbf959df0, dgram=0xb7f34084)
amcheck-clients: time 20.003: (sockaddr_in *)0xbf959df0 = { 2, 10080,
192.168.10.24 }
amcheck-clients: dgram_send_addr: 0xb7f34084-socket = 4
security_seterror(handle=0x805e6c0, driver=0xb7f330e0 (BSD) error=timeout
waiting for ACK)
security_close(handle=0x805e6c0, driver=0xb7f330e0 (BSD))
amcheck: pid 8229 finish time Wed Nov 28 15:18:48 2007
The version of xinet is different from the etch server and the sarge
machine, the sarge machine is also a samba server and swat is running as a
xinet service.
Any advice would be great
Re: Amanda with Debian Etch and Sarge
Your xinetd amanda service is configure for bsdtcp auth, but you are
using bsd.
Edit your dumptype to include: auth bsdtcp
Jean-Louis
Tech wrote:
I am in the process of learning Amanda and I am hoping someone can help me
with a problem I am having.
I have been using this website as a starting point:
http://www.howtoforge.com/disk_based_backups_amanda_debian_etch
We have a Debian etch machine as a server and 2 clients and everything is
working but now we want to add a Debian sarge machine as a client and the
result is: selfcheck request failed: timeout waiting for ACK
Amanda on the Sarge machine is installed from backports.org and is the
same version as on the etch machines.
From the Sarge machine
service amanda
{
disable = no
socket_type = stream
protocol= tcp
wait= no
user= backup
group = backup
groups = yes
server = /usr/lib/amanda/amandad
# server_args = -auth=bsd amdump amindexd amidxtaped
server_args = -auth=bsdtcp amdump
}
I have tried different server_args to see if I can make it work, but the
result is always
more amcheck.20071128151818.debug
amcheck: debug 1 pid 8229 ruid 34 euid 0: start at Wed Nov 28 15:18:18 2007
amcheck: debug 1 pid 8229 ruid 34 euid 34: rename at Wed Nov 28 15:18:18 2007
security_getdriver(name=BSD) returns 0xb7f330e0
security_handleinit(handle=0x805e6c0, driver=0xb7f330e0 (BSD))
amcheck-clients: time 0.001: bind_portrange2: Try port 860: Available -
Success
amcheck-clients: time 0.001: dgram_bind: socket bound to 0.0.0.0.860
amcheck-clients: dgram_send_addr(addr=0xbf959f00, dgram=0xb7f34084)
amcheck-clients: time 0.003: (sockaddr_in *)0xbf959f00 = { 2, 10080,
192.168.10.24 }
amcheck-clients: dgram_send_addr: 0xb7f34084-socket = 4
changer_query: changer return was 5 1
changer_query: searchable = 0
changer_find: looking for NULL changer is searchable = 0
amcheck-clients: dgram_send_addr(addr=0xbf959df0, dgram=0xb7f34084)
amcheck-clients: time 10.005: (sockaddr_in *)0xbf959df0 = { 2, 10080,
192.168.10.24 }
amcheck-clients: dgram_send_addr: 0xb7f34084-socket = 4
amcheck-clients: dgram_send_addr(addr=0xbf959df0, dgram=0xb7f34084)
amcheck-clients: time 20.003: (sockaddr_in *)0xbf959df0 = { 2, 10080,
192.168.10.24 }
amcheck-clients: dgram_send_addr: 0xb7f34084-socket = 4
security_seterror(handle=0x805e6c0, driver=0xb7f330e0 (BSD) error=timeout
waiting for ACK)
security_close(handle=0x805e6c0, driver=0xb7f330e0 (BSD))
amcheck: pid 8229 finish time Wed Nov 28 15:18:48 2007
The version of xinet is different from the etch server and the sarge
machine, the sarge machine is also a samba server and swat is running as a
xinet service.
Any advice would be great
Re: cleaning tapes and integration into Amanda backup scheme?
On Mon, 22 Oct 2007, Olivier Nicole wrote: My Sun L9 array has told me it needs a cleaning tape run. I have one so that's no problem but what I'd like to know is if there is a way that Amanda can receive info from the tape drive about the requirement for cleaning and co-ordinate cleaning tape runs as part of the overall backup stragegy? My strategy, all human based, is to have the cleaning tape on the pile of the next set of 6 tapes to be used. I have my tapes pool divided into 3 sets of 6, once I have run through the current set, I move the stack to the back and come up with a new stack, on top of which is the cleaning tape. My L9 tape array has DLT-4 tapes in the first 8 slots, and today I've put a brand new cleaning tape into the 9th slot. There's nothing in my tape server's amanda.conf file relating to cleaning tapes, so I'm wondering where in the Amanda config schema the info about location of cleaning tapes needs to be. Does Amanda itself need to know, or does mtx need to know directly? Craig. -- Post by Craig Dewick (tm). Web @ http://lios.apana.org.au/~cdewick;. Email 2 [EMAIL PROTECTED]. SunShack @ http://www.sunshack.org; Galleries @ http://www.sunshack.org/gallery2;. Also lots of tech data, etc. Sun Microsystems webring at http://n.webring.com/hub?ring=sunmicrosystemsu;.
