Getting Started with Idera SharePoint backup

Transcription

1 Getting Started with Idera SharePoint backup

2

3 Legal Notice Idera, Inc., DTx, IntelliCompress, Point admin toolset, Pointbackup, Pointcheck, PowerShellPlus, SharePoint enterprise manager, SharePoint security manager, SharePoint diagnostic manager, SharePoint backup, SharePoint performance monitor, SQLcheck, SQL change manager, SQLconfig, SQL comparison toolset, SQL compliance manager, SQLcompliance, SQLcm, SQL defrag manager, SQL diagnostic manager, SQLdm, SQL mobile manager, SQLpermissions, SQLsafe, SQLsafe Freeware Edition, SQLsafe Lite, SQLscaler, SQLschedule, SQL schema manager, SQLsecure, SQLsmarts, SQLstats, SQLtool, SQL toolbox, SQL virtual database, SQLvdb, virtual database, Idera, BBS Technologies and the Idera logo are trademarks or registered trademarks of Idera, Inc., or its subsidiaries in the United States and other jurisdictions. All other company and product names may be trademarks or registered trademarks of their respective companies Idera, Inc., all rights reserved. THIS DOCUMENT AND THE SOFTWARE DESCRIBED IN THIS DOCUMENT ARE FUR- NISHED UNDER AND ARE SUBJECT TO THE TERMS OF A LICENSE AGREEMENT. EXCEPT AS EXPRESSLY SET FORTH IN SUCH LICENSE AGREEMENT, IDERA, INC., PRO- VIDES THIS DOCUMENT AND THE SOFTWARE DESCRIBED IN THIS DOCUMENT "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. SOME STATES DO NOT ALLOW DISCLAIMERS OF EXPRESS OR IMPLIED WARRANTIES IN CERTAIN TRANSACTIONS; THEREFORE, THIS STATE- MENT MAY NOT APPLY TO YOU. YOU ARE ENCOURAGED TO READ THE LICENSE AGREEMENT BEFORE INSTALLING OR USING THIS DOCUMENTATION OR SOFTWARE. Some companies, names, and data in this document are used for illustration purposes and may not represent real companies, individuals, or data. This document could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein. These changes may be incorporated in new editions of this document. Idera, Inc., may make improvements in or changes to the software described in this document at any time Idera, Inc., all rights reserved. U.S. Government Restricted Rights: The software and the documentation are commercial computer software and documentation developed at private expense. Use, duplication, or disclosure by the Government is subject to the terms of the Idera, Inc., standard commercial license for the software, and where applicable, the restrictions set forth in the Rights in Technical Data and Computer Software clauses and any successor rules or regulations.

4 Contents Legal Notice 3 Contents 4 Welcome to Idera SharePoint backup 7 What is Idera SharePoint backup? 7 How does Idera SharePoint backup help me? 7 Using Idera SharePoint backup in your disaster recovery plans 8 Restoring and rebuilding from a Farm Backup 13 Find answers using this documentation 16 Using this Documentation 16 Contacting Idera 16 Using the Help 16 Understanding the document conventions 16 About Idera 17 Idera Products Release Notes 18 New features new features new features new features new features 19 Fixed issues Fixed issues Fixed issues Fixed issues Fixed issues 20 Tips 20 Known Issues 24 Granular backup and restore limitations 24 Recommended Idera Solutions 26

