E-business enterprises depend on their Web sites to generate revenue, satisfy customers, and optimize business processes. The enterprise Web site must respond quickly and be available 24/7 to service customers, business partners, and employees. The Web infrastructure has to be designed, maintained, and scaled to achieve this high availability. As companies become more dependent on their Web sites for communications and transactions, the need for a Web server infrastructure that can provide 100% percent uptime and grow to meet increased Web traffic demands becomes a business necessity.

Why Choose Frontpages for MOSS HA?

• 
  
  

  Clients

  Trusted by Fortune 500 companies and the most recognized brands in the world.
• 
  
  

  Expertise

  We have largest certified Microsoft SharePoint staff of engineers in the U.S.
• 
  
  

  Infrastructure

  As a tier 4 data center, we provide you with the highest ranking in reliability.

MOSS High Availability Plans

MOSS HA BASIC –  5 Server Farm
Normally, server redundancy is implemented at each layer to bring high availability in the overall system.  For the WFE layer, this can be achieved by using at least two front-end web servers load-balanced and for database layer; two clustered database servers can be used.

This server farm design introduces minimum high availability features into the system. Since this is an extension of the Two Server farm where the application roles are merged in the WFE roles, the system might not perform at its best but still, the availability requirements are being met using this architecture.

MOSS HA PRO – 8 Server Farm
To add the application layer to the overall design, at least one more server would be needed to represent the application layer. This will result in a design where high availability is induced at least in the Front End Servers. In addition, releasing the responsibility of Application Roles (Excel Services, Search etc.) from the front end layer results in improved application performance in terms of response time and user experience.
To add redundancy to the application layer itself in turn, we add one more server to the application layer that results in a 6 server farm. This, in my point of view, results in the best design that caters both availability and performance requirements.

It should be noted that not all application server roles can be redundant. There are limitations that restrict you from adding redundancy to some server roles. Although these application roles can be deployed to multiple servers for scalability, but they do not operate in a load-balanced manner and are not redundant. Such application roles are:

• WSS 3.0 Search Role (this is different from Office SharePoint Server Search which can be made redundant)
• Index Server Role (Typically not a deal breaker since Index Server propagates the indexed content periodically to the Search Servers.  As Index Server goes down, the Search Servers can still use their content indexes to provide search results.  Their content indexes won’t be updated until the Index Server comes back online.)

Frontpages addresses this native deficiency by using replication technology on the Index Servers to provide redundancy for this server role thus removing another single point of failure.
For a solution that has high availability and optimized performance requirements, 6 server farm is a design to start with but this 8 server architecture provides even better performance while increasing availability by clustering the Index Server. While designing a system using MOSS for a particular customer scenario, all the above-mentioned aspects should be considered to carve a good design which is long-lasting and meets the customer expectations.

MOSS HA PRO PLUS – 10 Server Farm
To add the application layer to the overall design, at least one more server would be needed to represent the application layer. This will result in a design where high availability is induced at least in the Front End Servers. In addition, releasing the responsibility of Application Roles (Excel Services, Search etc.) from the front end layer results in improved application performance in terms of response time and user experience.
To add redundancy to the application layer itself in turn, we add one more server to the application layer that results in a 6 server farm. This, in my point of view, results in the best design that caters both availability and performance requirements.

It should be noted that not all application server roles can be redundant. There are limitations that restrict you from adding redundancy to some server roles. Although these application roles can be deployed to multiple servers for scalability, but they do not operate in a load-balanced manner and are not redundant.
Such application roles are:

• WSS 3.0 Search Role (this is different from Office SharePoint Server Search which can be made redundant)
• Index Server Role (Typically not a deal breaker since Index Server propagates the indexed content periodically to the Search Servers.  As Index Server goes down, the Search Servers can still use their content indexes to provide search results.  Their content indexes won’t be updated until the Index Server comes back online.)

Frontpages addresses this native deficiency by using replication technology on the Index Servers to provide redundancy for this server role thus removing another single point of failure. We also add redundant, high performance fiber channel SANs serving as the SQL back ends for robust storage, performance and scalability.  Sharepoint data is replicated across the SANs for redundancy.

For a solution that has high availability and optimized performance requirements, 6 server farm is a design to start with but this 10 server architecture provides even better performance and capacity by adding the redundant fiber channel SANs. While designing a system using MOSS for a particular customer scenario, all the above-mentioned aspects should be considered to carve a good design which is long-lasting and meets the customer expectations.

MOSS GEO – 20 Server Farm, 2 Data Centers
To add the application layer to the overall design, at least one more server would be needed to represent the application layer. This will result in a design where high availability is induced at least in the Front End Servers. In addition, releasing the responsibility of Application Roles (Excel Services, Search etc.) from the front end layer results in improved application performance in terms of response time and user experience.

To add redundancy to the application layer itself in turn, we add one more server to the application layer that results in a 6 server farm. This, in my point of view, results in the best design that caters both availability and performance requirements.

It should be noted that not all application server roles can be redundant. There are limitations that restrict you from adding redundancy to some server roles. Although these application roles can be deployed to multiple servers for scalability, but they do not operate in a load-balanced manner and are not redundant.
Such application roles are:

• WSS 3.0 Search Role (this is different from Office SharePoint Server Search which can be made redundant)
• Index Server Role (Typically not a deal breaker since Index Server propagates the indexed content periodically to the Search Servers.  As Index Server goes down, the Search Servers can still use their content indexes to provide search results.  Their content indexes won’t be updated until the Index Server comes back online.)

Frontpages addresses this native deficiency by using replication technology on the Index Servers to provide redundancy for this server role thus removing another single point of failure. Redundant, high performance fiber channel SANs serving as the SQL back ends provide robust storage, performance and scalability.

This true disaster recovery architecture adds a 2nd data center with a high speed secure WAN connection replicating all Sharepoint data.  While adding the 2nd data center increases the cost and complexity of the solution, it is small investment, with a fast ROI, for a large enterprise with global operations using Sharepoint as a mission-critical foundation.
For a solution that has high availability and optimized performance requirements, 6 server farm is a design to start with but this 20 server, dual data center architecture provides maximum availability, performance, capacity and disaster recovery coverage. While designing a system using MOSS for a particular customer scenario, all the above-mentioned aspects should be considered to carve a good design which is long-lasting and meets the customer expectations.

• MOSS 2007 Hosting
• MOSS Dedicated
• MOSS High Availability
  • Pricing & Sign Up
  • Availability
  • Capacity
  • Disaster Recovery
  • How-to Web Farm