Re: [Samba] Domain DFS on samba 4
For data replication just use glusterd/glusterfs. This would do the job . Running for me without trouble. Greetings Daniel --- EDV Daniel Müller Leitung EDV Tropenklinik Paul-Lechler-Krankenhaus Paul-Lechler-Str. 24 72076 Tübingen Tel.: 07071/206-463, Fax: 07071/206-499 eMail: muel...@tropenklinik.de Internet: www.tropenklinik.de --- -Ursprüngliche Nachricht- Von: samba-boun...@lists.samba.org [mailto:samba-boun...@lists.samba.org] Im Auftrag von Ludovic Rouse-Lamarre Gesendet: Samstag, 3. November 2012 21:56 An: samba@lists.samba.org Betreff: Re: [Samba] Domain DFS on samba 4 On 2012-10-28 13:01, Robert Schetterer wrote: To set up a load-balancing Dfs share, create the symbolic link like this: # ln -s 'msdfs:toltec\data,msdfs:mixtec\data' lb-data Ok well anyway it seems samba DFS doesn't include data replication. I have been looking around and I think maybe the Unison project would do the job for us. In response to AB, if possible we prefer to avoid the latency penalty for everyone. I have reconsidered using domain DFS. I think a stand-alone DFS root would be sufficient. I am interested in setting up a load-balancing Dfs share but I need clarifications regarding the selection process. Let's say I define my load balancing share like this: ln -s 'msdfs:serverindatacenter\data,msdfs:nasinremoteoffice\data' lb-data If both shares specified in the load balancing Dfs share are available, can I be sure the clients in our remote office will always be accessing their own NAS rather than the server available over the WAN? In other words is it possible they will connect to the server available with a higher latency or can I be sure they will always connect to the server directly on the LAN? Please take note the remote office is connected to the central server through a VPN. -- Ludovic Rouse-Lamarre, ing. jr Coordonnateur au support technique ludovic.rouse-lama...@xyzcivitas.com Groupe XYZCivitas Inc. 4000 rue Saint-Ambroise Bureau 190 Montréal, Québec, H4C 2C7 http://www.xyzcivitas.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Domain DFS on samba 4
On 2012-10-28 13:01, Robert Schetterer wrote: To set up a load-balancing Dfs share, create the symbolic link like this: # ln -s 'msdfs:toltec\data,msdfs:mixtec\data' lb-data Ok well anyway it seems samba DFS doesn't include data replication. I have been looking around and I think maybe the Unison project would do the job for us. In response to AB, if possible we prefer to avoid the latency penalty for everyone. I have reconsidered using domain DFS. I think a stand-alone DFS root would be sufficient. I am interested in setting up a load-balancing Dfs share but I need clarifications regarding the selection process. Let's say I define my load balancing share like this: ln -s 'msdfs:serverindatacenter\data,msdfs:nasinremoteoffice\data' lb-data If both shares specified in the load balancing Dfs share are available, can I be sure the clients in our remote office will always be accessing their own NAS rather than the server available over the WAN? In other words is it possible they will connect to the server available with a higher latency or can I be sure they will always connect to the server directly on the LAN? Please take note the remote office is connected to the central server through a VPN. -- Ludovic Rouse-Lamarre, ing. jr Coordonnateur au support technique ludovic.rouse-lama...@xyzcivitas.com Groupe XYZCivitas Inc. 4000 rue Saint-Ambroise Bureau 190 Montréal, Québec, H4C 2C7 http://www.xyzcivitas.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Domain DFS on samba 4
On Sun, 2012-10-28 at 12:46 -0400, Ludovic Rouse-Lamarre wrote: Hello, Our company currently stores its data on centralized samba servers which causes performance problems for remote office employees. We are thinking of decentralizing the data with NAS in each office and synchronizing all the NAS on our central domain controller with MSDFS. I have heard this can be done in real time with Windows and Active Directory. http://en.wikipedia.org/wiki/Distributed_File_System_(Microsoft) http://en.wikipedia.org/wiki/Distributed_File_System_%28Microsoft%29 http://technet.microsoft.com/en-us/library/cc782417.aspx The physical location of the data becomes transparent to the end user. The DFS path formed with the domain name remains \\DOMAINNAME\share123 which points the client to the storage device which is physically closest to him (the local NAS), thus eliminating the latency problems and simplifying the paths to our servers. We are currently running a Samba domain and we tend toward open source solutions but this is something we need. From what I understand Samba 3 cannot run domain DFS because it requires Active Directory. I would like to know if this will be possible with Samba 4? If you just want to redirect one share from a common name to somewhere else, then you don't need domain DFS, normal MSDFS will do. You wouldn't use the domain name, but just another server (fs.domain.com for example) and then point back the shares to the office you wish to actually host the data. There is documentation on DFS in the Samba HOWTO. Naturally, the data will only be in one spot, but if it's the right spot, that shouldn't be an issue. You can then move it around without breaking things, but just changing who pays the latency penalty. Andrew Bartlett -- Andrew Bartletthttp://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Domain DFS on samba 4
Hello, Our company currently stores its data on centralized samba servers which causes performance problems for remote office employees. We are thinking of decentralizing the data with NAS in each office and synchronizing all the NAS on our central domain controller with MSDFS. I have heard this can be done in real time with Windows and Active Directory. http://en.wikipedia.org/wiki/Distributed_File_System_(Microsoft) http://en.wikipedia.org/wiki/Distributed_File_System_%28Microsoft%29 http://technet.microsoft.com/en-us/library/cc782417.aspx The physical location of the data becomes transparent to the end user. The DFS path formed with the domain name remains \\DOMAINNAME\share123 which points the client to the storage device which is physically closest to him (the local NAS), thus eliminating the latency problems and simplifying the paths to our servers. We are currently running a Samba domain and we tend toward open source solutions but this is something we need. From what I understand Samba 3 cannot run domain DFS because it requires Active Directory. I would like to know if this will be possible with Samba 4? Respectfully, -- Ludovic Rouse-Lamarre, ing. jr Coordonnateur au support technique ludovic.rouse-lama...@xyzcivitas.com Groupe XYZCivitas Inc. 4000 rue Saint-Ambroise Bureau 190 Montréal, Québec, H4C 2C7 http://www.xyzcivitas.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Domain DFS on samba 4
Am 28.10.2012 17:46, schrieb Ludovic Rouse-Lamarre: Hello, Our company currently stores its data on centralized samba servers which causes performance problems for remote office employees. We are thinking of decentralizing the data with NAS in each office and synchronizing all the NAS on our central domain controller with MSDFS. I have heard this can be done in real time with Windows and Active Directory. http://en.wikipedia.org/wiki/Distributed_File_System_(Microsoft) http://en.wikipedia.org/wiki/Distributed_File_System_%28Microsoft%29 http://technet.microsoft.com/en-us/library/cc782417.aspx The physical location of the data becomes transparent to the end user. The DFS path formed with the domain name remains \\DOMAINNAME\share123 which points the client to the storage device which is physically closest to him (the local NAS), thus eliminating the latency problems and simplifying the paths to our servers. We are currently running a Samba domain and we tend toward open source solutions but this is something we need. From what I understand Samba 3 cannot run domain DFS because it requires Active Directory. I would like to know if this will be possible with Samba 4? Respectfully, there are many ways keeping data in sync i.e rsync, div cluster file systems ( all open source ) etc, so you need to look what exact fits best to you dfs might not be ,the best solution for your setup anyway look http://www.samba.org/samba/docs/using_samba/ch08.html ... Configuring Samba for Dfs To act as a Dfs server, Samba 2.2 must be compiled with the --with-msdfs configure option. (See Chapter 2 for instructions on configuring and compiling Samba.) Samba 3.0 includes Dfs support by default and does not need to be compiled with the --with-msdfs configure option. Once a Dfs-enabled Samba server is running, there are just two steps to serving a Dfs share. First we will set up a Dfs root directory on the server, and then we will modify the smb.conf configuration file to enable the share. Setting up the Dfs root First we need to create a directory to act as the Dfs root: # mkdir /usr/local/samba/dfs This can be any directory, but it is important that it be owned by root and given the proper permissions: # chown root:root /usr/local/samba/dfs # chmod 755 /usr/local/samba/dfs The Dfs directory tree can have subdirectories and files, just like any other shared directory. These will function just as they would in any other share, allowing clients to access the directories and files on the Samba server. The whole idea of Dfs, though, is to gather together shares on other servers by making references to them in the Dfs tree. The way this is implemented with Samba involves a clever use of symbolic links, which can be in the Dfs root directory or any subdirectory in the Dfs tree. You are probably familiar with using symbolic links to create references to files that exist on the same system, and perhaps crossing a local filesystem boundary (which ordinary Unix links cannot do). But maybe you didn't know that symbolic links have a more general functionality. Although we can't display its contents directly, as we could with a text or binary file, a symbolic link contains an ASCII text string naming what the link points to. For example, take a look at the listing for these symbolic links: $ ls -l wrdlnk alnk lrwxrwxrwx1 jay jay15 Mar 14 06:50 wrdlnk - /usr/dict/words lrwxrwxrwx1 jay jay 9 Mar 14 06:53 alnk - dreamtime As you can infer from the size of the wrdlnk link (15 bytes), the string /usr/dict/words is encoded into it. The size of alnk (9 bytes) is smaller, corresponding to the shorter name of dreamtime. Now let's create a link in our Dfs root for an SMB share: # cd /usr/local/samba/dfs # ln -s 'msdfs:maya\e' maya-e # ls -l maya-e lrwxrwxrwx1 root root 12 Mar 13 17:34 maya-e - msdfs:maya\e This link might appear as a broken link in a directory listing because it points to something that isn't a file on the local system. For example, the file command will report: $ file maya-e maya-e: broken symbolic link to msdfs:maya\e However, maya-e is a valid reference to the \\maya\e share when used with Samba's Dfs support. When Samba encounters this file, it sees the leading msdfs: and interprets the rest as the name of a remote share. The client is then redirected to the remote share. When creating links in the Dfs root directory, simply follow the same format, which in general is msdfs:server\share. Note that this is similar to a UNC appended onto the msdfs: string, except that in this case, the two backslashes preceding the server's name are omitted. TIP The names for the symbolic links in Dfs shares must be in all lowercase. In addition to regular network shares, you can use symbolic links of this type to reference Dfs shares on other Dfs servers. However, referencing printer