5 Learning about the components and architecture 28 Learning about the components 28 Learning about data grooming 31 Learning about communications and security 32 Learning about Tivoli Storage Manager 32 Learning about the requirements 34 Learning about the SharePoint requirements 34 Learning about the Management Console requirements 34 Learning about the Management Service requirements 35 Learning about the Backup Service requirements 35 Learning about the Self-Service Recovery feature requirements 37 Learning about the Management Service permission requirements 37 Installing and deploying Idera SharePoint backup 40 Installing Idera SharePoint backup 40 Installing on a standalone SharePoint server 41 Installing the Backup Service manually 43 Upgrading Idera SharePoint backup 45 Upgrading to Idera SharePoint backup 45 Configuring Idera SharePoint backup 50 Opening the Idera SharePoint backup Management Console 50 Connecting a standalone Management Console to the Management Service 51 Configuring Idera SharePoint backup for your farm 52 Specifying the Central Administration settings 52 Selecting the WFE servers where you want to install the Backup Service 53 Selecting the database servers where you want to install the Backup Service 54 Installing the Self-Service Recovery feature 55 Configuring the SharePoint backup licenses 57 Specifying the Backup Service preferences for a new farm 57 Configuring the alert settings 61 Configuring the alert notification settings 61 Configuring the grooming settings 61

6 Configuring the fault tolerance settings 61 Managing licenses 62 Adding new license keys 63 Managing the Backup Service 64 Starting the Backup Service 64 Stopping the Backup Service 64 Managing farms 65 Monitoring multiple farms 65 Adding a farm 66 Editing a farm 67 Removing a farm 67 Configuring fault tolerance 68 Managing self-service recovery 69 Manually installing the Self-Service Recovery feature 69 Configuring the Self-Service Recovery settings 70 Delegating permission for Self-Service Recovery 72 Specifying Idera SharePoint backup preferences 73 Defining the Backup Service preferences 73 Defining the Management Service preferences 76 Defining the Management Console preferences 78 Configuring the Backup Service settings for Multiple Farms 78 Understanding load balancing 80 Managing alerts 80 Learning about alerts 81 Viewing alerts in the Management Console 83 Configuring the alert settings 84 Managing the alert notification settings 85 Configuring alert grooming 87 Managing Backup Set disk space 87 Archiving Backup Sets 88 Importing Backup Sets 88

7 Index 90 Welcome to Idera SharePoint backup Idera SharePoint backup provides full-farm backup and restore protection for Microsoft SharePoint environments. It provides administrators with a complete set of tools to schedule and manage backups, monitor operations, broadcast notifications, and empower their users with self-service granular restore capabilities. SP backup includes the following: Full farm protection. Granular backup and restore. Enterprise management of backup and restore. What is Idera SharePoint backup? Idera SharePoint backup is a powerful solution that automates your SharePoint backup protection and provides flexible SharePoint restore and recovery. SP backup features an intuitive Management Console and delivers a robust, efficient backup and restore solution that you can install in minutes. SP backup provides comprehensive SharePoint backup and restore services through the following critical features: Automated backup of SharePoint 2010 farm components. Automated backup of site collections and Web sites. Reduced time and size of backups using differentials to capture only those objects that changed since your last full backup. Powerful IntelliSearch for finding the backed up content you need. Self-service SharePoint recovery through an intuitive Self-Service Recovery feature. Detailed restore capabilities and options for the specific objects you need. Comprehensive reporting and operation monitoring provided within the Management Console. Easy installation and use. How does Idera SharePoint backup help me? Microsoft SharePoint helps you to improve the efficiency of your organization through comprehensive content collaboration and management. You need to protect your SharePoint content with a reliable and flexible backup and recovery solution. Idera SharePoint backup provides the powerful solution that you need. SP backup helps you to back up your SharePoint content on a regular basis. You can back up frequently changing content more often to provide additional protection. Finding and recovering lost content can be time consuming. SP backup solves these issues by providing a proactive solution that safely backs up your content and provides an intuitive Management Console to help you quickly locate and restore the backed up content you need. The Self-Service Recovery feature provides the flexible restore solution you need to avoid delays and reduce your SharePoint admin-

