Sharepoint 2010 Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint 2010       RSS Feeds

SharePoint 2010 NLB

  Date: May 30    Category: Sharepoint 2010    Views: 1569

I just have some urgent questions and i really wish if i can get some answers
and help regarding the same.
I want to Have a Full SharePoint 2010 Fail-over Environment which including 5
Servers, Below:

- Three SQL 2008 R2 Enterprise SP1 Running as Mirroring (Principal, Mirror and
Wetness). For a Full SQL Fail-over.
- Tow Servers for SharePoint 2010, Which i want them to give me the Full Power
of Fail-over, Which means if one Server went down the other should ACT the same
(SharePoint CA, Web Apps, and Service Apps).

BTW, All Servers is 64-Bit with Windows Server 2008 R2 Enterprise SP1.

So, my question is: DO i need to have a Windows NLB on these 2 SharePoint
Servers or Maybe any other NLB, and How can i achieve this Kind of Scenario?
If there is some documentations or such an article please share it with me.



20 Answers Found

Answer #1    Answered On: May 30    

Yes, to get failover in that kind of environment you would need some kind of
Network Load Balancing for the Front Ends. But it wouldn't necessarily need
to be Windows NLB.

A good place to start when building this kind of environment is the
following Technet article.


Answer #2    Answered On: May 30    

But, what if that there is no 3rd Party solution
for NLB, Do i still be able to run Such environment with Windows NLB?
If yes, Is there any recommendations or How-To Best Practice?

Answer #3    Answered On: May 30    

You can either choose a third party product (hardware LB is the best option). If
this is not an option, you can either choose windows NLB or use Microsofts TMG
to do the balancing for you. We currently use Windows NLB, but this has some
side affects (the balancing is done using ip-hash calculation and if not
implemented properly, you’ll end up with one server doing all the work..) But
it is kind of free. If you use TMG, it is probably better, but you will need
infra + licenses.

Please be carefull in this discussion, load balancing and fail over capacity
tend to mix here
%2D8320%2Dba5369008acb&ID=209> &ID=209). Specifying what you need is essential;
I use NLB mainly for fail over (just remove a server from the nlb, patch it and
put I back in) but that is not always the correct way ;-)

This might give you a good start on WNLB


Answer #4    Answered On: May 30    

Thanks a lot for your informations and help.
Of course, I'll get back to you guys in fact if I face any problems :)

Answer #5    Answered On: May 30    

Was going to point him to the same websites.

From what it appears, he is over his head. NLB isn't one of those things you
keep going to to user group for support. It requires much more understanding
and planning than we can provide as a group.

Perhaps the OP should find a class on NLB in his area.

Answer #6    Answered On: May 30    

Thanks for your answer. But, what if that there is no 3rd Party solution
for NLB, Do i still be able to run Such environment with Windows NLB?
If yes, Is there any recommendations or How-To Best Practice?

Answer #7    Answered On: May 30    

Windows NLB will work fine in this scenario. The point is that its not the only
NLB system you can use. But it is certainly one that will work.

Answer #8    Answered On: May 30    

If u wish to have disaster recovery then NLB is not the solution

NLB is just to balance your high user load, something like if you hv 10m
users then your system may slow if you hv only one iis server in such
senario we need a NLB to balance out the user load on servers. also like one
farm with 2 WFEs.

now for disaster recovery you can con figure one more sharepoint system with
(on same farm) same config db. so if you hv issues on main sharepoint system
u can up the second system which is bind with same config and content db.
hope this info will help.

Answer #9    Answered On: May 30    

If you check his original message you will see that he also intends to do SQL
High Availability mirroring. In this scenario creating two windows front end
servers that are network load balanced is the other half of the equation. So
NLB is a PART of the solution. It won’t do it alone, but it is an integral

Answer #10    Answered On: May 30    

Thanks for the explanation. So, do you really suggestion me to have these 2
SharePoint Server running with windows NLB.

Answer #11    Answered On: May 30    

If you don't already have a hardware based Network Load Balancer then yes.

Answer #12    Answered On: May 30    

The problem here that the hardware is limited to build
this environment, i mean i have only those 5 servers that i already mention at
the 1st mail. which including 2 servers for SharePoint. and as you saying the
point of this environment to have Disaster Solution for the environment.

So, Please i really need a Better idea and solution for this kind of scenario,
Cause i really confused.

Answer #13    Answered On: May 30    

I'm not sure I understand. With the 5 servers you mentioned you can build a
Fault Tolerant environment. Set it up as follows:

2 SharePoint Servers running Windows NLB

3 SQL servers doing Mirroring in High Availability mode. (1 active, 1 passive,
1 witness)

There is no better way to do it with only 5 servers. Without additional
resources like an SQL cluster this is pretty much the minimum for a Fault
Tolerant High Availability environment.

Answer #14    Answered On: May 30    

Thanks. So, let me summarize the steps that i can follow to finish
this build successful:
1- I already have all the SQL Boxes up-and running with 3 different instances
name. (BTW, I'm Planning to use Alias name in both SharePoint 2010).
2- Build the Windows NLB for the 2 SharePoint Servers.
3- Build the 1st SharePoint Server using the Alias name to connect to the Active
SQL (SQL1), Run the Configuration wizard and finish all the steps to make the
1st SharePoint Box up-and-running.

4- Build the 2nd SharePoint Server using also the Alias name to connect to the
same SharePoint_Config.DB and Choice Advanced option while running the
Configuration Wizard to make this server also hosting the CA, finish all the
steps to make sure that this server also is up-and running.
5- Configure the CA AAM to host the same in just one specific URL.

6- Make a full Backup for All the SharePoint DB's and then restored in the 2nd
Passive SQL (SQL2), and start the Mirroring Configuration.

Please Correct me if i am wrong.

Answer #15    Answered On: May 30    

Take a look at the planning guide link I sent you. Step #4 is wrong. You
don’t connect the passive SQL server to SharePoint. You set it up, establish
mirroring and then list it as the Failover server in SharePoint. It’s all on

Answer #16    Answered On: May 30    

I think you have done a wonderful job trying to assist this user but it appears
this is another contractor that took an assignment he was unqualified for.

Much of what was asked is not at the sole discretion of the SP admin but the
backend group of DBA's and sysadmins.

In response to the OP it appears that you are in way over your depth of
knowledge perhaps you should hire a SP consulting group to assist you.

Answer #17    Answered On: May 30    

Backend GROUP of DBAs and sysadmins? I think I need a raise!

Answer #18    Answered On: May 30    

Possibly. But he could as easily be in a relatively small IT shop who are
looking to do everything themselves and don't have a backend group. But you
are correct that he probably needs more help than can be provided on an
email list.

Answer #19    Answered On: May 30    

You all rights, and I know that this kind of job need more resources like (DBA &
SysAdmin). But, in my case I need to do all of this :))

Answer #20    Answered On: May 30    

Also, I recommend ISA Server for true load balancing. NLB has session management

Didn't find what you were looking for? Find more on SharePoint 2010 NLB Or get search suggestion and latest updates.