Designing a Microsoft SharePoint 2010 Infrastructure Vol 2 part 28 potx

MCT USE ONLY. STUDENT USE PROHIBITED Planning Business Continuity 14-25 Planning User-Controlled Business Continuity Features Key Points SharePoint Server 2010 includes several user-controlled capabilities and features that you can use for business continuity. You must carefully plan how you might use them in your environment. You should plan to use the Recycle Bin and versioning features of SharePoint Server 2010 in your environment to help users protect and recover their data. Recycle Bins and versioning are key components of a business continuity strategy. Protecting Content by Using Recycle Bins You can use Recycle Bins to retrieve deleted SharePoint Server 2010 objects such as files, documents, list items, lists, and document libraries. SharePoint Server 2010 supports two stages of recycle bins: the first-stage Recycle Bin and the second- stage Recycle Bin. You enable and configure the Recycle Bins at the Web application level. Note: You cannot use Recycle Bins to recover previous versions or accidental overwrites of documents. You must use versioning to enable this functionality. MCT USE ONLY. STUDENT USE PROHIBITED 14-26 Designing a Microsoft® SharePoint® 2010 Infrastructure The following table describes how an item is deleted and recovered from the first- stage Recycle Bin and the second-stage Recycle Bin. Action Item state Item restored by User deletes item Item is held in the first-stage Recycle Bin until the item is deleted from the Recycle Bin or the item has been in the Recycle Bin for longer than the time limit configured for an item to be held in the Recycle Bin User or site collection administrator User deletes item from the Recycle Bin Item is held in the second-stage Recycle Bin Site collection administrator Caution: Turning off the Recycle Bin for a Web application empties all Recycle Bins and permanently deletes all items in them. First-Stage Recycle Bin The first-stage Recycle Bin is located at the site level and is available to users who have Contribute, Design, or Full Control permissions on a site. The first-stage Recycle Bin process works as follows: • When a user deletes an item from a Web site, the item goes to the site's first- stage Recycle Bin: • Items in the first-stage Recycle Bin count toward the site quota. • Items remain in the site’s first-stage Recycle Bin until a specified time period elapses. By default, this time period is 30 days. The time limit for the Recycle Bin applies to the total time after the item was first deleted, not the time spent in the Recycle Bin. • When a user deletes an item from the Recycle Bin, the item goes to the second- stage Recycle Bin. Second-Stage (Site Collection) Recycle Bin The second-stage Recycle Bin is located at the site collection administrator level, and is organized into two views: MCT USE ONLY. STUDENT USE PROHIBITED Planning Business Continuity 14-27 • Objects in the first-stage Recycle Bins of all sites in the site collection. • Objects in the second-stage Recycle Bin. The second-stage Recycle Bin process works as follows: • When a user deletes an item from the first-stage Recycle Bin, it goes to the second-stage Recycle Bin. • When an item goes to the second-stage Recycle Bin, only a site collection administrator can recover it. • Items remain in the second-stage Recycle Bin until either a specified time period elapses (by default, this is 30 days) or until the second-stage Recycle Bin reaches its size limit (set as a percentage of the size quota), at which time the oldest items are deleted. Protecting Content by Using Versioning You can use versioning to help prevent data loss that is caused by someone overwriting a document. When a site owner turns on versioning in a document library or a list, the library or list keeps multiple copies of a document, item, or file. In the event of an unwanted change, an overwritten file, or document corruption, the user can easily restore the previous version. You can enable versioning at the library or list level, and you can version both items and files. You must closely manage your versioning implementation. If sites have too many versions of files and documents, the sites can become quite large. If you do not limit the size of sites, your sites can exceed your storage capacity. Farm administrators can manage this issue by establishing SLAs with site owners and by setting size quotas on sites. Additional Reading For more information about how to use the Recycle Bin in SharePoint Server 2010, see http://go.microsoft.com/fwlink/?LinkId=90917&clcid=0x409. For more information about how to configure Recycle Bin settings, see http://go.microsoft.com/fwlink/?LinkID=201260&clcid=0x409. For more information about how to manage site collection storage limits, see http://go.microsoft.com/fwlink/?LinkID=202092&clcid=0x409. MCT USE ONLY. STUDENT USE PROHIBITED 14-28 Designing a Microsoft® SharePoint® 2010 Infrastructure Planning for Disaster Recovery in SharePoint Server 2010 Key Points You must make several key decisions when you plan your disaster recovery strategy for an implementation of SharePoint Server 2010. Evaluating Costs As you plan your disaster recovery requirements, you must be aware that disaster recovery can be one of the more expensive requirements for a system. The shorter the interval between failure and availability and the more systems that you decide to protect, the more complex and expensive your disaster recovery solution is liable to be. When you plan your investment in a disaster recovery solution, you must consider the following costs: • Additional hardware and software, which often increase the complexity of operations between software applications, such as custom scripts for failover and recovery. • Additional operational complexity. MCT USE ONLY. STUDENT USE PROHIBITED Planning Business Continuity 14-29 You should evaluate the costs of maintaining hot or warm standby data centers in conjunction with your business needs. Do all of your services require the same level of recoverability after a disaster? You should offer different degrees of disaster recovery for different content, sites, services, or farms. For example, content that has a high impact on your business or an Internet publishing farm might need a greater degree of recoverability than other content. Tip: When you implement failover between server farms, it is recommended that you first deploy and tune the core solution within a farm, and then implement and test the disaster recovery strategy. Identifying System Requirements for Disaster Recovery In an ideal scenario, your failover components and systems would match the primary components and systems in all areas: platform, hardware, and number of servers. At a minimum, your failover environment must be able to cope with the extra traffic that you would expect during a failover operation. You should keep in mind that the failover system may only serve a subset of users. Whatever your scenario, the systems must match in at least the following areas: • Operating system versions and updates. • SQL Server versions and updates. • SharePoint Server 2010 product versions and updates. Although we are principally discussing the availability of SharePoint Server 2010, other components can affect the system uptime, so you should also: • Ensure that infrastructure dependencies such as power, cooling, network, directory, and Simple Mail Transfer Protocol (SMTP) are fully redundant. • Choose a switching mechanism such as Domain Name System (DNS) or hardware load balancing that meets the needs of your organization and environment. MCT USE ONLY. STUDENT USE PROHIBITED 14-30 Designing a Microsoft® SharePoint® 2010 Infrastructure Choosing a Disaster Recovery Strategy You can choose from several approaches to provide disaster recovery for your SharePoint Server 2010 environment, depending on your business needs. The following table lists example scenarios that show reasons for choosing cold, warm, or hot standby disaster recovery strategies. Strategy Example scenario Pros Cons Cold standby A business ships backups to support computer system recovery to local and regional offsite storage on a regular basis. The business has contracts in place for emergency server rentals in another region. Often the cheapest option to maintain, operationally. Often an expensive option to recover, because it requires you to configure physical servers correctly after a disaster has occurred. Usually the slowest option to recover. Warm standby A business ships virtual server images to local and regional disaster recovery farms. Often relatively inexpensive to recover because a virtual server farm can require little configuration upon recovery. Can be very expensive and time-consuming to maintain. Hot standby A business runs multiple data centers, but serves content and services through only one data center. Often relatively fast to recover. Can be quite expensive to configure and maintain. MCT USE ONLY. STUDENT USE PROHIBITED Planning Business Continuity 14-31 Using Log Shipping for Disaster Recovery in SharePoint Server 2010 Key Points The most common solution for providing disaster recovery for SharePoint Server 2010 is to use SQL Server log shipping. You can use SQL Server log shipping to create a disaster recovery farm in a geographically distributed data center for SharePoint Server 2010. Using this configuration, you can provide a disaster recovery site that provides services when a failover occurs. Overview of SQL Server Log Shipping Log shipping enables you to configure SQL Server to continually send transaction log backups from a primary database on a primary server instance to one or more secondary databases on separate secondary server instances. You then apply the transaction log backups to each secondary database individually. Continually backing up the transaction logs from a primary database and then copying and restoring them to a secondary database keeps the secondary database almost synchronized with the primary database. Log shipping can also include an optional third server instance, which is known as the monitor server. This server records the MCT USE ONLY. STUDENT USE PROHIBITED 14-32 Designing a Microsoft® SharePoint® 2010 Infrastructure history and status of backup and restore operations and raises alerts if these operations do not occur as scheduled. Log shipping consists of three operations: 1. Back up the transaction log on the primary server instance. 2. Copy the transaction log file to the secondary server instance. 3. Restore the transaction log backup on the secondary server instance. The image on the slide for this topic illustrates the log shipping process. SharePoint Server 2010 and Log Shipping You can use SQL Server log shipping to send content databases, including My Sites databases, from one SharePoint Server 2010 farm to one or more geographically dispersed secondary farms. Considerations for Using Log Shipping for SharePoint Server 2010 You must consider several things when you plan to use log shipping for SharePoint Server 2010 disaster recovery: • By default, the failover process for log shipping is manual. You can create scripts to automate failover. • The minimum time that you can configure for synchronization is one minute. • When failover happens, you must run a SQL Server script to make all of the content databases writeable. • You cannot use log shipping to send the configuration database to another farm because it contains computer-specific information. You must maintain the same customizations and configuration settings on both farms manually. • In the event of an unplanned failover, some data loss is possible, depending on the frequency of log shipping and the time of failure. • Site collections that are added to the primary farm are not automatically added to the configuration database on the secondary farm. You must add them by using either Stsadm operations or a script. MCT USE ONLY. STUDENT USE PROHIBITED Planning Business Continuity 14-33 Discussion: High-Level Business Continuity Planning Key Points Answer the following questions in the context of the sample business continuity plan. Question: What effects does implementing versioning have on your design? Question: What areas of your design are impacted by requirements for business continuity? MCT USE ONLY. STUDENT USE PROHIBITED 14-34 Designing a Microsoft® SharePoint® 2010 Infrastructure Lesson 3 Creating a Backup and Restore Plan for SharePoint Server 2010 There are several strategies, tools, and scenarios to consider when you create a successful backup and restore plan for SharePoint Server 2010. This lesson describes the key tools and strategies for backing up and restoring your SharePoint Server 2010 environment. Objectives After completing this lesson, you will be able to: • Determine what to protect in your SharePoint Server 2010 environment. • Plan the backup and restore of SharePoint Server 2010. • Identify backup and restore strategies for SharePoint Server 2010. . up the transaction logs from a primary database and then copying and restoring them to a secondary database keeps the secondary database almost synchronized with the primary database. Log shipping. PROHIBITED 14-34 Designing a Microsoft SharePoint 20 10 Infrastructure Lesson 3 Creating a Backup and Restore Plan for SharePoint Server 20 10 There are several strategies, tools, and scenarios to. PROHIBITED 14 -28 Designing a Microsoft SharePoint 20 10 Infrastructure Planning for Disaster Recovery in SharePoint Server 20 10 Key Points You must make several key decisions when you plan your disaster