8 istration costs. For SharePoint 2010 farms, SP backup lets you backup and restore the components that make up your farm. SP backup incorporates proven SharePoint experience and knowledge in a comprehensive, automated, and effective solution. With SP backup, you can do the following: Automate the SharePoint backup process to protect changing content. Reduce storage requirements for backed up SharePoint objects. Quickly locate and recover backed up SharePoint objects. Deliver self-service SharePoint content recovery to save time. Eliminate training needs with the intuitive Management Console, Self-Service Recovery feature, and wizards. Monitor and review backup and restore operations. Using Idera SharePoint backup in your disaster recovery plans Your plans for recovering from problems with your Microsoft SharePoint farm are a vital part of your SharePoint strategy. Idera SharePoint backup can be an important part of those plans. What is a disaster recovery plan? A disaster recovery plan is your expectation of and preparation for problems with your SharePoint deployment. A disaster recovery plan is not as simple as backing up and restoring the servers that make up your SharePoint farm. Disaster recovery is a business problem, not a technical one. Your disaster recovery plan must balance the business needs of your enterprise with the technical and financial costs required to implement the plan. Your disaster recovery plan must answer many questions, including the following: How long will it take? What can I afford to lose? What will it cost? How will I protect my SharePoint farms from disaster? This means that backup and recovery is part of how you design and implement your disaster recovery plan. Backup and recovery are technical, process answers to a business question. These technical questions and their answers are important, but they are not the whole story. In fact, not all disaster recovery involves backup and restore. Some plans for disaster recovery can omit backup and restore capabilities entirely. How are disaster recovery strategies designed, and how do they evolve over time? Your SharePoint disaster recovery plan is a part of, and grows from, your larger business continuity plan. You create your business continuity plan based on a business impact analysis. The business impact analysis is in turn based on a risk analysis of your business operations. Your business continuity plan and the SharePoint disaster recovery plan must prioritize your plans and the resources allotted to them. You can prioritize the plans based on the financial impact of executing the plan. You should also consider what happens if you do not implement the plan. What disaster recovery specific issues should I consider? When you create your disaster recovery plan, there are some unique issues that you should

9 consider, including the following: Term Definition Comments Recovery Point Objective (RPO) Recovery Time Objective (RTO) Disaster Recovery(DR) targets The RPO is the point in time that is your target when you recover from a disaster. The RPO is measured in time before the present. The RTO is the goal amount of time to recover from a disaster. It is measured in time from the present. The DR targets are the items in your SharePoint deployment that you protect from loss or failure. When you specify the RPO, you answer the question "How much data am I willing to lose?" When you specify the RTO, you answer the question "How long do I have to restore an agreed-upon level of functionality? You can specify coarse or granular targets. You can mix levels of granularity, depending on the target. Thus, you may need to protect an entire SharePoint farm in one deployment. In another, you may need to protect only a site collection, a Web Application, a single site, or specified data. The DR plan must set priorities for the targets that it includes. Not all targets have equal importance to the farm or to users. How does Idera SharePoint backup fit into a Disaster Recovery strategy? SP backup helps you to execute your disaster recovery strategy. Before a disaster happens, you can use SP backup to back up the elements that make up your SharePoint farm. Depending on the version of SharePoint that you use, you can back up the farm components or the SharePoint objects themselves. SP backup requires a functioning SharePoint farm for both backup operations and restore operations. As such, it is not suitable for all parts of your DR strategy. SP backup is not a High Availability (HA) solution. It is also not intended for the portions of your DR plans that require low RTO or low RPO windows that measure in minutes rather than hours. Which SharePoint Farm Components can you use SP backup to back up and restore? SP backup can back up many of the components that make up your SharePoint farm. You can also restore these components when needed. The components that SP backup can back up and restore include the following: SharePoint Configuration Database SharePoint Content Databases Search components

