SharePoint 2010 provides rich integration with SQL Server enabling SharePoint administrators to leverage the high availability solutions provided by Microsoft SQL Server. Changes include support for the Fail-over_Partner keyword, which enables SharePoint 2010 to natively interpret/translate and respond to state changes in a database mirroring topology. Following is brief of how to accomplish SQL Mirroring.

SQL Mirroring – The Native Way

Since SharePoint 2010 has built-in support for SQL mirroring so farm administrator can configure the SQL environment to mirror a SharePoint content database. When a new database is created, the SharePoint administrator will be prompted to enter the fail-over server. SharePoint then communicates with the witness server, and if issues are discovered, SharePoint will fail-over to the hot backup of the environment. Following image shows the configuration:

The post SharePoint 2010 – Ensure High Availability with SQL Mirroring appeared first on MachSol Blog.

Answer: Create host-named site collections using PowerShell

The management shell in SharePoint 2010 provides a comprehensive set of Windows PowerShell cmdlets that make development, implementation, and management of SharePoint 2010 easier and more effective. The SharePoint management shell replaces the Stsadm.exe management tool. All current and upcoming development of command-line resources and management information in Microsoft SharePoint Foundation 2010 should use this new scripting technology.

However, in order to create named site collection we can make use of the same SharePoint management shell. Following is the way to go:

Create host-named site collections using PowerShell:

Open up the SharePoint 2010 Management Shell and enter the following commands to create a new site collection for each of your desired vanity (Self-love) URLs. In this case I have created a site collection with the host name portal.machsol.com

New-SPSite http://portal.machsol.com -OwnerAlias DOMAIN\username -HostHeaderWebApplication http://web-app-url.com

The post SharePoint 2010 – Host-Named Site Collections Using Powershell appeared first on MachSol Blog.

Answer: Plan for virtualization (SharePoint Server 2010)​

SharePoint Server 2010 – Virtualized Farm Architecture for fully Redundant Farm with only Two Physical Nodes

•  – High Availability across Hosts
•  – All Components Virtualized
•  – Uses Only two Windows Enterprise Edition Licenses

As more companies try to decrease managing and investment expenses, fix the problems of datacenter solidity, and provide versatility to their SharePoint deployments – so in such circumstances virtualization becomes the pivotal point of conversation.  SharePoint 2010 provides more versatility in assistance of virtualization and similar to other hosting server technological innovation needs appropriate preparing to make sure those objectives are met.

A virtual platform is made up of two related levels, one actual and one virtual. A settings change in either level results hosts in the other level. This interrelationship becomes obvious when you plan to setup and use SharePoint Hosting server 2010 in a virtual platform. For more details you can contact us or read see virtualization overview.

All components of Microsoft SharePoint Server 2010 are fully reinforced when implemented in a Microsoft Windows Server 2008 R2 Hyper-V technology platform. Additionally, any relevant or required helping technologies are also support. Every factor of a SharePoint forest that is setup on a virtual machine should adhere to the licensing specifications for SharePoint Server 2010 as well as relevant and supported technologies.

The post SharePoint 2010 Redundant & Virtualized Farm appeared first on MachSol Blog.