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?
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
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?
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