10 Search databases Service applications.net Framework Configuration Certificate Store Internet Information Services (IIS) Configuration IIS Metabase SharePoint Registry entries SharePoint Root SharePoint Web Application Roots SP backup does not backup certain other components, including the following: Microsoft FAST Search Server for SharePoint Microsoft Project Server 2010 What factors affect SP backup performance? The following factors can affect the performance of your SP backup deployment and thus can affect the RPO and RTO: Performance of the SQL Server that hosts the Share- Point databases. Backup location file performance. Network performance. Individual farm server performance. Backup of SharePoint objects (granular backup) utilizes the SQL Server heavily because SP backup uses the SharePoint object model. Poorly-performing or oversubscribed SQL Servers virtually assure that you will experience poor backup and restore performance when you perform granular operations. All content is backed up to a UNC path or a Tivoli Storage Manager (TSM) Virtual Storage Node that you specify when you create a backup job. SP backup performs extensive multi-stream, concurrent read and write activity. When you perform a Farm Backup, each farm member and each SQL Server can initiate read/write activity separately. In a multi-server SharePoint farm, the performance of the backup location host can be a significant bottleneck. As SP backup performs Granular Backups and Farm Backups, it can transfer multiple gigabytes of data across your network to and from the backup location. A saturated network can slow SP backup performance dramatically. SP backup relies on the Backup Service hosts and the farm servers to collect data. Performance impediments on the servers impact the performance of SP backup. When you compress or encrypt backups, you increase the workload of the Backup Service hosts. With modern, multi-core x64 systems, hardware performance is a relatively smaller issue.

11 How do Granular Backups fit into my Disaster Recovery plan? You can perform Granular Backups for all SharePoint 2007 and SharePoint 2010 farms. Granular Backups help you to back up the following types of SharePoint content: Site Collections Sites Lists Libraries Items Granular Backups use the SharePoint object model to perform operations. This lets you rely on SharePoint security for items. On the other hand, using the object model causes performance penalties when moving very large amounts of data from or to a SharePoint farm. Granular Backup is a best fit in the following cases: Use Restore data lost through accidental deletion, end-user error, or unintended system action including automated deletion by Site Use Confirmation and Deletion. Restore data following a large-scale data loss. Cross-platform or cross-version recovery of Share- Point data. For example, moving between SharePoint 2007 and SharePoint Comments Restore is initiated by the backup administrator or a Site Collection administrator. RPOs are driven by the backup schedule. RTOs are driven by the speed of the restore through the object model. Completely restore one or more Site Collections to a new content database. Restore is initiated by the backup administrator. RPO is driven by the backup schedule. Large amounts of data are slow to restore through the SharePoint Object Model. Restore is initiated by the backup administrator. This is a special case, and it provides flexibility as you transition versions. Tip: SP backup is not designed to migrate your SharePoint farm to a new Share- Point version. You can use SP backup to move data between SharePoint farms or from one SharePoint farm to another.

12 Granular Backups are a poor fit in the following cases: Use Backup of the entire Share- Point Farm or the Farm Components. Fast recovery, with a short RTO. High availability. Comments Only the SharePoint content is backed up. Configuration or farm-level data is not included in backups. Granular Backups have a low RTO for limited amounts of data. For large-scale restoration, the RTO is high. SP backup is not a high availability (HA) solution and is not suitable for a low RPO/low RTO disaster strategy. How do Farm Backups fit into my Disaster Recovery plan? You can perform Farm Backups for SharePoint 2010 farms only. Farm Backups help you to back up the following SharePoint items: Content Databases Service Applications Farm Configuration information Search components Farm Backups use the Microsoft Volume Shadow Copy Service (VSS) to back up the components as your farm works. Because it does not rely on the SharePoint object model, Farm Backup is an order of magnitude faster than a similar Granular Backup. Farm Backup is a best fit in the following cases: Use Back up the entire SharePoint farm. Large scale backup of SharePoint Content databases Comments RPO is driven by the backup schedule. RPOs and RTOs are significantly shorter than that of a similar-scale Granular Backup. Configuration data is included in the backup, but you use that data to perform a manual rebuild of the SharePoint environment. RPO is driven by the backup schedule. Lets you quickly restore Content databases in place to recover lost or corrupt data. Farm Backups are a poor fit in the following cases:

