• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 365
  • Last Modified:

SBS 2008 Network redundancy

Hi,  I appreciate that this question has been raised a few times, and I have researched and got some answers to consider, but would love an expert opinion on the following:
I have 40 plus users in a SBS 2008 network. I have inherited this network and am trying to make it as efficient and resilient to disaster as possible.
The DC is SBS 2008 Standard with 8 GB RAM (not enough, I know) on an HP Proliant DL380 G5 server. They utilise Sharepoint and Exchange 2007. There are 3 other servers - two Win 2003 servers and a second Win 2008. The second Win 2008 hosts their major heavily used application – a SQL app that is also web based. One sbs 2003 is the terminal server and the other hosts other apps and Quickbooks.
They are V heavily reliant on email and network availability both on phones and pcs. I want to be sure that there is minimum downtime for them.  I also need to test backups – I have Shadow Protect and understand there is the virtual boot capability but am v nervous about testing anything on the SBS server as there is no backup server and downtime is a no - no!  The company is also growing and may get bigger than 75 users in a year or two.
What are my options here? Do I get a second server with SBS 2008 Premium on it and replicate the AD functions for network redundancy etc and have an online Exchange failover solution? Or do I get a second SBS 2008 server set up and configured exactly the same way as our current so I can test updates, backups etc and have it ‘ready to go”?
1 Solution
Lee W, MVPTechnology and Business Process AdvisorCommented:
You can only have ONE SBS server in a domain.  The SBS server must be the FSMO master - since you can only have one FSMO master, you can only have one SBS in a domain.

The more redundancy you have the more it will cost you.  

There are several ways of doing this.... you could turn the servers into VMs and cluster them (you still have single points of failure if the OS gets hacked, corrupted, or infected with a virus), you could install BDRs that can, in minutes, assume the identities of the server(s) that fail.  You could implement server mirroring with products like DoubleTake.  All these solutions have the potential to cost mid 4 figures OR MORE, depending on what you have and the skills you have to implement this in-house vs. hiring a consultant.
sbsgalAuthor Commented:
Understood. And yes, certainly expensive. Thank you for your feedback. I'll give this some more thought.

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now