- Timestamp:
- Mar 1, 2010, 3:05:48 PM (15 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
branches/samba-3.3.x/docs/htmldocs/Samba3-ByExample/HA.html
r368 r411 1 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 13. Performance, Reliability, and Availability</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.7 5.2"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="up" href="RefSection.html" title="Part III. Reference Section"><link rel="prev" href="DomApps.html" title="Chapter 12. Integrating Additional Services"><link rel="next" href="ch14.html" title="Chapter 14. Samba Support"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 13. Performance, Reliability, and Availability</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="DomApps.html">Prev</a> </td><th width="60%" align="center">Part III. Reference Section</th><td width="20%" align="right"> <a accesskey="n" href="ch14.html">Next</a></td></tr></table><hr></div><div class="chapter" title="Chapter 13. Performance, Reliability, and Availability"><div class="titlepage"><div><div><h2 class="title"><a name="HA"></a>Chapter 13. Performance, Reliability, and Availability</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="HA.html#id2625018">Introduction</a></span></dt><dt><span class="sect1"><a href="HA.html#id2625115">Dissection and Discussion</a></span></dt><dt><span class="sect1"><a href="HA.html#id2625588">Guidelines for Reliable Samba Operation</a></span></dt><dd><dl><dt><span class="sect2"><a href="HA.html#id2625615">Name Resolution</a></span></dt><dt><span class="sect2"><a href="HA.html#id2626091">Samba Configuration</a></span></dt><dt><span class="sect2"><a href="HA.html#id2626419">Use and Location of BDCs</a></span></dt><dt><span class="sect2"><a href="HA.html#id2626494">Use One Consistent Version of MS Windows Client</a></span></dt><dt><span class="sect2"><a href="HA.html#id2626516">For Scalability, Use SAN-Based Storage on Samba Servers</a></span></dt><dt><span class="sect2"><a href="HA.html#id2626565">Distribute Network Load with MSDFS</a></span></dt><dt><span class="sect2"><a href="HA.html#id2626620">Replicate Data to Conserve Peak-Demand Wide-Area Bandwidth</a></span></dt><dt><span class="sect2"><a href="HA.html#id2626666">Hardware Problems</a></span></dt><dt><span class="sect2"><a href="HA.html#id2626814">Large Directories</a></span></dt></dl></dd><dt><span class="sect1"><a href="HA.html#id2626917">Key Points Learned</a></span></dt></dl></div><p>2 <a class="indexterm" name="id26 24980"></a>3 <a class="indexterm" name="id26 24986"></a>4 <a class="indexterm" name="id26 24993"></a>1 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 13. Performance, Reliability, and Availability</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="up" href="RefSection.html" title="Part III. Reference Section"><link rel="prev" href="DomApps.html" title="Chapter 12. Integrating Additional Services"><link rel="next" href="ch14.html" title="Chapter 14. Samba Support"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 13. Performance, Reliability, and Availability</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="DomApps.html">Prev</a> </td><th width="60%" align="center">Part III. Reference Section</th><td width="20%" align="right"> <a accesskey="n" href="ch14.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="HA"></a>Chapter 13. Performance, Reliability, and Availability</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="HA.html#id2618932">Introduction</a></span></dt><dt><span class="sect1"><a href="HA.html#id2619030">Dissection and Discussion</a></span></dt><dt><span class="sect1"><a href="HA.html#id2619503">Guidelines for Reliable Samba Operation</a></span></dt><dd><dl><dt><span class="sect2"><a href="HA.html#id2619530">Name Resolution</a></span></dt><dt><span class="sect2"><a href="HA.html#id2620006">Samba Configuration</a></span></dt><dt><span class="sect2"><a href="HA.html#id2620334">Use and Location of BDCs</a></span></dt><dt><span class="sect2"><a href="HA.html#id2620409">Use One Consistent Version of MS Windows Client</a></span></dt><dt><span class="sect2"><a href="HA.html#id2620431">For Scalability, Use SAN-Based Storage on Samba Servers</a></span></dt><dt><span class="sect2"><a href="HA.html#id2620480">Distribute Network Load with MSDFS</a></span></dt><dt><span class="sect2"><a href="HA.html#id2620535">Replicate Data to Conserve Peak-Demand Wide-Area Bandwidth</a></span></dt><dt><span class="sect2"><a href="HA.html#id2620581">Hardware Problems</a></span></dt><dt><span class="sect2"><a href="HA.html#id2620728">Large Directories</a></span></dt></dl></dd><dt><span class="sect1"><a href="HA.html#id2620832">Key Points Learned</a></span></dt></dl></div><p> 2 <a class="indexterm" name="id2618895"></a> 3 <a class="indexterm" name="id2618901"></a> 4 <a class="indexterm" name="id2618908"></a> 5 5 Well, you have reached one of the last chapters of this book. It is customary to attempt 6 6 to wrap up the theme and contents of a book in what is generally regarded as the … … 11 11 </p><div class="blockquote"><table border="0" width="100%" cellspacing="0" cellpadding="0" class="blockquote" summary="Block quote"><tr><td width="10%" valign="top"> </td><td width="80%" valign="top"><p> 12 12 In a world so full of noise, how can the sparrow be heard? 13 </p></td><td width="10%" valign="top"> </td></tr><tr><td width="10%" valign="top"> </td><td colspan="2" align="right" valign="top">--<span class="attribution">Anonymous</span></td></tr></table></div><div class="sect1" title="Introduction"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2625018"></a>Introduction</h2></div></div></div><p>14 <a class="indexterm" name="id26 25026"></a>13 </p></td><td width="10%" valign="top"> </td></tr><tr><td width="10%" valign="top"> </td><td colspan="2" align="right" valign="top">--<span class="attribution">Anonymous</span></td></tr></table></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2618932"></a>Introduction</h2></div></div></div><p> 14 <a class="indexterm" name="id2618940"></a> 15 15 The sparrow is a small bird whose sounds are drowned out by the noise of the busy 16 16 world it lives in. Likewise, the simple steps that can be taken to improve the … … 21 21 custom tools and methods. Only passing comments are offered concerning these methods. 22 22 </p><p> 23 <a class="indexterm" name="id26 25056"></a>24 <a class="indexterm" name="id26 25062"></a>25 <a class="indexterm" name="id26 25069"></a>23 <a class="indexterm" name="id2618970"></a> 24 <a class="indexterm" name="id2618977"></a> 25 <a class="indexterm" name="id2618984"></a> 26 26 <a class="ulink" href="http://www.google.com/search?hl=en&lr=&ie=ISO-8859-1&q=samba+cluster&btnG=Google+Search" target="_top">A search</a> 27 for <span class="quote">“<span class="quote">samba cluster</span>”</span> produced 71,600 hits. And a search for <span class="quote">“<span class="quote">highly available samba</span>”</span>28 and <span class="quote">“<span class="quote">highly available windows</span>”</span>produced an amazing number of references.27 for “<span class="quote">samba cluster</span>” produced 71,600 hits. And a search for “<span class="quote">highly available samba</span>” 28 and “<span class="quote">highly available windows</span>” produced an amazing number of references. 29 29 It is clear from the resources on the Internet that Windows file and print services 30 30 availability, reliability, and scalability are of vital interest to corporate network users. 31 31 </p><p> 32 <a class="indexterm" name="id26 25103"></a>32 <a class="indexterm" name="id2619018"></a> 33 33 So without further background, you can review a checklist of simple steps that 34 34 can be taken to ensure acceptable network performance while keeping costs of ownership 35 35 well under control. 36 </p></div><div class="sect1" title="Dissection and Discussion"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2625115"></a>Dissection and Discussion</h2></div></div></div><p>37 <a class="indexterm" name="id26 25123"></a>38 <a class="indexterm" name="id26 25130"></a>36 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2619030"></a>Dissection and Discussion</h2></div></div></div><p> 37 <a class="indexterm" name="id2619038"></a> 38 <a class="indexterm" name="id2619045"></a> 39 39 If it is your purpose to get the best mileage out of your Samba servers, there is one rule that 40 40 must be obeyed. If you want the best, keep your implementation as simple as possible. You may … … 45 45 complex ones. 46 46 </p><p> 47 <a class="indexterm" name="id26 25152"></a>48 <a class="indexterm" name="id26 25159"></a>47 <a class="indexterm" name="id2619067"></a> 48 <a class="indexterm" name="id2619074"></a> 49 49 Problems reported by users fall into three categories: configurations that do not work, those 50 50 that have broken behavior, and poor performance. The term <span class="emphasis"><em>broken behavior</em></span> … … 55 55 and at other times not listing them even though the machines are in use on the network. 56 56 </p><p> 57 <a class="indexterm" name="id26 25186"></a>58 <a class="indexterm" name="id26 25193"></a>59 <a class="indexterm" name="id26 25200"></a>60 <a class="indexterm" name="id26 25207"></a>61 <a class="indexterm" name="id26 25213"></a>62 <a class="indexterm" name="id26 25220"></a>57 <a class="indexterm" name="id2619101"></a> 58 <a class="indexterm" name="id2619108"></a> 59 <a class="indexterm" name="id2619115"></a> 60 <a class="indexterm" name="id2619121"></a> 61 <a class="indexterm" name="id2619128"></a> 62 <a class="indexterm" name="id2619135"></a> 63 63 A significant number of reports concern problems with the <code class="literal">smbfs</code> file system 64 64 driver that is part of the Linux kernel, not part of Samba. Users continue to interpret that … … 71 71 Samba and are really foreign to it. 72 72 </p><p> 73 <a class="indexterm" name="id26 25281"></a>73 <a class="indexterm" name="id2619196"></a> 74 74 The new project, <code class="literal">cifsfs</code>, is destined to replace <code class="literal">smbfs</code>. 75 75 It, too, is not part of Samba, even though one of the Samba Team members is a prime mover in … … 77 77 </p><p> 78 78 Table 13.1 lists typical causes of: 79 </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Not Working (NW)</p></li><li class="listitem"><p>Broken Behavior (BB)</p></li><li class="listitem"><p>Poor Performance (PP)</p></li></ul></div><div class="table"><a name="ProbList"></a><p class="title"><b>Table 13.1. Effect of Common Problems</b></p><div class="table-contents"><table summary="Effect of Common Problems" border="1"><colgroup><col align="left"><col align="center"><col align="center"><col align="center"></colgroup><thead><tr><th align="left"><p>Problem</p></th><th align="center"><p>NW</p></th><th align="center"><p>BB</p></th><th align="center"><p>PP</p></th></tr></thead><tbody><tr><td align="left"><p>File locking</p></td><td align="center"><p>-</p></td><td align="center"><p>X</p></td><td align="center"><p>-</p></td></tr><tr><td align="left"><p>Hardware problems</p></td><td align="center"><p>X</p></td><td align="center"><p>X</p></td><td align="center"><p>X</p></td></tr><tr><td align="left"><p>Incorrect authentication</p></td><td align="center"><p>X</p></td><td align="center"><p>X</p></td><td align="center"><p>-</p></td></tr><tr><td align="left"><p>Incorrect configuration</p></td><td align="center"><p>X</p></td><td align="center"><p>X</p></td><td align="center"><p>X</p></td></tr><tr><td align="left"><p>LDAP problems</p></td><td align="center"><p>X</p></td><td align="center"><p>X</p></td><td align="center"><p>-</p></td></tr><tr><td align="left"><p>Name resolution</p></td><td align="center"><p>X</p></td><td align="center"><p>X</p></td><td align="center"><p>X</p></td></tr><tr><td align="left"><p>Printing problems</p></td><td align="center"><p>X</p></td><td align="center"><p>X</p></td><td align="center"><p>-</p></td></tr><tr><td align="left"><p>Slow file transfer</p></td><td align="center"><p>-</p></td><td align="center"><p>-</p></td><td align="center"><p>X</p></td></tr><tr><td align="left"><p>Winbind problems</p></td><td align="center"><p>X</p></td><td align="center"><p>X</p></td><td align="center"><p>-</p></td></tr></tbody></table></div></div><br class="table-break"><p>80 <a class="indexterm" name="id26 25575"></a>79 </p><div class="itemizedlist"><ul type="disc"><li><p>Not Working (NW)</p></li><li><p>Broken Behavior (BB)</p></li><li><p>Poor Performance (PP)</p></li></ul></div><div class="table"><a name="ProbList"></a><p class="title"><b>Table 13.1. Effect of Common Problems</b></p><div class="table-contents"><table summary="Effect of Common Problems" border="1"><colgroup><col align="left"><col align="center"><col align="center"><col align="center"></colgroup><thead><tr><th align="left"><p>Problem</p></th><th align="center"><p>NW</p></th><th align="center"><p>BB</p></th><th align="center"><p>PP</p></th></tr></thead><tbody><tr><td align="left"><p>File locking</p></td><td align="center"><p>-</p></td><td align="center"><p>X</p></td><td align="center"><p>-</p></td></tr><tr><td align="left"><p>Hardware problems</p></td><td align="center"><p>X</p></td><td align="center"><p>X</p></td><td align="center"><p>X</p></td></tr><tr><td align="left"><p>Incorrect authentication</p></td><td align="center"><p>X</p></td><td align="center"><p>X</p></td><td align="center"><p>-</p></td></tr><tr><td align="left"><p>Incorrect configuration</p></td><td align="center"><p>X</p></td><td align="center"><p>X</p></td><td align="center"><p>X</p></td></tr><tr><td align="left"><p>LDAP problems</p></td><td align="center"><p>X</p></td><td align="center"><p>X</p></td><td align="center"><p>-</p></td></tr><tr><td align="left"><p>Name resolution</p></td><td align="center"><p>X</p></td><td align="center"><p>X</p></td><td align="center"><p>X</p></td></tr><tr><td align="left"><p>Printing problems</p></td><td align="center"><p>X</p></td><td align="center"><p>X</p></td><td align="center"><p>-</p></td></tr><tr><td align="left"><p>Slow file transfer</p></td><td align="center"><p>-</p></td><td align="center"><p>-</p></td><td align="center"><p>X</p></td></tr><tr><td align="left"><p>Winbind problems</p></td><td align="center"><p>X</p></td><td align="center"><p>X</p></td><td align="center"><p>-</p></td></tr></tbody></table></div></div><br class="table-break"><p> 80 <a class="indexterm" name="id2619490"></a> 81 81 It is obvious to all that the first requirement (as a matter of network hygiene) is to eliminate 82 82 problems that affect basic network operation. This book has provided sufficient working examples 83 83 to help you to avoid all these problems. 84 </p></div><div class="sect1" title="Guidelines for Reliable Samba Operation"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2625588"></a>Guidelines for Reliable Samba Operation</h2></div></div></div><p>85 <a class="indexterm" name="id26 25596"></a>86 <a class="indexterm" name="id26 25603"></a>84 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2619503"></a>Guidelines for Reliable Samba Operation</h2></div></div></div><p> 85 <a class="indexterm" name="id2619511"></a> 86 <a class="indexterm" name="id2619518"></a> 87 87 Your objective is to provide a network that works correctly, can grow at all times, is resilient 88 88 at times of extreme demand, and can scale to meet future needs. The following subject areas provide 89 89 pointers that can help you today. 90 </p><div class="sect2" title="Name Resolution"><div class="titlepage"><div><div><h3 class="title"><a name="id2625615"></a>Name Resolution</h3></div></div></div><p>90 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2619530"></a>Name Resolution</h3></div></div></div><p> 91 91 There are three basic current problem areas: bad hostnames, routed networks, and network collisions. 92 92 These are covered in the following discussion. 93 </p><div class="sect3" title="Bad Hostnames"><div class="titlepage"><div><div><h4 class="title"><a name="id2625627"></a>Bad Hostnames</h4></div></div></div><p>94 <a class="indexterm" name="id26 25635"></a>95 <a class="indexterm" name="id26 25644"></a>96 <a class="indexterm" name="id26 25651"></a>97 <a class="indexterm" name="id26 25658"></a>98 <a class="indexterm" name="id26 25665"></a>93 </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2619542"></a>Bad Hostnames</h4></div></div></div><p> 94 <a class="indexterm" name="id2619550"></a> 95 <a class="indexterm" name="id2619559"></a> 96 <a class="indexterm" name="id2619566"></a> 97 <a class="indexterm" name="id2619573"></a> 98 <a class="indexterm" name="id2619579"></a> 99 99 When configured as a DHCP client, a number of Linux distributions set the system hostname 100 100 to <code class="constant">localhost</code>. If the parameter <em class="parameter"><code>netbios name</code></em> is not … … 108 108 correctly. 109 109 </p><p> 110 <a class="indexterm" name="id26 25719"></a>110 <a class="indexterm" name="id2619634"></a> 111 111 A few sites have tried to name Windows clients and Samba servers with a name that begins 112 112 with the digits 1-9. This does not work either because it may result in the client or 113 113 server attempting to use that name as an IP address. 114 114 </p><p> 115 <a class="indexterm" name="id26 25733"></a>116 <a class="indexterm" name="id26 25742"></a>115 <a class="indexterm" name="id2619648"></a> 116 <a class="indexterm" name="id2619657"></a> 117 117 A Samba server called <code class="constant">FRED</code> in a NetBIOS domain called <code class="constant">COLLISION</code> 118 118 in a network environment that is part of the fully-qualified Internet domain namespace known … … 122 122 attempts to resolve <code class="constant">fred.parrots.com.parrots.com</code>, which most likely 123 123 fails given that you probably do not have this in your DNS namespace. 124 </p><div class="note" title="Note"style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>125 <a class="indexterm" name="id26 25787"></a>126 <a class="indexterm" name="id26 25796"></a>127 <a class="indexterm" name="id26 25803"></a>124 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> 125 <a class="indexterm" name="id2619702"></a> 126 <a class="indexterm" name="id2619711"></a> 127 <a class="indexterm" name="id2619717"></a> 128 128 An Active Directory realm called <code class="constant">collision.parrots.com</code> is perfectly okay, 129 129 although it too must be capable of being resolved via DNS, something that functions correctly 130 130 if Windows 200x ADS has been properly installed and configured. 131 </p></div></div><div class="sect3" title="Routed Networks"><div class="titlepage"><div><div><h4 class="title"><a name="id2625819"></a>Routed Networks</h4></div></div></div><p>132 <a class="indexterm" name="id26 25827"></a>133 <a class="indexterm" name="id26 25834"></a>134 <a class="indexterm" name="id26 25843"></a>131 </p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2619734"></a>Routed Networks</h4></div></div></div><p> 132 <a class="indexterm" name="id2619742"></a> 133 <a class="indexterm" name="id2619748"></a> 134 <a class="indexterm" name="id2619758"></a> 135 135 NetBIOS networks (Windows networking with NetBIOS over TCP/IP enabled) makes extensive use 136 136 of UDP-based broadcast traffic, as you saw during the exercises in <a class="link" href="primer.html" title="Chapter 16. Networking Primer">“Networking Primer”</a>. 137 137 </p><p> 138 <a class="indexterm" name="id26 25862"></a>139 <a class="indexterm" name="id26 25869"></a>140 <a class="indexterm" name="id26 25876"></a>138 <a class="indexterm" name="id2619777"></a> 139 <a class="indexterm" name="id2619784"></a> 140 <a class="indexterm" name="id2619791"></a> 141 141 UDP broadcast traffic is not forwarded by routers. This means that NetBIOS broadcast-based 142 142 networking cannot function across routed networks (i.e., multi-subnet networks) unless 143 143 special provisions are made: 144 </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>145 <a class="indexterm" name="id26 25893"></a>146 <a class="indexterm" name="id26 25900"></a>147 <a class="indexterm" name="id26 25907"></a>144 </p><div class="itemizedlist"><ul type="disc"><li><p> 145 <a class="indexterm" name="id2619808"></a> 146 <a class="indexterm" name="id2619815"></a> 147 <a class="indexterm" name="id2619822"></a> 148 148 Either install on every Windows client an LMHOSTS file (located in the directory 149 149 <code class="filename">C:\windows\system32\drivers\etc</code>). It is also necessary to … … 151 151 and <em class="parameter"><code>remote browse sync</code></em>. For more information, refer to the online 152 152 manual page for the <code class="filename">smb.conf</code> file. 153 </p></li><li class="listitem"><p>154 <a class="indexterm" name="id26 25952"></a>153 </p></li><li><p> 154 <a class="indexterm" name="id2619867"></a> 155 155 Or configure Samba as a WINS server, and configure all network clients to use that 156 156 WINS server in their TCP/IP configuration. 157 </p></li></ul></div><div class="note" title="Note"style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>158 <a class="indexterm" name="id26 25969"></a>159 <a class="indexterm" name="id26 25979"></a>157 </p></li></ul></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> 158 <a class="indexterm" name="id2619884"></a> 159 <a class="indexterm" name="id2619893"></a> 160 160 The use of DNS is not an acceptable substitute for WINS. DNS does not store specific 161 161 information regarding NetBIOS networking particulars that get stored in the WINS 162 162 name resolution database and that Windows clients require and depend on. 163 </p></div></div><div class="sect3" title="Network Collisions"><div class="titlepage"><div><div><h4 class="title"><a name="id2625992"></a>Network Collisions</h4></div></div></div><p>164 <a class="indexterm" name="id26 25999"></a>165 <a class="indexterm" name="id26 26009"></a>166 <a class="indexterm" name="id26 26018"></a>167 <a class="indexterm" name="id26 26025"></a>163 </p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2619906"></a>Network Collisions</h4></div></div></div><p> 164 <a class="indexterm" name="id2619914"></a> 165 <a class="indexterm" name="id2619923"></a> 166 <a class="indexterm" name="id2619933"></a> 167 <a class="indexterm" name="id2619940"></a> 168 168 Excessive network activity causes NetBIOS network timeouts. Timeouts may result in 169 169 blue screen of death (BSOD) experiences. High collision rates may be caused by excessive … … 174 174 in <a class="link" href="primer.html" title="Chapter 16. Networking Primer">“Networking Primer”</a>. 175 175 </p><p> 176 <a class="indexterm" name="id26 26053"></a>177 <a class="indexterm" name="id26 26060"></a>178 <a class="indexterm" name="id26 26067"></a>176 <a class="indexterm" name="id2619968"></a> 177 <a class="indexterm" name="id2619975"></a> 178 <a class="indexterm" name="id2619982"></a> 179 179 Under no circumstances should the facility be supported by many routers, known as <code class="constant">NetBIOS 180 180 forwarding</code>, unless you know exactly what you are doing. Inappropriate use of this … … 184 184 less than 15 KB/sec. After the NetBIOS forwarding was turned off, file transfer performance 185 185 immediately returned to 11 MB/sec. 186 </p></div></div><div class="sect2" title="Samba Configuration"><div class="titlepage"><div><div><h3 class="title"><a name="id2626091"></a>Samba Configuration</h3></div></div></div><p>186 </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2620006"></a>Samba Configuration</h3></div></div></div><p> 187 187 As a general rule, the contents of the <code class="filename">smb.conf</code> file should be kept as simple as possible. 188 188 No parameter should be specified unless you know it is essential to operation. 189 189 </p><p> 190 <a class="indexterm" name="id262 6111"></a>191 <a class="indexterm" name="id262 6118"></a>192 <a class="indexterm" name="id262 6125"></a>190 <a class="indexterm" name="id2620026"></a> 191 <a class="indexterm" name="id2620033"></a> 192 <a class="indexterm" name="id2620040"></a> 193 193 Many UNIX administrators like to fully document the settings in the <code class="filename">smb.conf</code> file. This is a 194 194 bad idea because it adds content to the file. The <code class="filename">smb.conf</code> file is re-read by every <code class="literal">smbd</code> … … 198 198 It is recommended to keep a fully documented <code class="filename">smb.conf</code> file on hand, and then to operate Samba only 199 199 with an optimized file. 200 </p><p><a class="indexterm" name="id262 6175"></a>200 </p><p><a class="indexterm" name="id2620090"></a> 201 201 The preferred way to maintain a documented file is to call it something like <code class="filename">smb.conf.master</code>. 202 202 You can generate the optimized file by executing: … … 224 224 Press enter to see a dump of your service definitions 225 225 </pre><p> 226 <a class="indexterm" name="id262 6234"></a>226 <a class="indexterm" name="id2620149"></a> 227 227 You now, of course, press the enter key to complete the command, or else abort it by pressing Ctrl-C. 228 228 The important thing to note is the noted Server role, as well as warning messages. Noted configuration … … 234 234 </pre><p> 235 235 </p><p> 236 <a class="indexterm" name="id262 6262"></a>237 <a class="indexterm" name="id262 6269"></a>238 <a class="indexterm" name="id262 6276"></a>236 <a class="indexterm" name="id2620177"></a> 237 <a class="indexterm" name="id2620184"></a> 238 <a class="indexterm" name="id2620191"></a> 239 239 There are two parameters that can cause severe network performance degradation: <em class="parameter"><code>socket options</code></em> 240 240 and <em class="parameter"><code>socket address</code></em>. The <em class="parameter"><code>socket options</code></em> parameter was often necessary … … 242 242 this parameter being set. Do not use either parameter unless it has been proven necessary to use them. 243 243 </p><p> 244 <a class="indexterm" name="id262 6310"></a>245 <a class="indexterm" name="id262 6317"></a>246 <a class="indexterm" name="id262 6323"></a>247 <a class="indexterm" name="id262 6330"></a>244 <a class="indexterm" name="id2620225"></a> 245 <a class="indexterm" name="id2620231"></a> 246 <a class="indexterm" name="id2620238"></a> 247 <a class="indexterm" name="id2620245"></a> 248 248 Another <code class="filename">smb.conf</code> parameter that may cause severe network performance degradation is the 249 249 <em class="parameter"><code>strict sync</code></em> parameter. Do not use this at all. There is no good reason … … 252 252 degrade network performance, so do not set it; if you must, do so with caution. 253 253 </p><p> 254 <a class="indexterm" name="id262 6372"></a>255 <a class="indexterm" name="id262 6379"></a>256 <a class="indexterm" name="id262 6386"></a>257 <a class="indexterm" name="id262 6393"></a>254 <a class="indexterm" name="id2620287"></a> 255 <a class="indexterm" name="id2620294"></a> 256 <a class="indexterm" name="id2620301"></a> 257 <a class="indexterm" name="id2620308"></a> 258 258 Finally, many network administrators deliberately disable opportunistic locking support. While this 259 259 does not degrade Samba performance, it significantly degrades Windows client performance because … … 263 263 oplock support for operations that are tolerant of it. See <a class="link" href="appendix.html#ch12dblck" title="Shared Data Integrity">“Shared Data Integrity”</a> for more 264 264 information. 265 </p></div><div class="sect2" title="Use and Location of BDCs"><div class="titlepage"><div><div><h3 class="title"><a name="id2626419"></a>Use and Location of BDCs</h3></div></div></div><p>266 <a class="indexterm" name="id262 6427"></a>267 <a class="indexterm" name="id262 6433"></a>268 <a class="indexterm" name="id262 6440"></a>269 <a class="indexterm" name="id262 6446"></a>270 <a class="indexterm" name="id262 6453"></a>265 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2620334"></a>Use and Location of BDCs</h3></div></div></div><p> 266 <a class="indexterm" name="id2620342"></a> 267 <a class="indexterm" name="id2620348"></a> 268 <a class="indexterm" name="id2620354"></a> 269 <a class="indexterm" name="id2620361"></a> 270 <a class="indexterm" name="id2620368"></a> 271 271 On a network segment where there is a PDC and a BDC, the BDC carries the bulk of the network logon 272 272 processing. If the BDC is a heavily loaded server, the PDC carries a greater proportion of … … 276 276 and is undesirable. 277 277 </p><p> 278 <a class="indexterm" name="id262 6472"></a>279 <a class="indexterm" name="id262 6479"></a>278 <a class="indexterm" name="id2620387"></a> 279 <a class="indexterm" name="id2620394"></a> 280 280 As a general guide, instead of adding domain member servers to a network, you would be better advised 281 281 to add BDCs until there are fewer than 30 Windows clients per BDC. Beyond that ratio, you should add 282 282 domain member servers. This practice ensures that there are always sufficient domain controllers 283 283 to handle logon requests and authentication traffic. 284 </p></div><div class="sect2" title="Use One Consistent Version of MS Windows Client"><div class="titlepage"><div><div><h3 class="title"><a name="id2626494"></a>Use One Consistent Version of MS Windows Client</h3></div></div></div><p>284 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2620409"></a>Use One Consistent Version of MS Windows Client</h3></div></div></div><p> 285 285 Every network client has its own peculiarities. From a management perspective, it is easier to deal 286 286 with one version of MS Windows that is maintained to a consistent update level than it is to deal … … 290 290 have necessitated special handling from the Samba server end. If you want to remain sane, keep you 291 291 client workstation configurations consistent. 292 </p></div><div class="sect2" title="For Scalability, Use SAN-Based Storage on Samba Servers"><div class="titlepage"><div><div><h3 class="title"><a name="id2626516"></a>For Scalability, Use SAN-Based Storage on Samba Servers</h3></div></div></div><p>293 <a class="indexterm" name="id262 6524"></a>294 <a class="indexterm" name="id262 6531"></a>292 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2620431"></a>For Scalability, Use SAN-Based Storage on Samba Servers</h3></div></div></div><p> 293 <a class="indexterm" name="id2620439"></a> 294 <a class="indexterm" name="id2620446"></a> 295 295 Many SAN-based storage systems permit more than one server to share a common data store. 296 296 Use of a shared SAN data store means that you do not need to use time- and resource-hungry data 297 297 synchronization techniques. 298 298 </p><p> 299 <a class="indexterm" name="id262 6545"></a>300 <a class="indexterm" name="id262 6552"></a>299 <a class="indexterm" name="id2620460"></a> 300 <a class="indexterm" name="id2620467"></a> 301 301 The use of a collection of relatively low-cost front-end Samba servers that are coupled to 302 302 a shared backend SAN data store permits load distribution while containing costs below that 303 303 of installing and managing a complex clustering facility. 304 </p></div><div class="sect2" title="Distribute Network Load with MSDFS"><div class="titlepage"><div><div><h3 class="title"><a name="id2626565"></a>Distribute Network Load with MSDFS</h3></div></div></div><p>305 <a class="indexterm" name="id262 6574"></a>306 <a class="indexterm" name="id262 6580"></a>304 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2620480"></a>Distribute Network Load with MSDFS</h3></div></div></div><p> 305 <a class="indexterm" name="id2620488"></a> 306 <a class="indexterm" name="id2620495"></a> 307 307 Microsoft DFS (distributed file system) technology has been implemented in Samba. MSDFS permits 308 308 data to be accessed from a single share and yet to actually be distributed across multiple actual … … 310 310 implementation of an MSDFS installation. 311 311 </p><p> 312 <a class="indexterm" name="id262 6599"></a>313 <a class="indexterm" name="id262 6608"></a>312 <a class="indexterm" name="id2620514"></a> 313 <a class="indexterm" name="id2620523"></a> 314 314 The combination of multiple backend servers together with a front-end server and use of MSDFS 315 315 can achieve almost the same as you would obtain with a clustered Samba server. 316 </p></div><div class="sect2" title="Replicate Data to Conserve Peak-Demand Wide-Area Bandwidth"><div class="titlepage"><div><div><h3 class="title"><a name="id2626620"></a>Replicate Data to Conserve Peak-Demand Wide-Area Bandwidth</h3></div></div></div><p>317 <a class="indexterm" name="id262 6629"></a>318 <a class="indexterm" name="id262 6636"></a>319 <a class="indexterm" name="id262 6642"></a>316 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2620535"></a>Replicate Data to Conserve Peak-Demand Wide-Area Bandwidth</h3></div></div></div><p> 317 <a class="indexterm" name="id2620544"></a> 318 <a class="indexterm" name="id2620550"></a> 319 <a class="indexterm" name="id2620557"></a> 320 320 Consider using <code class="literal">rsync</code> to replicate data across the WAN during times 321 321 of low utilization. Users can then access the replicated data store rather than needing to do so … … 324 324 implementation if you choose to permit modification and return replication of the modified file; 325 325 otherwise, you may inadvertently overwrite important data. 326 </p></div><div class="sect2" title="Hardware Problems"><div class="titlepage"><div><div><h3 class="title"><a name="id2626666"></a>Hardware Problems</h3></div></div></div><p>327 <a class="indexterm" name="id262 6674"></a>328 <a class="indexterm" name="id262 6681"></a>329 <a class="indexterm" name="id262 6688"></a>330 <a class="indexterm" name="id262 6694"></a>331 <a class="indexterm" name="id262 6704"></a>332 <a class="indexterm" name="id262 6713"></a>326 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2620581"></a>Hardware Problems</h3></div></div></div><p> 327 <a class="indexterm" name="id2620588"></a> 328 <a class="indexterm" name="id2620595"></a> 329 <a class="indexterm" name="id2620602"></a> 330 <a class="indexterm" name="id2620609"></a> 331 <a class="indexterm" name="id2620618"></a> 332 <a class="indexterm" name="id2620628"></a> 333 333 Networking hardware prices have fallen sharply over the past 5 years. A surprising number 334 334 of Samba networking problems over this time have been traced to defective network interface 335 335 cards (NICs) or defective HUBs, switches, and cables. 336 336 </p><p> 337 <a class="indexterm" name="id262 6729"></a>337 <a class="indexterm" name="id2620644"></a> 338 338 Not surprising is the fact that network administrators do not like to be shown to have made 339 339 a bad decision. Money saved in buying low-cost hardware may result in high costs incurred 340 340 in corrective action. 341 341 </p><p> 342 <a class="indexterm" name="id262 6743"></a>343 <a class="indexterm" name="id262 6750"></a>344 <a class="indexterm" name="id262 6757"></a>345 <a class="indexterm" name="id262 6764"></a>346 <a class="indexterm" name="id262 6771"></a>342 <a class="indexterm" name="id2620658"></a> 343 <a class="indexterm" name="id2620665"></a> 344 <a class="indexterm" name="id2620672"></a> 345 <a class="indexterm" name="id2620679"></a> 346 <a class="indexterm" name="id2620686"></a> 347 347 Defective NICs, HUBs, and switches may appear as intermittent network access problems, intermittent 348 348 or persistent data corruption, slow network throughput, low performance, or even as BSOD … … 353 353 Defective hardware problems may take patience and persistence before the real cause can be discovered. 354 354 </p><p> 355 <a class="indexterm" name="id262 6794"></a>355 <a class="indexterm" name="id2620709"></a> 356 356 Networking hardware defects can significantly impact perceived Samba performance, but defective 357 357 RAID controllers as well as SCSI and IDE hard disk controllers have also been known to impair Samba server … … 360 360 administrator until the entire server was replaced. While you may well think that this would never 361 361 happen to you, experience shows that given the right (unfortunate) circumstances, this can happen to anyone. 362 </p></div><div class="sect2" title="Large Directories"><div class="titlepage"><div><div><h3 class="title"><a name="id2626814"></a>Large Directories</h3></div></div></div><p>362 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2620728"></a>Large Directories</h3></div></div></div><p> 363 363 There exist applications that create or manage directories containing many thousands of files. Such 364 364 applications typically generate many small files (less than 100 KB). At the best of times, under UNIX, … … 400 400 as specified in the <code class="filename">smb.conf</code> stanza. This means that smbd will not be able to find lower case 401 401 filenames with these settings. Note, this is done on a per-share basis. 402 </p></div></div><div class="sect1" title="Key Points Learned"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2626917"></a>Key Points Learned</h2></div></div></div><p>402 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2620832"></a>Key Points Learned</h2></div></div></div><p> 403 403 This chapter has touched in broad sweeps on a number of simple steps that can be taken 404 404 to ensure that your Samba network is resilient, scalable, and reliable, and that it … … 409 409 her an even break. 410 410 </p><p> 411 <a class="indexterm" name="id262 6938"></a>411 <a class="indexterm" name="id2620853"></a> 412 412 Last, but not least, you should not only keep the network design simple, but also be sure it is 413 413 well documented. This book may serve as your pattern for documenting every
Note:
See TracChangeset
for help on using the changeset viewer.
