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
Re: amanda not using smbclient for samba clients?
Marc Muehlfeld schrieb: > Stefan G. Weichinger schrieb: >>> The machine must not be the backupserver itself. >> >> You mean: >> >> "The machine does not have to be the backupserver itself" >> >> Right? > > Oh hell. Better I go back home. Getting up at 6am doesn't seem to be > good for me. :-) Same here, same here. The problem is: I *am* at home. ;) Greets, Stefan
Re: amanda not using smbclient for samba clients?
Stefan G. Weichinger schrieb: The machine must not be the backupserver itself. You mean: "The machine does not have to be the backupserver itself" Right? Oh hell. Better I go back home. Getting up at 6am doesn't seem to be good for me. :-) Marc -- Marc Muehlfeld (Leitung Systemadministration) Zentrum fuer Humangenetik und Laboratoriumsmedizin Dr. Klein und Dr. Rost Lochhamer Str. 29 - D-82152 Martinsried Telefon: +49(0)89/895578-0 - Fax: +49(0)89/895578-78 http://www.medizinische-genetik.de
Re: amanda not using smbclient for samba clients?
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. Marc -- Marc Muehlfeld (Leitung Systemadministration) Zentrum fuer Humangenetik und Laboratoriumsmedizin Dr. Klein und Dr. Rost Lochhamer Str. 29 - D-82152 Martinsried Telefon: +49(0)89/895578-0 - Fax: +49(0)89/895578-78 http://www.medizinische-genetik.de
amanda not using smbclient for samba clients?
I've been through the docs a bunch of times to try to figure out what exactly I'm doing wrong but either I'm not doing anything wrong (unlikely) or there's something I keep thinking is right but isn't (more likely). When I run a check on the Amanda setup, it queries the samba client (a Mac OS X computer) but tries to communicate via Amanda ports rather than trying to mount and check the samba share. Here's the output as well as disklist and amanda.conf. I'm guessing that the problem is the disklist but the problem is non-obvious to me. # su - amanda -c "amcheck -c Macs" Amanda Backup Client Hosts Check WARNING: coralie: selfcheck request failed: timeout waiting for ACK Client check: 1 host checked in 30.000 seconds, 1 problem found (brought to you by Amanda 2.5.2p1) # tcpdump -i en0|grep 192.168.0.32 23:29:59.871691 IP 192.168.0.32.919 > 192.168.0.61.amanda: UDP, length: 125 23:29:59.871738 IP 192.168.0.61 > 192.168.0.32: icmp 36: 192.168.0.61 udp port amanda unreachable 23:30:09.870724 IP 192.168.0.32.919 > 192.168.0.61.amanda: UDP, length: 125 23:30:09.870788 IP 192.168.0.61 > 192.168.0.32: icmp 36: 192.168.0.61 udp port amanda unreachable 23:30:19.870655 IP 192.168.0.32.919 > 192.168.0.61.amanda: UDP, length: 125 23:30:19.870731 IP 192.168.0.61 > 192.168.0.32: icmp 36: 192.168.0.61 udp port amanda unreachable # disklist # Design Resources Mac coralie //coralie/design_resources_archive/ tar-comp-srvbest-ne coralie //coralie/design_resources/ tar-comp-srvbest-ne # amanda.conf org "Macs" # your organization name for reports mailto "amanda [EMAIL PROTECTED]" # space separated list of operators at your site dumpuser "amanda" # the user to run dumps under inparallel 16 # maximum dumpers that will run in parallel (max 63) # this maximum can be increased at compile-time, # modifying MAX_DUMPERS in server-src/driverio.h dumporder "sssSsssStttTbbbB"# specify the priority order of each dumper # s -> smallest size # S -> biggest size # t -> smallest time # T -> biggest time # b -> smallest bandwitdh # B -> biggest bandwitdh # try "BTBTBTBTBTBT" if you are not holding # disk constrained taperalgo first # The algorithm used to choose which dump image to send # to the taper.+ # Possible values: # [first|firstfit|largest|largestfit|smallest|last] # Default: first. # first First in - first out. # firstfit The first dump image that will fit # on the current tape. # largest The largest dump image. # largestfitThe largest dump image that will fit # on the current tape. # smallest The smallest dump image. # last Last in - first out. displayunit "m" # Possible values: "k|m|g|t" # Default: k. # The unit used to print many numbers. # k=kilo, m=mega, g=giga, t=tera netusage 1 Kbps# maximum net bandwidth for Amanda, in KB per sec dumpcycle 4 weeks # the number of days in the normal dump cycle runspercycle 30 # the number of amdump runs in dumpcycle days # (4 weeks * 5 amdump runs per week -- just weekdays) tapecycle 10 tapes # the number of tapes in rotation # 4 weeks (dumpcycle) times 5 tapes per week (just # the weekdays) plus a few to handle errors that # need amflush and so we do not overwrite the full # backups performed at the beginning of the previous # cycle bumpsize 20 Mb # minimum savings (threshold) to bump level 1 -> 2 bumppercent 20 # minimum savings (threshold) to bump level 1 -> 2 bumpdays 1 # minimum days at each level bumpmult 4 # threshold = bumpsize * bumpmult^(level-1) etimeout 300# number of seconds per filesystem for estimates. dtimeout 1800 # number of idle seconds before a dump is aborted. ctimeout 30 # maximum number of seconds that amcheck waits # for each client host tapebufs 256# A positive integer telling taper how many # 32k buffers to allocate. The default is 20 usetimestamps yes runtapes 1 # number of tapes to be used in a single run of amdump tapedev "/dev/nst0" # the no-rewind tape dev
