Archives For SharePoint High availability


This white paper describes the design, deployment, and validation of a comprehensive midsize Microsoft SharePoint 2010 solution.   This solution is based on VMware vSphere 4.1 technologies for server virtualization and availability.   EMC CLARiiON CX4-130 is used as the storage platform for virtual machine data, content and remote BLOB storage (RBS).   Finally, EMC RecoverPoint, which is integrated with VMware vCenter Site Recovery Manager (SRM), ensures continuous availability of the Microsoft SharePoint 2010 farm.

Download Whitepaper: Protection for Virtualized SharePoint 2010 Farms

EMC Continuous Protection for Virtualized SharePoint 2010 Farms

Download Whitepaper: Protection for Virtualized SharePoint 2010 Farms


A Microsoft SharePoint Server 2010 Environment comprising of various servers which collectively hosts
the core applications and provide services, termed as SharePoint Farm is responsible for providing
various functions to its users. A three-tier architectural topology in which the SharePoint tiers (Web,
Application, and Database) are deployed using independent servers responsible for each tier is among
the most used SharePoint 2010 farm topology. To size each tier of a SharePoint farm demands detailed
study of the workload requirement and its usage patterns along with the performance capabilities of each
hardware component deployed in the system.

This paper illustrates performance of a medium SharePoint farm, built using Cisco UCS servers
implementing three tier architecture. A load generation framework to perform a load test was developed
by the SharePoint engineering team at Cisco, to measure the performance metrics while keeping the
much important response time less than 1 second. The paper shares the test results which provide
accurate guidance, better understanding of the performance impact of different SharePoint workloads,
assist our customers in sizing and designing the best farm architecture to support different workloads,
while recommending the best infrastructure elements for the optimal SharePoint implementation.

This study details information on how the recommended farm architecture could support 50000 users with
10% of total users concurrently working and show how to achieve sub second response time. Also,
highlights the performance benefits of new Cisco Servers used for this study.

Configuration of the SharePoint 2010 Farm

Read More: Microsoft SharePoint Server 2010 on Cisco Unified Computing System


Externalizing Large SharePoint 2010 with EMC VNX Series and Metalogix StoragePoint 

Externalizing Large SharePoint 2010 Objects with EMC VNX Series
A virtualized SharePoint environment reduces the cost by using the infrastructure effectively. Virtualization enables a reduction in the number
czech.emc.com/…/h8185-sharepoint-vnx-metalogix-psg.pdf


SharePoint 2010: SharePoint on the Internet and in the Intranet–Different Environments, Similar Needs

You can use SharePoint Server 2010 to create both Internet and intranet sites, but you need to be aware of the key differences and similarities between the two.

http://technet.microsoft.com/en-ca/magazine/gg457886.aspx


Downloadable and printable content (available in .doc, .pdf, or .xps file formats) that contains information about the capabilities of and requirements for SharePoint Server 2010.
Downloadable book: Getting started with SharePoint Server 2010

 


Limit Maximum value Limit type Notes
Application pools 10 per Web server Supported The maximum number is determined by hardware capabilities.

This limit is dependent largely upon:

  • The amount of RAM allocated to the Web servers
  • The workload that the farm is serving, that is, the user base and the usage characteristics (a single highly active application pools can reach 10 GB or more)

Limit Maximum value Limit type Notes
Content database 300 per Web application Supported With 300 content databases per Web application, end user operations such as opening the site or site collections are not affected. But administrative operations such as creating a new site collection will experience decrease in performance. We recommend that you use Windows PowerShell to manage the Web application when a large number of content databases are present, because the management interface becomes slow and difficult to navigate.
Zone 5 per Web application Boundary The number of zones defined for a farm is hard-coded to 5. Zones include Default, Intranet, Extranet, Internet, and custom.
Managed path

20 per Web application Supported Managed paths are cached on the Web server, and CPU resources are used to process incoming requests against the managed path list.

Exceeding 20 managed paths per Web application adds more load to the Web server for each request.

If you plan to exceed twenty managed paths in a given Web application, we recommend that you test for acceptable system performance.

Solution cache size 300 MB per Web application Threshold The solution cache allows the InfoPath Forms service to hold solutions in cache in order to speed up retrieval of the solutions. If the cache size is exceeded, solutions are retrieved from disk, which may slow down response times. You can configure the size of the solution cache by using the Windows PowerShell cmdlet Set-SPInfoPathFormsService.

Number Of Per SharePoint 2007 SharePoint 2010
Child Sites Site 2,000 5,000
Items List 5,000,000 50,000,000
Items View 2,000 5,000
Column Doc Lib 2,000 8,000
Column List 4,096 8,000
Indexed Docs Search Index 50,000,000 100,000,000

http://technet.microsoft.com/en-us/library/ff607936.aspx