[Samba] Simple Samba PDC - tdbsam limitations?

[Ryan Novosielski]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Charles Marcus wrote:
> Charles Marcus, on 12/21/2007 8:06 AM, said the following:
>> What are the limitations of the tdbsam backend, with respect to
>> performance and the number of workstations/users it can reasonably be
>> expected to support?
> 
> Never mind - of course this is well documented in the most excellent
> 'The Official SAMBA-3 HOWTO and Reference Guide'...
> 
> For anyone curious - it is not generally recommended to use the tdbsam
> backend for sites with 250+ users, but this is only because these sites
> likely will be spread out and require BDCs and multiple servers...
> 
> They specifically mention one site using the tdbsam backend with 4,500+
> users with no performance problems whatsoever...
> 
> Sorry for the noise.

This is extremely timely for me, since I was looking into this subject
just this morning.

I have about 11,500 users on an smbpasswd file! :-o This does not work
very well, and we recently reached a breaking point. I looked into
tdbsam, figuring that that might be the easy way to go (I do not need
replication, as this backend is running a computer lab, not 11,500
concurrent users). The fact that my setup is two orders of magnitude
larger than the recommendation for tdbsam gives me pause.

Can anyone comment on this? I'm sorta in an emergency situation, not a
design situation... I'm almost looking at MySQL because that is
something that I could reasonably deploy in the next 48 hours. LDAP
would require at least some substantial reading for me, I'd think. Maybe
not.

=R

- --
 ---- _  _ _  _ ___  _  _  _
 |Y#| |  | |\/| |  \ |\ |  | |Ryan Novosielski - Systems Programmer II
 |$&| |__| |  | |__/ | \| _| |novosirj at umdnj.edu - 973/972.0922 (2-0922)
 \__/ Univ. of Med. and Dent.|IST/AST - NJMS Medical Science Bldg - C630
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHbAp0mb+gadEcsb4RAvpjAKChomcxXbQYo1CoFlxTlc2idTBNBACdE/VD
QyN68wBsW23xU+AKBVoPj7g=
=Lbkx
-----END PGP SIGNATURE-----