How many file shares can I create on a Windows 2008 server?

Simple question.

How many file shares can I create on a single Windows 2008 server.  I'm hoping to have 300, but can settle for 200.
LVL 1
Gene KlamerusTechnical ArchitectAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Steven HarrisPresidentCommented:
With the introduction of SMB2 in Windows Server 2008, a single file server can host over 4 billion shares.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Gene KlamerusTechnical ArchitectAuthor Commented:
What about SMB1?

We've had issues with SMB2.
0
Steven HarrisPresidentCommented:
I have not been able to find any documentation on SMB1 limits, but I would venture that you are safe at 300 as I have run close to that on that a 2003 server.

How many users do you plan to have running concurrently?  That may be the bigger issue here.
0
Gene KlamerusTechnical ArchitectAuthor Commented:
We would have almost zero users.

The share is to host files for an application server (for a document management product).  By moving the files to a file share and off of our application server we can then set up additional application servers to provide the files to end-users (who connect only to the application server from their clients).

The application servers then share the files and the DB that's controlling the application overall.  This gives us redundancy for patching and upgrades as well as system outages.  We might even go to 3 application servers.  This also helps with scalability, but we have no scalability issues on the application server.

Ideally we'd use a NetApp to host the files, but we don't have that option.  I'd like to use a Windows Server (2008 or 2012) only hosting files to make it very stable and then as a "just in case" have DFS replication to a second File Server.  Then if we need to patch or upgrade the file share (or it has an issue) we have a secondary for the application servers to use.

What we want to have is a share for each year's documents for each of the 10 repositories provided by the application server so that's 1 shares/folders per year.  We also need to be able to retain up to 30 years files.

That said, we all know that no one keeps an application around for 30 years so we really don't need to have 300 shares, but if the high-end of what Windows 2008 can handle 500 file shares (for instance) then we have plenty of buffer to have no concerns.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows OS

From novice to tech pro — start learning today.