13 Use "Bare metal" restore scenarios. Very high speed restore with a very low RTO. Comments SP backup helps you to back up critical farm components, but you must have a functioning SharePoint 2010 farm to restore to. SP backup does not protect the underlying operating system, the SQL Server, or any dependent systems. Recovery speeds are limited by the ability to move backed up data over the network from the backup location. In addition, optional decryption and decompression can add time to the process. SP backup is not a high availability (HA) solution. Restoring and rebuilding from a Farm Backup When disaster strikes, Idera SharePoint backup can help you to restore your SharePoint 2010 farm to operation. When you use SP backup to restore, you must first have a functional, minimally-configured SharePoint 2010 farm. The restore procedures vary based on your specific environment. What online guidance exists for restoring a farm? The following articles may help you to develop your procedures when you restore: Restore a Web application. Configuration-only restore. Restore a service application. Provision search. How do I restore portable configuration settings in a configuration-only restore? When you perform a configuration-only restore, you can restore the following settings: Antivirus configuration. Information rights management (IRM) configuration. Outbound settings (only when you perform an "overwrite").

14 Customizations deployed as trusted solutions. Diagnostic logging configuration. When you perform a configuration-only restore, you should use the following as a general guide to the steps that you should perform: Attach the source farm configuration database to a SQL Server deployment. Perform a configuration-only backup on the new farm with the Backup-SPConfigurationDatabase cmdlet. When you perform the backup, you specify the SQL Server where the source farm configuration DB is located. Perform a configuration-only restore with the Restore-SPFarm cmdlet using the backup that you created. How do I restore the.net Framework Configuration and the IIS Configuration? You can restore the.net Framework Configuration files and the Internet Information Service (IIS) Configuration files out of place. When you perform the restore, you can use the restored files as a guide to configure your settings in the.net Framework and in the IIS settings. It is not possible to safely replace these configuration files on your computer. How do I restore the SharePoint Registry? You can restore the SharePoint Registry out of place. When you perform the restore, you can use the restored files as a guide to configure your SharePoint registry settings in the registry editor. It is not possible to safely replace registry on your computer. How do I restore the Certificate Store? You can restore the Windows Certificate Store out of place to a location that you specify. You can use the Windows Certificate Manager to import the Certificate file. How do I restore a Web Application and its content? You can use the following as a general guide to the steps that you should perform to restore a Web application and its content: Attach the restored content databases to the desired SQL Server instance or instances. Use the Configuration Browser in the SP backup Management Console to view the configuration settings in the backup set, and then use the settings as a guide to create the Web Applications in the SharePoint Central Administration. Use the Manage Content Database Settings tool in the SharePoint Central Administration to remove the default database that was created. Use the Add a content database tool in the SharePoint Central Administration page to attach the restored content databases. You can also use the Mount-SPContentDatabase cmdlet to attach the databases. You must attach each content database separately. How do I restore a service application? Every service application is unique. In a very general way, when you restore a service application, you do the following: Attach any associated service application databases to the desired SQL Server instance or instances.

15 Use the Central Administration page to create a new service application. You can use the Configuration Browser in the SP backup Management Console to view the configuration settings in the backup set, and then use the settings as a guide to create the new service application. Use the existing (re-attached) databases as the database names to use when prompted for the databases to use. How do I restore search? Your search settings are unique, and so is the procedure that you use to restore search databases. You can restore search facilities out of place or in place. When you perform an in-place restore, can restore the search components as part of a larger restore of the entire farm. You include the search components when you select the farm components to restore in the SP backup Management Console. You restore the farm components to a new SharePoint farm, replacing the existing components. In general, you can use the following guidelines when you restore search out of place: Provision the search service on the new SharePoint farm. You can use the Configuration Browser in the SP backup Management Console to view the configuration settings in the backup set, and then use the settings as a guide for the new search settings. When the search service is built, do the following: Stop the time service and the search service. The SharePoint Foundation Search service is named SharePoint Foundation Search v4. The SharePoint Office Search Service is named SharePoint Server Search 14. The SharePoint 2010 Timer service is named SharePoint 2010 Timer. Delete the search service application databases. Restore the prior search databases and their index files out-of-place. Reattach the restored database files to the desired SQL Server instance or instances. Delete the existing index files. Copy the restored index files to the Index Server. Make sure to copy the contents of the restored search, crawl, and query folders to the Index Server. You do not restore the folders themselves because the GUID for the new folders does not match the GUID for the restored folders. Restart the search service and the time service. Perform an incremental crawl of the site. How do I restore the Global Assembly Cache, the SharePoint Root, or the SharePoint Web Application Roots? Normally, SharePoint itself manages the contents of the Global Assembly Cache, the SharePoint Root, and the Web Application Roots when you deploy and retract solutions within SharePoint. If you performed decentralized customizations of your SharePoint environment, you may need to perform additional steps to restore those customizations. A decentralized customization requires you to install files into these locations manually. Every decentralized customization is unique, and they may require you to perform additional steps to enable them. When you restore the Global Assembly Cache, the SharePoint Root, or the Web Application Roots, SP backup restores the contents the backup to a directory that you specify. You can then

