We help IT Professionals succeed at work.

How to split a single server installation accross two servers

154 Views
Last Modified: 2010-03-19
I have Sharepoint 2007 test server which I have been forced due to time constraints to go live with, the problem is that at present the entire installation (Sharepoint 2007, SQL 2005 and IIS are sitting on one machine) I have a second server available which I would like to mirror the configuration of my first server (so that in case of hardware failure either server can support the entire enviroment) but ideally I would like one of the machines to be running IIS and the second to be running SQL 2005 to give me better performance aswell some contingency in case of a disaster.
Please can anybody advise the best way to go about this with as little impact on the live system as possible, or provide any links to some usefull documents?
Comment
Watch Question

Ted BouskillSenior Software Developer
CERTIFIED EXPERT
Top Expert 2009

Commented:
I actually designed and managed a 7 server Sharepoint 2007 web farm so I think I can help! :)  Our farm has a two node Active/Active SQL cluster and uses network load balancing on the web and application servers so everything has a hot standby except the indexing server (the 7th) because Microsoft doesn't support load balancing the indexing services.

I'm going to assume you followed some best practices and did NOT use the computer name for the Sharepoint site and instead used a fully qualified DNS name for the sharepoint site.  If you didn't that will cause trouble!

The easiest way would be to do a complete installation of Sharepoint on the new server.  Then, using the configuration wizard join it to the web farm.  You could then redirect traffic to that server by changing the DNS entry for the fully qualified website name I mentioned earlier and then disconnect Sharepoint on the SQL server and uninstall it.

Adding new Sharepoint servers is very easy after that, however, adding a SQL cluster later would be very difficult.  In fact, moving SQL databases in Sharepoint is possible but very risky and only for very advanced SQL/Networking/Sharepoint Administrators.

By the way, splitting onto two servers will gave you greated performance but wil NOT provide contigency in case of disaster.  If either server fails, your farm is down.  The minimum number of servers for full contingency is 4.

A great resource for all things Sharepoint is http://blogs.msdn.com/Sharepoint which is run by the Sharepoint Product team.

Author

Commented:
My understanding was that whilst not being the fully contingent model, 2 servers would suffice by just shutting down serivce not being used on each machine  (SQL or IIS) and then starting up the service in case of emergency. I assume the:
sp_dropserver 'old_name'
go
sp_addserver 'new_name', 'local'
go
command will solve the issue of moving the SQL databases to a different server, so then it just a case of having IIS mirrored on both machines, but only turned on on one.
I ran the Sharepoint configuration on the second machine and pointed it at the sharepoint_config database on my original machine, however this just points everything on my second machine at the existing machine how can I seperate them?
Senior Software Developer
CERTIFIED EXPERT
Top Expert 2009
Commented:
Unlock this solution and get a sample of our free trial.
(No credit card required)
UNLOCK SOLUTION
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a sample view!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.