Posts tagged High availability
Upcoming how-to guides
0Within two weeks I will post two how-to guides.
- How to setup a high availability SQL Server 2008 R2 cluster (HA clustering and mirroring).
- How to create a highly available SharePoint 2010 farm.
Requests for other how-to guides are always welcome.
DFS Operations Guide: Migrating from FRS to DFS Replication
0
Source: Microsoft Download
How to upgrade Windows Server 2008 systems that have the Hyper-V role installed to Windows Server 2008 R2
0
Microsoft has officially published documentation on upgrading Hyper-V clusters to Hyper-V R2.
Upcoming blog posts
0Currently I am working on several articles. These articles will be published within the next couple of weeks on this blog.
- Comparison of SQL Server 2008 High availability options (fail-over clustering, mirroring, log-shipping and replication)
- How to create a SQL Server 2008 2 node cluster on Windows Server 2008 R2 (using iSCSI and Windows Storage Server 2008)
- How to create a baseline of a new MOSS 2007 environment using Visual Studio 2008
- How to extend MOSS 2007 search capabilities using 3rd party software (Ontolica, BA-Insight and open source Faceted search)
Stay tuned.
Failover Clustering Performance Counters – Part 2
0Source: Microsoft Clustering and High Availability blog.
Hi Cluster Fans,
In Part 1 of this blog series we discussed Performance Counters and their interaction with the Network, Multicast Request Reply, Global Update Manager and Database clustering components. This post will look at monitoring some additional cluster components: the Checkpoint Manager, Resource Control Manager, Resource Types, APIs and Cluster Shared Volumes.
Checkpoint Manager
Checkpoint Manager is a component that helps you to make sure that data of the clustered application is available on all the nodes. Failover Cluster supports two kinds of checkpoints. Crypto Checkpoints allow you to keep your secret protected and available on all the nodes. The secret is used to create protected containers, generate keys in the containers, and encrypt data using the keys. If your application uses Crypto API and keeps secrets in the crypto container then you can associate a Crypto Checkpoint with your resource, providing it with information about the crypto provider and the container name. The cluster will export the keys from this container, export the container with data and will save all of this information to the cluster database. After offlining the resource on a node, the Checkpoint Manager will update the snapshot.
Failover Clustering Performance Counters – Part 1
0Source: Microsoft Clustering and High Availability blog
Hi Cluster Fans,
In Windows Server 2008 R2 we have added performance counters for Failover Clustering. Performance counters are like meters you have on some devices in your house. For instance, your electrical or water meter tracks what utilities you have consumed or your thermometer shows you the current temperature. They all have at least one thing in common – they show you aggregated information about the current state. However, they would not show you every event that contributes to that state. Some components in the cluster deal with lots of calls or traffic going through them and some buffer information in memory before it can get processed. We have added performance counters to several such components. This post will discuss each counter set and in future posts we will look at a couple of practical examples showing several issues resolved with the help of the performance counters.
SharePoint 2007 and High Availability
0
Today I decided to share some links about High Availability on SharePoint 2007.
Technet: Configure disaster recovery across SharePoint farms by using SQL Server log shipping
Technet: Configure availability in a single farm by using SQL Server clustering
Technet: Configure availability in a single farm by using SQL Server database mirroring
Using Database Mirroring with Office SharePoint Server and Windows SharePoint Services
MOSS 2007: Patching a mirrored farm with minimal downtime
0
Source: Microsoft SharePoint Team blog
For administrators of large SharePoint server farms, a newly-published article describes how to update server farms that use database mirroring, while incurring minimal perceived downtime for users. This solution is for enterprise customers who have high-availability needs and infrastructure. The article describes a step-by-step process for Office SharePoint Server farms that incorporate SQL Server mirroring. You can achieve similar results on Office SharePoint Server farms that are set up in a clustered server environment.
In brief, the solution requires that you:
· Disable mirroring and set the mirror databases to read-only
· Route network and database traffic to the read-only databases
· Apply software updates to the offline servers
· Route network and database traffic to the updated servers
· Apply software updates to the secondary farm
· Re-enable mirroring and set the mirrored databases to read/write
To read the full solution, see Configure a server farm for minimal downtime during software updates


