- Business logic
- application development
- Visual C#
- Visual Studio
- Microsoft Office
- Exchange server
- SharePoint 2010
- document management
- Web development
- Web sites
- Web Parts
- SharePoint Service Account
- SharePoint administration
SharePoint Protection: From High Availability to Disaster Recovery
If you have deployed SharePoint or are still in the planning phases, you probably have an ideal SharePoint scenario in mind, one where your intranet becomes useful again; your end users collaborate using team sites; and information is both organized and searchable. Now imagine your phone ringing at 2 A.M. with a voice on the other end saying, SharePoint is down. You rush to the office to discover that your SharePoint server has suffered a massive hardware failure. Your SharePoint dreams may have just turned into a massive nightmare. As you get this sinking feeling, youre asking yourself one question, Did we back up SharePoint?
Backups are a fundamental operational activity for any organization, and backing up SharePoint is no exception. Unfortunately, backup planning and implementation are often overlooked. This article explains how to protect your SharePoint environment and the data it contains. Even though you cant always prevent disasters from occurring, you can take steps to ensure your data is protected and can be restored if a disaster does occur. Before jumping into setting up and configuring backups, it's worth reviewing some SharePoint protection options.
High Availability Options
Your first impulse may be to consider the options for high availability. But before listing the technical aspects of these options, you should understand that high availability protects you only against service disruptions due to server or application failures. High availability does not protect you from data loss. For example, if you choose to implement high availability for your SharePoint farm, a server failure would have little if any impact on your end users, who could continue working uninterrupted. In other words, high availability options keep SharePoint online when a server fails, with little or no disruption in service. But you will still need to implement a method to protect the data.
Figure 1. High Availability SharePoint Farm: In this farm, two load-balanced front end web servers obtain data from two clustered servers (one active, one passive) that can both access shared storage.
After clustering your SQL Server, you will more than likely want to set up network load balancing between two or more web front-ends. After all, what good is a highly available database if the application on the front-end isnt online? You can use a hardware load balancer or the Microsoft Network Load Balancing Service (NLBS) to provide high availability and load balancing between multiple web front-ends as shown in the top box in Figure 1. The NLBS option balances traffic between the multiple front-end SharePoint servers during normal operations. When servers go offline, all traffic is diverted to the server(s) still online.
The top box in Figure 1 depicts two web front-end servers set up with network load balancing. This scenario balances all web traffic between the two front-end servers. If one server fails, traffic would continue to be routed through the still-active web server.
With high availability in place, you can turn your attention to putting a solid data backup plan in place.
A Developer.com eBook
Discover how to start developing for the Android platform with this extensive guide, which provides a reference to the Android platform as well as a look at developing your first Android application. You'll explore the top 10 features for developers as well as learn design and development tips that go beyond the phone and target tablet development as well.