16 use the original setup instructions for your decentralized customization to perform the customization again, using the files that SP backup restored. Find answers using this documentation This documentation set includes a comprehensive online Help system as well as additional resources that support you as you install and use the product. You can also search Idera Solutions, available at the Idera customer service portal ( Using this Documentation This documentation set includes a comprehensive online Help system as well as additional resources that support you as you install and use the product. You can also search Idera Solutions, available at the Idera customer service portal ( Contacting Idera Please contact us with your questions and comments. We look forward to hearing from you. For support around the world, please contact us or your local partner. For a complete list of our partners, please see our Web site ( Sales GO.IDERA ( ) (only in the United States and Canada) Sales sales@idera.com Support GO.IDERA ( ) (only in the United States and Canada) Web site Using the Help This Help system can be accessed either through the Start menu, through the Help menu on the Management Console, or by pressing F1 on your keyboard while on the window for which you would like more information. TIP: The online Help requires Internet Explorer version 7.0 or later. Understanding the document conventions Idera documentation uses consistent conventions to help you identify items throughout the printed online library.

17 Convention Bold Italics Fixed Font Straight brackets, as in [value] Curly braces, as in {value} Logical OR, as in value 1 value 2 Specifying Window items Book and CD titles Variable names New terms File and directory names Commands and code examples Text typed by you Optional command parameters Required command parameters Exclusive command parameters where only one of the options can be specified About Idera At Idera, we deliver a new generation of tools for managing, administering, and securing your Microsoft Windows Servers, including SQL Server, SharePoint, PowerShell and Microsoft Dynamics. We employ numerous industry experts worldwide who are devoted to bringing proven solutions to you, the administrator. Idera provides solutions that help you ensure server performance and availability and reduce administrative overhead and expense. Our award-winning products install in minutes, configure in hours and deploy worldwide in days. Idera is a Microsoft Gold Certified Partner headquartered in Houston, Texas, with offices in London, UK, Melbourne, Australia, and Sao Paulo, Brazil. Idera Products Our tools are engineered to scale - from managing a single server to enterprise deployments with thousands of servers. Idera products combine ease of use with a design that installs in minutes, configure in hours, and deploy worldwide in days. To learn more about Idera products, visit our Web site (

18 3.2.1 Release Notes Idera SharePoint backup helps you to automate your SharePoint backups. SP backup includes flexible SharePoint restore and recovery. New features on page 18 Fixed issues on page 19 Tips on page 20 Known Issues on page 24 Granular backup and restore limitations on page 24 Recommended Idera Solutions on page 26 New features Idera SharePoint backup provides the following new features new features There are no new features for this release. 3.2 new features Enhanced Self-Service Recovery feature, with the ability to delegate recovery to users who are not Site Collection Administrators, faster and more precise backup set search, and deeper SharePoint integration. Faster performance on Granular Backup and Restore. Support for restoring multiple list item versions. Support for Tivoli Storage Manager destinations for backup sets. Automate load balancing for granular backups. Improved data grooming options, including the ability to retain a specified number of backup sets and per-backup job grooming settings. Integrated view of Farm Component and Granular backup operations in the Operation Queue tab. First-time configuration wizard to help you deploy and configure SP backup. 3.1 new features Expanded support for SharePoint 2010 farms, including the following components: SharePoint Root (14-hive). Internet Information Services (IIS) configuration. SharePoint site webroot folders..net Global Assembly Cache (GAC). Certificate Stores for SSL certificates. SharePoint-relevant registry entries. Related.NET Framework items, including machine.config files. Improved restore capabilities for farm component backups, especially search components. Automated in-place restore of the SharePoint farm, including the farm configuration database

19 In-place restore of Search components. Enterprise-scale improvements for SQL clustering, service scalability, and VSS integration. Improved handling of Volume Shadow Copy (VSS) configuration issues. Improved Backup Service database permission handling. SQL Server cluster support. SQL Server alias support, including IP addresses and fully-qualified domain names (FQDN). Improved Wide Area Network (WAN) and slow-link deployment scenarios. Improved handling of multi-farm networks. Automatic handling of farms with multiple products that use VSS. Improved handling of lists that contain one million or more items. 3.0 new features Farm backup for SharePoint 2010 farms, including configuration information, databases, and more. Integrates powerful SQL safe compression and encryption for SharePoint 2010 farm component backups. Real-time status updating that includes current progress and operation throughput. A Today page that reports farm component backup coverage for SharePoint 2010 farms. Improvements to scalability and fault-tolerance for all backup operations. Fixed issues This build includes many fixed issues, including the following: Fixed issues Improved support when restoring Web sites created with user templates deployed in a solution. Fixed an issue preventing certain Web apps from displaying objects and causing SP backup to display an error message. Fixed an issue preventing backup set grooming and causing users to run out of disk space. Fixed an issue causing the Management Console to hang when attempting to view the granular backup operation status. Fixed an issue preventing some Web app and site collections from appearing in SP backup Self-Service Recovery. Fixed an issue that caused SP backup to search for a backup file even after the site backup fails. Fixed an issue causing grooming to fail when a user deletes backup sets outside of the Management Console. 3.2 Fixed issues List item versions are now included in Granular Backups. SP backup can now restore the Master Pages Gallery as an individual object. Support for restoring multiple list item versions

20 3.1 Fixed issues Improved restore capabilities for farm component backups, especially search components. Enterprise-scale improvements for SQL clustering, service scalability, and VSS integration. Improved handling of Volume Shadow Copy (VSS) configuration issues. Improved Backup Service database permission handling. Improved Wide Area Network (WAN) and slow-link deployment scenarios. Improved handling of multi-farm networks. Automatic handling of farms with multiple products that use VSS. Improved handling of lists that contain one million or more items. 3.0 Fixed issues Tips Farm component protection for SharePoint 2010 farms, including configuration information, databases, and more. Integrates powerful SQL safe compression and encryption for SharePoint 2010 farm component backups. Real-time status updating that includes current progress and operation throughput. A Today page that reports farm component backup coverage for SharePoint 2010 farms. Improvements to scalability and fault-tolerance for all backup operations. The following tips for Idera SharePoint backup can help you to install and use SP backup. If you need further assistance with any item, please contact Support ( Installation and configuration issues When you install SP backup, the installer creates a new Web Application policy that grants Full Control to every Web Application in the farm, then assigns this policy to the Backup Service account. This version of Idera SharePoint Backup includes changes to the way that permissions are handled in differential backup and restore. When you upgrade to the current version, you should immediately perform a differential backup to accurately capture any permissions changes. If you add a Web Application to the farm after you install SP backup, you should restart all of the Idera SharePoint backup Service instances in the farm. General Considerations SP backup does not back up FAST Server Search components. When you specify a Backup Set Location, the full path of the location, including the Backup Set folder and the file name of any contents, must be less than 255 characters. If the path name is too long, backups may complete successfully, but restore operations fail. If a restore operation fails and the error message indicates that the file does not exist in the source directory, verify that the path is less than 255 characters. When you perform an out-of-place restore of any item, the full path of the item, including the item filename, must be less than 255 characters