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 [email protected] 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

21 If you use Restore or Quick Restore to restore in place and the target item already exists or is in the site or site collection recycle bin, a duplicate item may appear. Alternatively, an error may occur during the restore process. When you restore an item in place, you should ensure that the items that you are restoring do not exist in the site recycle bin, or the site collection recycle bin. When searching for items in a backup set, if there is a large number of matches for a given search term, some items that match the search term may not be included in the search results. The SP backup Management Service maintains a cache of the members of the Farm Administrators group. If you create a new Farm Administrator, the new Administrator does not have rights to existing backup sets until the Management Service refreshes its cache. Normally, the Management Service refreshes the cache every 5 minutes. You can also use the Services control panel to restart the Management Service to force it to rebuild its cache. If ActiveX Scripting is set to prompt, the help may not load properly, and the help window displays a blank screen. Under certain circumstances on Microsoft Office SharePoint Server (MOSS) 2007 farms, the Timer Job that SP backup uses to assign privileges to the Backup Service account does not load properly. When this occurs, only the "All Site Collections" node appears in the Granular Backup tab. No other Site Collections appear in the Granular Backup tab. If this occurs, you should restart the SharePoint Timer Service, then wait for the Timer Job to execute at the start of the next hour. After the Timer Job executes, restart every Backup Service in the farm. Considerations for Tivoli Storage Manager If you use a Tivoli Storage Manager (TSM) virtual client node as a Backup Location and the TSM Storage Pool runs out of free space, SP backup encounters errors. You should ensure that the TSM Storage Pool that hosts a Backup Location does not run out of free space. If you import a backup stored in a TSM virtual client node, you can only perform in place restores from that set. Management Console Considerations When the Management Console host is a Windows 2008 Server computer, an "Access Denied" error may appear when you try to stop or start the Backup Service. The error appears due to the User Account Control (UAC) group policy. You can either use the Run As command to run the Backup Service as the user <domain>\administrator or you can disable the User Account Control: Run all administrators in Admin Approval Mode local security policy. If you archive a backup set and remove it from the backup set storage location, the Idera SharePoint backup Repository Database contains cached information about the original location of the backup set. If you move the backup set to a new location and then import the backup set, you should close and then restart the Idera SharePoint backup Management Console before you restore SharePoint objects from that backup set. If the SQL Browser Service is stopped or is disabled on the computer that hosts the Repository Database, the error message "An error occurred connecting to the Repository Database. Please verify the preferences are set correctly for Repository Database Connection." appears. The Management Console relies on the SQL Browser service to con

22 nect to the Repository Database. Restart the SQL Browser Service and start the Management Console again. Backup Service Considerations Before you upgrade your SharePoint 2007 farm to SharePoint 2010 Foundation or Share- Point 2010 Server, you must disable all scheduled backups, and uninstall any Idera Share- Point Backup Service instances that are installed in your farm. After you upgrade from SharePoint 2007 to SharePoint 2010, you can reinstall the Backup Service instances. If you deploy a new a solution (WSP file) to your SharePoint farm while one or more Idera SharePoint Backup Service instances are running, you must restart all of the back instances before you create or perform a backup or an error message may appear. If a backup or restore job is in progress and the computer that hosts the Backup Service is rebooted, queued jobs may not start. If this occurs, restarting all Backup Service instances to start the queued jobs. Self-Service Recovery feature Considerations After you use the Self-Service Recovery feature to locate and preview a file that is part or a Granular Backup, you must reload the web page that contains the Self-Service Recovery feature to select and preview another file. When you use the Self-Service Recovery feature to locate and retrieve files, Idera Share- Point backup can only retrieve files from backup sets created by the same version of the product. This version retrieves files from backup sets created by this same version. To ensure that users can retrieve files with the Self-Service feature, you should perform a full backup of the content as soon as possible when you upgrade SP backup. Farm Backup and Restore Considerations If a SharePoint server with the Backup Service installed also hosts Microsoft SQL Server, you must ensure that the SQL Server VSS Writer component starts properly. If it does not, the Backup Service cannot back up the server components. The VSS Writer must start properly even if the SQL Server is not used as part of the farm. If the SharePoint Farm includes multiple Search services that are both running simultaneously, the servers that host the services do not properly register themselves with the VSS writer. You should remove the duplicate search services from your environment to let the VSS Writer connect to the servers. Farm Backup does not back up all of the SharePoint components. The WSS_Logging database does not appear in the list of selectable components, and it cannot be backed up by SP backup. If you restore a database that uses alternative authentication, you may need to manually restore the database connection with your SharePoint farm. When you use the Farm Configuration browser to view the contents of an XML file, the Management Console opens the file in memory on the Management Console host. If the file contains more than 10,000 rows, the Management Console may require a large amount of memory to open the file. In extreme cases, the file may contain in excess of 100,000 rows, and the Management Console may require in excess of 2 GB of memory. When you perform a Farm Backup, the Backup Service contacts the SQL Servers that host both the Repository Database and the SharePoint Content databases. If any SQL Server is unavailable or has not yet finished startup, or if one of the databases is not

23 yet available, the Farm Backup may fail. Ensure that all of the SQL Servers have completely started, then repeat the backup. SP backup relies on VSS to perform Farm Backups. Due to restrictions in the way that VSS works, only one VSS differential backup of a given component can be in use at any given time. If a different product performs a Full Backup with VSS, the existing differential backup is no longer valid. If you use a scheduled Farm Backup with differential backups to back up a SharePoint component and then use another product that uses VSS to perform a backup of the same component, SP Backup detects the use of the other product and automatically performs a full backup instead of a differential backup. If you use another product that supports differential backups with VSS and you use SP backup to perform a Farm Component backup, you may interfere with the other product. If you use multiple products that use VSS to perform backups, you should only use full backup Farm Backups in SP backup. If you select particular components or component types for a farm backup operation, then add a new component to your SharePoint farm, SP backup does not add the component to an existing backup job automatically. If you add a Content Database, Web Application, Configuration Database, or Service Application to the farm, you should create a new Farm Backup operation to back up the new component. If the operation includes All Farm Components, the backup includes new components automatically. If the certificates for your SharePoint farm are configured to prohibit certificate export or if certificate export requires a password, SP backup is unable to back the certificates up. If you enable database mirroring in SharePoint and SharePoint uses the mirrored database, Farm Component backups do not include SharePoint search components. If this occurs, SP backup displays a warning when the backup occurs. If you import a backup set created by SP backup 3.0 or 3.1 that contains a Farm Component backup, the details of the backup set do not appear in the Overview tab in the Farm Backup page. The backup content appears in the Restore tab in the Farm Backup page. You can successfully restore from the set even though the details do not appear. Out of Place Restores from SharePoint 2007 to SharePoint 2010 If you perform an out-of-place restore of a MOSS 2007 workflow to a SharePoint 2010 farm, warnings appear during the restore. The restore succeeds. Any content associated with the workflows is restored properly. The workflows themselves are not restored properly. The warnings appear as a result of the changes in workflow format in SharePoint If you perform an out-of-place restore from SharePoint 2007 to SharePoint 2010, the default SharePoint Web Parts appear two times on the home page of the restored web site. The Web Parts only appear a single time when you view All Site Content. Certain features available in SharePoint 2007 are not available in SharePoint 2010 and will not be restored. In order to prevent restore errors, it is recommended that these unsupported features are disabled in SharePoint 2007 before creating a backup of content that will be restored into a SharePoint 2010 Farm. "Office SharePoint Server Enterprise Site Features" and "Office SharePoint Server Standard Site Features" should be disabled. When restoring a Site Collection from a SharePoint 2007 Farm to a SharePoint 2010 Farm, some items are not supported in SharePoint 2010 and will not be restored. These items include the Site Template Gallery list. Some SharePoint 2007 Site Templates are not supported in SharePoint 2010 and may not restore correctly when restored Out of Place to a SharePoint 2010 Farm. These site

24 Known Issues templates include Wiki sites, Site Directories, Report Centers, Search Centers, Search Centers with Tabs, Collaboration Portals, Publishing Portals, Publishing Portals with Workflows and News Sites. Idera strives to ensure our products provide quality solutions for your SharePoint needs. The following known issues for Idera SharePoint backup are described in this section. Farm Backup and Restore Considerations If you use a scheduled Farm Backup with differential backups to back up a SharePoint component and also use another product that uses Microsoft Volume Shadow Copy Service (VSS) to perform a backup of the same component, the SP Backup differential backups succeed, but cannot be used to perform a restore. This happens because use of the thirdparty product invalidates the data that VSS uses to create differential backups. In the same way, if the other product supports differential backups and you perform a full backup with SP backup, you may interfere with the other product. If you use multiple products to perform backups, you should only use full backup farm backups in SP backup. Granular backup and restore limitations You rely on the backup and restore solution that you select to safeguard the data that is stored in your SharePoint farm. For you to trust the backup solution that you use, you need to fully understand the abilities and limits of the tool that you select. Idera is committed to giving you the information that you need to know about Idera SharePoint backup. SP backup can back up both SharePoint farm components and granular SharePoint objects. Farm component backups and granular backups work differently, and have different advantages and limitations. Your needs and your SharePoint environment may call for you to use one of the backup methods and not the other. Most SharePoint 2010 farms use both methods, because they are complementary, rather than a direct replacement. How do Farm Component Backups help me? Farm component backups use the Microsoft Volume Shadow Copy Service (VSS) to back up entire SharePoint components. That is, you can use SP backup to back up the entire farm, or every content database, or a single specific component. For backed-up components, the entire component is always backed up, with no limitations. When you restore, SP backup restores the entire component. You cannot restore a single Site Collection, or list, or item from a farm component backup without additional steps. You can use farm component backup to ensure complete backup coverage for the components that make up your SharePoint farm, or if you need to back up and recover objects that granular backup is unable to back up and restore. What are the limitations of a Farm Component Backup? A Farm Component backup includes all of any component that you include. When you perform a restore, you can restore the entire component. This means that while you can restore an entire Content Database, you cannot restore a single item from a single list in a Site Collection. A Farm Component backup helps you restore the entire farm when disaster strikes. It is not designed to help with the fallout from end-user errors

25 In addition, because Farm Component Backups rely on VSS to perform backups, only SharePoint 2010 farms can be backed up with a farm component backup You can use Granular Backups to supplement Farm Component Backups to provide item-level backup and restore capabilities for your SharePoint farm. How do Granular Backups help me? A granular backup uses the SharePoint object model to access individual SharePoint objects in the farm. Because it uses the Object Model, it is subject to certain limitations when it tries to back up and restore objects. You can use farm component backups to compensate for the limitations in granular backups, or to allow easier restoration of the entire component or farm. Because it backs up and restores at the object level, granular backup lets you restore individual objects. That is, you can restore any specific SharePoint object in-place or out-of-place. If you install the Self-Service Recovery feature, Site Collection Administrators and other trusted users that you specify can download backed-up content to their computer. Granular backups help you to accommodate the fallout from end-user error. What are the limitations of a Granular Backup? SP backup uses the SharePoint Object Model for granular access to the contents of your farm. This process makes sure that your SharePoint farm environment remains supported by Microsoft. Microsoft does not support use of methods other than the Object Model to access objects in the SharePoint farm. As a result, Microsoft can refuse to provide support for farms where you make changes outside of the Object Model. The publicly available methods and properties of the Object Model itself limit the access that SP backup has to some of the data in the farm. In other cases, the Object Model theoretically allows the required access, but the limits placed on that access make use of the Object Model impractical. For example, access to the data may impose performance penalties on the backup and restore process or on the farm that cannot be overcome. SP backup makes every attempt to backup and restore the data that is stored in your farm. The constraints introduced by reliance on the Object Model prevent access to certain elements of the farm. Any backup tool that provides granular access to the objects in your SharePoint farm operates under these same limitations. You can use Farm Component Backups to supplement Granular Backups and provide comprehensive backup and restore capability for the components that make up your SharePoint farm. For additional information about support from Microsoft for your Share- Point farm, see For complete information about performing granular backup of specific SharePoint objects, see the Idera Knowledge Base. How does Idera SharePoint backup safeguard data? SP backup strives for high fidelity to the data that is stored in your farm. As a result of the constraints imposed by adherence to the SharePoint Object Model, it is not possible to both strictly adhere to the Object Model and to provide a full-fidelity backup and restore

26 Granular backups include all of the data accessible using the Application Programming Interfaces (APIs) and methods that Microsoft supports. SP backup does not back up data when the publicly exposed methods and properties of the SharePoint Object Model do not allow SP backup to access the data. As with backups, use of the Object Model for Granular Restore imposes certain limits on what SP backup can restore. When SP backup is unable to restore backed-up data, it generates a warning about the data and attempts to continue the restore process. Idera continuously works with Microsoft and with customers to address issues that affect individual environments. If you are unable to restore backed-up content that is not described below, please contact Idera Technical Support for assistance. Tip: If you do not enable site locking when you perform granular backups of your SharePoint farm content, the granular backup sets may include inconsistencies. Some of these inconsistencies may cause the backup sets to become unusable. The inconsistencies may only be apparent when you try to restore the content, not when the backup is made. You should use caution when you disable site locking during granular backups. For more information about these inconsistencies, see /Downloads/ProdCollateral/Consistency-Creating-SharePoint-Backups.pdf. Recommended Idera Solutions Idera strives to ensure our products provide quality solutions for your Microsoft SharePoint needs. The following Idera Solutions were recently added to the knowledge base at our Customer Service Portal ( Number Title What ports are used by SharePoint backup? Idera SharePoint Backup Console constantly displays the "Loading..." message when you attempt a backup or restore. Users receive 'Access is Denied' or '403 Forbidden' error while sites are being backed up with SharePoint Backup. Warning during backup, "Unable to export the XML for web part." Error when configuring WFE for SharePoint backup, "Unable to retrieve the configuration database connection string."

27

28 Learning about the components and architecture Idera SharePoint backup provides a robust, easy-to-use SharePoint backup and restore solution. Behind a friendly user interface, SP backup offers a unique architecture that is both flexible and extremely powerful. Idera SharePoint backup fits your environment, no matter how simple or complex. The following diagram illustrates the components of the Idera SharePoint backup architecture. SP backup uses the SharePoint and Active Directory permissions that you set in your environment to control access to content and to farm components. Learning about the components For more information about permissions, see Learning about the requirements on page 34. The SP backup components include the following: Idera SharePoint backup has a light, unobtrusive architecture that easily runs in your environment with minimal configuration. SP backup does not add to or modify any of your native SharePoint files or services when you install it. When needed, SP backup does make changes to needed permissions. Management Console You use the SP backup Management Console to configure SP backup, view operation status and history, schedule automated backup activities, and perform other related functions. The Management Console includes comprehensive Today pages for the farms you specify. The Today page includes a view of the backup status and recent backup and restore operations. You also use the Management Console to configure SP backup and to perform backup and restore tasks

29 Multiple copies of the Management Console can all contact a single Management Service. You can let each of the SharePoint administrators in your environment collaborate to perform backup and restore operations. In addition, if your environment includes multiple SharePoint farms, each Management Console can connect to one or more of the farms simultaneously. You can use the SP backup installer to install the Management Console and Management Service on a computer, or you can install the Management Console only. If you install only the Management Console, you must install the Management Service on another computer. Management Service Backup Service The Management Service receives requests from the Management Console and from the SP backup Self-Service Recovery feature. Based on those requests, the Management Service connects to one or more Backup Service installations hosted on a Share Point Web Front End (WFE) or on a SharePoint Database Server and starts the requested operation. You can install the Management Service on any computer in your network. The Management Service host does not need to be a part of the SharePoint farm. The host that you select should be running at all times so that it can contact and manage the Backup Service when needed. Both the Management Service and the Management Console are installed when you perform a full install of SP backup. You cannot install only the Management Service. The Management Service uses the SP backup Repository Database to store historical data. Each Management Service uses a separate Repository Database. If you schedule an activity, the Management Service initiates the scheduled activity and records its progress and status. The Backup Service performs any backup and restore operations you request. When an on-demand or scheduled operation begins, the Management Service contacts the Backup Service and initiates the operation. The Backup Service uses the Microsoft Volume Shadow Copy Service (VSS) to backup SharePoint 2010 Farm components. The Backup Service uses the SharePoint object model to backup and restore granular SharePoint content on any SharePoint 2007 or 2010 farm. To perform Granular Backups of SharePoint 2007 and SharePoint 2010 farms, you install the Backup Service on at least one WFE in your farm. You can install the Backup Service on every WFE in your farm. Multiple Backup Service installations let you balance backup loads between servers and configure fault tolerance for your backups. You can specify how many simultaneous threads the Backup Service uses when it performs Granular Backups

30 To perform Farm Backups for SharePoint 2010 farms, you install the Backup Service on every WFE and every Database Server in the SharePoint 2010 farm. The Backup Service stores the objects that it backs up in backup sets. You specify a location where the Backup Service stores the sets. You can specify a UNC location or a Tivoli Storage Manager (TSM) virtual client node. You can use the Management Console to discover your WFE hosts and standalone Database Server hosts and install the Backup Service. You can also use the SP backup installer to manually install the service on a WFE host or Database Server host. You can only install one Backup Service on each server, but the Backup Service can be shared by multiple Management Service copies. You can back up content databases from a SQL Server host that is shared between farms as part of the relevant farms. When it starts, the Backup Service verifies connectivity to the farm and to the Web Applications in the farm. To perform backups, the Backup Service account must be assigned a Full Control policy for every Web Application in the farm. When it starts, the Backup Service assigns the required policies to the Backup Service account. If you add a Web Application to the farm, you should restart all of the Backup Service copies so that the Backup Service can grant privileges for the new Web Application. Repository Database Self-Service Recovery feature The SP backup Repository Database stores configuration information, backup and restore operation data, and statistical and other data that the Management Service collects. Each Management Service uses a separate Repository Database. A single SQL Server host can host multiple uniquely-named Repository Databases. The SQL Server that hosts the Repository Database does not need to be part of the SharePoint farm. The Repository Database does not store backed up SharePoint content. The Self-Service Recovery feature lets authorized SharePoint users help themselves when they need to recover specific library items from granular backups. The self-service feature saves backup administrators time and effort while also giving Site Collection administrators fast, convenient access to their backed up library items. You install the Self-Service Recovery feature when you configure SP backup for your farm

31 Learning about data grooming Idera SharePoint backup can automatically delete backup sets after a time that you specify. This expiration lets you save disk space for more recent backups. You can specify the time until SP backup deletes a backup and the time of day that SP backup performs the delete. Data grooming only applies to Granular Backups. If you enable Data Grooming, SP backup checks daily at the time you specify for expired backup sets. If SP backup discovers an expired set, it deletes the set. If a full backup is older than the age you specify but is associated with a differential backup that is younger than the age you specify, the full backup is not groomed. You can configure data grooming preferences separately for each farm in the Management Service preferences in the SP backup Management Console. You can also set grooming options for a scheduled backup job. You can also specify that SP backup always keeps a certain number of good backups, no matter the age of the backup. For information about setting the Management Service Preferences, including grooming, see Defining the Management Service preferences on page 76. For information about configuring grooming for a scheduled backup, see Specifying backup schedule grooming in the SP backup help. By default, backup data is not groomed automatically. When you enable data grooming, you should schedule it for non-peak hours. Data grooming can be a processor-intensive and disk-intensive process, and can interfere with your enterprise network. Tip: SP backup can use Tivoli Storage Manager (TSM) to store backup set content. If you enable data grooming for a backup set that SP backup stores in TSM, SP backup removes references to the data in SP backup. In addition, SP backup sets the data objects to Inactive in TSM. SP backup does not automatically delete the data itself. If you need to delete the data from TSM, you should use the TSM management tools to do so. For more information about using TSM, see Learning about Tivoli Storage Manager on page 32. How do I enable data grooming? You use the Idera SharePoint backup Management Service preferences to configure data grooming. To configure the Data Grooming preferences 1. In the SP backup Management Console, do one of the following: Click the name of the farm whose data grooming preferences you want to set, then click Tools > Preferences. In the Idera SharePoint backup Preferences dialog box, click Management Service. In the left pane, click Configuration, then click the name of the farm whose data grooming preferences you want to set, then click Management Service

32 2. In the Grooming area, select or clear the Delete backup sets from repository check box. If you select the check box, you should also set the number of days before the data expires and the time on the Management Service computer when the SP backup Management Service checks for expired backup sets. Learning about communications and security Depending on the configuration of your SharePoint farm and your enterprise network, many of the computers in your network can host the Idera SharePoint backup components. The components use encrypted TCP/IP communications to communicate with one another. SP backup encrypts all internal communications between components. If a component is not able to negotiate an encrypted communications channel, the communication fails. This helps to ensure the security of your SharePoint data. SP backup uses the Microsoft.NET Windows Communications Foundation (WCF) services to secure communications. All communications channels use transport encryption and signing, and do not use non-fips encryption methods. All communications within SP backup are therefore FIPS-compliant. You can customize the communications ports for each component if you choose. Contact Idera Technical Support for assistance to change the port. The components use the following default ports: Source Management Console Self-Service Recovery feature Backup Service Destination 3. Click OK to close the dialog box and save the changes you made to the Data Grooming settings. Port Management Service Management Service Backup Service In addition, you should enable the Remote Administration option in the Windows Firewall for each server in the farm to let the SP backup Management Console contact the server. All of the SP backup components should be hosted by computers that are members of the same farm or by farms that have mutual trust relationships defined. SP backup encrypts Farm Backups with the AES-128 algorithm. AES-128 is FIPS-compliant. Learning about Tivoli Storage Manager Tivoli Storage Manager (TSM) is a product from IBM that helps you to manage storage and backup on your enterprise network. If your enterprise network includes a TSM deployment, you can configure Idera SharePoint backup to store backup sets in TSM. Before you can use TSM as a Backup Location in SP backup, you must configure it

33 The precise steps that you follow to configure TSM in your environment depend on the version of TSM you have installed, and the way that your environment is configured. In general, though, you must do the following: Install and configure the TSM client software on every server in your SharePoint farm where the Backup Service is installed. On the TSM server, create a single virtual client node that the clients share. Grant access to the virtual client node to every server that hosts a Backup Service. In TSM, configure the options for the virtual client node. In addition to whatever options are appropriate for your deployment, you must set the option backdel=yes. In the SP backup Management Console, when you create a TSM Backup Location, you enter the name of the virtual client node where SP backup stores the backup data. The default TSM filespace that SP backup uses is IderaSPBackup. For information about installing configuring TSM and configuring the TSM client options, see your TSM documentation set. For information about creating a Backup Location, see Defining the Backup Service preferences on page 73. Tip: If you enable data grooming for a backup set that SP backup stores in TSM or if you manually delete the reference to a backup set that is stored in TSM from the Management Console, SP backup removes references to the data in SP backup. In addition, SP backup sets the data objects to Inactive in TSM. SP backup does not automatically delete the data itself. If you need to delete the data from TSM, you should use the TSM management tools to do so

34 Learning about the requirements You can install Idera SharePoint backup on any computer that meets or exceeds the hardware, software, and permission requirements. When you install multiple components on a single host computer, the computer should meet or exceed all of the requirements for the components. Consider the following requirements when you install SP backup in a typical environment. Learning about the SharePoint requirements on page 34 Learning about the Management Console requirements on page 34 Learning about the Management Service requirements on page 35 Learning about the Backup Service requirements on page 35 Learning about the Self-Service Recovery feature requirements on page 37 Learning about the Management Service permission requirements on page 37 Learning about the SharePoint requirements To use Idera SharePoint backup, you must have at least one Microsoft SharePoint farm installed and configured. The farm can be any of the following versions: Windows SharePoint Services (WSS) 3.0 Microsoft Office SharePoint Server (MOSS) 2007 Microsoft SharePoint Foundation 2010 Microsoft SharePoint Server 2010 Tip: To perform a Farm Component backup, your SharePoint farm must have SharePoint 2010 SP1 installed. Learning about the Management Console requirements You can install the Idera SharePoint backup Management Console alone or in concert with the other SP backup components. Tip: If you install the SP backup Management Console with any other SP backup components, you must use a version of Windows Server. Windows XP, Windows Vista, or Windows 7 can only host the Management Console. The computer where you install the Management Console must meet the following minimum requirements: 2.0 GHz or faster CPU. 2 GB or more memory. The required memory size varies, depending on the size of the Share- Point objects you back up. 50 MB free hard disk space. Microsoft.NET framework 3.5 SP1. Monitor capable of displaying 16-bit or more colors at a resolution of 1024 X 768 or higher. One of the following Windows versions, either 32-bit or 64-bit: Windows XP SP2 or later Windows Server 2003 SP2 Windows Vista SP2-34 -

35 Windows Server 2008 SP2 Windows Server 2008 R2. Windows 7 The Management Console user does not need to be a member of the Local Administrators group, Learning about the Management Service requirements You install the Idera SharePoint backup Management Service automatically when you install the other SP backup components. The computer that hosts the Management Service always hosts the Management Console. The computer where you install the Management Service must meet the following minimum requirements: 2.0 GHz or faster CPU. 2 GB or more memory. The required memory size varies, depending on the size of the Share- Point objects you back up. 50 MB free hard disk space. Microsoft.NET framework 3.5 SP1. Monitor capable of displaying 16-bit or more colors at a resolution of 1024 X 768 or higher. One of the following Windows versions, either 32-bit or 64-bit: Windows Server 2003 SP2 Windows Server 2008 SP2 Windows Server 2008 R2. In addition, the Management Service stores preferences and other information in a Repository Database. You specify the Microsoft SQL Server host for the database when you install the SP backup components. The SQL Server host that you select should be one of the following: Microsoft SQL Server 2005 SP3 Microsoft SQL Server 2008 SP1 Microsoft SQL Server 2008 R2 In addition, Microsoft SQL Server 2000 SP4 is supported only if you use Microsoft SharePoint Learning about the Backup Service requirements You install the Idera SharePoint backup Backup Service on every SharePoint Web Front End (WFE) server and Database Server in the SharePoint 2010 farms that you back up. For SharePoint 2007 farms, you install one or more Backup Service instances on the SharePoint WFE servers and Database Servers in the farm. What are the hardware and software requirements for the Backup Service? Any server that hosts the Backup Service must meet the following requirements: 2.0 GHz or faster CPU. 2 GB or more memory. The required memory size varies, depending on the size of the SharePoint objects you back up. 50 MB free hard disk space

36 Microsoft.NET framework 3.5 SP1. One of the following Windows versions, either 32-bit or 64-bit: Windows Server 2003 SP1. Windows Server 2003 R2. Windows Server Windows Server 2008 R2. What are the permission requirements for the Backup Service user account? When you install the Backup Service, you specify a user account that the Backup Service uses to access the farm. The Backup Service account that you specify requires the following permissions to perform backups and restores: Windows permissions SharePoint permissions SQL Server permissions The Backup Service account must have write permissions to the installation folder on the WFE and to the folder where you store backup sets. To perform Farm Backups of SharePoint 2010 farms, the Backup Service account must be a member of the Local Administrators group on the server that hosts the Backup Service. On SharePoint 2010 farms, the Backup Service user account must also be able to perform Microsoft Volume Shadow Copy Service (VSS) operations on the computer that hosts the Backup Service. Normally, members of the Local Administrators group have these permissions, but they can be removed by a Group Policy Setting. If your group policy settings makes changes to the Local Administrator group privileges, you should ensure that the Backup Service user has the following privileges: Act as Part of the Operating System Backup Files and Directories Create a Token Object Logon as a service Manage Auditing and Security Log Restore Files and Directories Take ownership of files and other objects If the SQL Server is a part of the farm, The Backup Service account must be a member of the SharePoint Farm Administrators group. If the farm uses a standalone SQL Server, there is no SharePoint Farm Administrators group on the server. The Backup Service account must have db_owner permissions for all SharePoint content databases, including the Admin Content and SharePoint Config databases to perform granular backups. In addition, SP backup needs access to all SharePoint databases to perform farm content backups

37 You should manually grant these permissions for the Admin Content and SharePoint Config databases to the Backup Service user account before you install the Backup Service. For all other databases, you can manually grant these permissions, or the Backup Service timer job can grant the permission automatically. When it runs, the Backup Service creates a SharePoint timer job. The job is named Idera Share- Point backup Confirm Backup Service Permissions. The Backup Service queues the job immediately when it creates the job. In addition, the timer job is scheduled to run at the beginning of every hour. Depending on the state of your Timer Job queue, execution of the timer job may be delayed. If desired, you can use the SharePoint Central Administration page to check the job status. The timer job assigns the db_owner role on every SharePoint database to the Backup Service user account that you specify. In addition, the timer job assigns the Full Control policy for every Web Application in the farm to the Backup Service user account. The timer job ensures that the Backup Service can access every SharePoint database to perform backups. Normal SharePoint operations, including creating a new Web Application or a Service Application, can create new databases. If you disable the job, you must manually assign permissions for the new databases or backups can fail. When you perform an operation that creates a new database, you can use the SharePoint 2010 timer job controls to manually start the job. You can also wait until the start of the next hour for the job to run on schedule. Learning about the Self-Service Recovery feature requirements The Idera SharePoint backup Self-Service Recovery feature lets Site Collection Administrators restore the backed up content for which they are responsible. To restore content, the user must currently be a Site Collection Administrator. In addition, the user must have had Site Collection Administrator privileges for the content when the backup took place. You can deploy the feature to any Web Front End (WFE) in your SharePoint farm. When you configure SP backup for your farm, you can automatically deploy the feature to the farm. Learning about the Management Service permission requirements The user account that you specify for the Idera SharePoint backup Management Service must have the following permissions: Must be a local administrator on the computer that hosts the Management Service. Must be a member of the db_owner role for the Repository Database. To perform Farm Backups of SharePoint 2010 farms, the account must be a member of the SharePoint Farm Administrators group. You specify the database to use as the Repository Database when you install the Management Services

38 In addition, when you install SP backup, the installer also assigns the permissions required to access the Microsoft Volume Shadow Copy Service (VSS) to the Farm Account and to the account that you specify for the Backup Service. For more information about the VSS permissions, see

39

40 Installing and deploying Idera SharePoint backup You can install and deploy Idera SharePoint backup in any network environment. You must have at least one Microsoft SharePoint farm deployed to use SP backup. o Learn about the architecture and components. See Learning about the components and architecture on page 28 and Learning about the components on page 28. o Review the requirements. See Learning about the requirements on page 34. o View the installation instructions. See Installing Idera SharePoint backup on page 40. Installing Idera SharePoint backup Idera SharePoint backup helps you to back up and restore the content of SharePoint 2007 and 2010 farms and the farm components that make up your SharePoint 2010 farms. Before you can use SP backup, you must select one or more computers to host the product components and install it on those computers. The computers that host the components must meet minimum requirements for the components that you install. For information about the requirements, see Learning about the requirements on page 34. If you plan to install SP backup on a "standalone" SharePoint server or a "basic install" of Share- Point 2007 or SharePoint 2010, see Installing on a standalone SharePoint server on page 41 for additional information. Tip: The account that you use to install SP backup must not have Windows User Account Control (UAC) enabled when you install. If UAC is enabled, the installation cannot finish successfully. How do I install Idera SharePoint backup? You use the SharePoint backup installation kit to install SharePoint backup. You can install SP backup on any computer that meets or exceeds the product requirements. For information on the requirements, see Learning about the requirements on page 34. When you download the installation kit from the Idera web site, the version of the installation kit that you use varies, depending on the operating system that hosts SP backup: Host Operating System 32-bit 64-bit Install Kit Filename IderaSharePointbackupInstallationKit.exe IderaSharePointbackupInstallationKit-x64.exe To install all of the Idera SharePoint backup components on a single computer 1. Log on to the computer where you want to install SP backup. You should use a user account that is a member of the Local Administrators group on the computer. In addition, the account that you use must have the sysadmin role assigned for the SQL Server instance that hosts the SP backup Repository Database

41 2. If you downloaded the SP backup installation kit, use following steps. If you obtained the SP backup installation kit on a disc, continue with step 3. a. Use Windows Explorer to locate the installation kit file, and then double-click the file. You can locate the filename in the table above. b. In the Idera SharePoint backup Installation Kit dialog box, click Continue. c. In the Select the folder dialog box, click OK. d. If the installation kit prompts you to create the folder, click Yes. e. When prompted, click OK to start setup. 3. If you obtained the SP backup installation kit on a disc, use the following steps: a. Insert the disc into your computer. b. If the setup program does not start automatically, double-click Setup.exe in the installation disc. 4. In the Welcome dialog box, click Install. 5. In the Install page, click Install Idera SharePoint backup. 6. In the Welcome page, click Next. 7. In the License Agreement page, review the terms of the license agreement, and then click I accept the terms in the license agreement, then click Next. 8. In the Destination Folder page, select a location to install the components, and then click Next. 9. In the Setup Type page, click Full Install to install all SP backup components on a single computer or click Console Only to install only the SP backup Management Console, and then click Next. 10. If you chose to install all of the components and the Microsoft firewall is enabled on the host computer, the Microsoft Firewall Enabled page reminds you to open the required ports for the Management Service. Click Continue. 11. If you chose to install all of the components, search for and then select a SQL Server instance and database name for the Repository database. You can also specify the credentials that the setup wizard uses to connect to the SQL Server. Click Next. 12. In the Idera SharePoint backup Management Service Account page, specify SQL Server Authentication credentials that the Management Service uses to connect to the Repository database, and then click Next. 13. In the Ready to Install the Program page, click Install. 14. In the Setup Wizard Completed page, click Finish. If you leave Launch Console selected, the SP backup Management Console starts. Installing on a standalone SharePoint server When you install Microsoft SharePoint, you can choose to perform a "standalone" or basic install on a single server that hosts all of the SharePoint components. The installer optimizes the component settings on a standalone SharePoint farm for the standalone environment. If you install Idera SharePoint backup on a standalone farm, you must make certain changes to these settings to give SP backup access to both the farm components and its own components. Tip: When you install on a multi-server farm, you do not need to make these changes. The changes are required only for standalone or basic installations of SharePoint 2007 or SharePoint

42 You must make these changes to your standalone SharePoint server before you install SP backup. Until you make the changes, SP backup cannot complete the Configuration Wizard and install the Backup Service. What changes do I need to make to a standalone SharePoint 2007 farm to install SP backup? Before you install SP backup on a standalone SharePoint 2007 server, you should make the following changes to your SharePoint farm: You must ensure that the SQL Server Browser Service on the SharePoint server is running. You must configure the Microsoft#SSEE instance to accept either TCP/IP or Named Pipes connections. You must disable the Hide Instance option in the SQL Server Configuration Manager. You use SQL Server Management Studio to manage the Microsoft#SSEE instance. In SQL Server Management Studio, you can use the following connection string to access the #SSEE instance: \\.\pipe\mssql$microsoft##ssee\sql\query -E What changes do I need to make to a standalone SharePoint 2010 farm to install SP backup? Before you install SP backup on a standalone SharePoint 2010 server, you should make the following changes to your SharePoint farm in the SQL Server Configuration Manager: Enable TCP/IP for the SQL Server instance. The instance name is <server name>\shar- EPOINT. Enable Named Pipes for the SQL Server instance. In the Services Control Panel, do the following: Set the startup type of the SQL Server Agent to Automatic. Set the startup type of the SQL Server Browser to Automatic. Start or restart the SQL Server Agent. You can then install Idera SharePoint backup and run the Configuration Wizard. For information about installing, see Installing Idera SharePoint backup on page 40. For information about the Configuration Wizard, see Configuring Idera SharePoint backup for your farm on page 52. When you have completed the Configuration Wizard, immediately quit the SP backup Management Console. In the Services Control Panel, you should change the login account for the SharePoint VSS Writer service to LocalSystem, then restart the service. Before you install SP backup, the SharePoint VSS Writer service runs as Local Service. As part of the Configuration Wizard, SP backup issues the command stsadm registervsswriter, which changes the account. When you set the service to run as LocalSystem, you are returning the service to its original settings. After making the changes, you can use SP backup normally

43 Installing the Backup Service manually When you add a farm to your Idera SharePoint backup installation, the Configuration Wizard lets you install a copy of the Backup Service on the SharePoint Web Front End (WFE) servers and Database Servers. If your disaster recovery planning only includes granular backups, SP backup uses the SharePoint object model to access the objects that you back up. When you perform granular backups, the Backup Service is only required on a single WFE. Additional Backup Service copies help you to ensure fault tolerance and to balance backup loads when you perform Granular Backups. You should generally install the Backup Service on every WFE in your farm. If your disaster recovery planning includes farm backups of SharePoint 2010 farms, you must install the Backup Service on every WFE and every Database Server in your SharePoint farm. When you use the Configuration Wizard, you must install the Backup Service on at least one WFE. Tip: The first Backup Service that you install must always be on a WFE server. You should normally use the Configuration Wizard to install the Backup Service on every WFE and every Database Server in your SharePoint farm. You can also use the SP backup Management Console to install the Backup Service on WFE hosts in the SharePoint farm. In addition, if you add a WFE or a Database Server to your farm, you can use the Management Console to install the Backup Service on the new server. Finally, you can use the SP backup installer to install the Backup Service on the WFE or Database Server directly. To do so, you must be able to log in to the server with an account that is a member of the Administrators group on the server. When you install a Backup Service, you select the WFE server or Database Server to install on. You also specify the user name and password that the Backup Service uses to run. The user account that you specify must have specific permissions for the farm. For information on the permissions that the Backup Service user account requires, see Learning about the Backup Service requirements on page 35. If you perform Granular Backups, the SharePoint Services Web Application Service must be operating on the WFE where you install the Backup Service. If the server does not have the Web Application Service active, you can use the SharePoint Central Administration page to install it. What permissions does the service account for the Backup Service require? The account you use as the service account for the Backup Service must have the following permissions: Member of the Local Administrators group on the WFE host. Member of the Farm Administrators group in the SharePoint farm. Must have at least db_owner permissions for all SharePoint content databases, including the Admin Content and SharePoint Config databases. Tip: If the account that you use is not a SQL Server System Administrator,

44 you should use the SQL Server Management Studio to grant the account access to the Repository Database that you specified when you installed SP backup. The default database name is IderaSPBackupRepository. How do I install the Backup Service on a WFE or a Database Server with the Management Console? You use the Install Backup Service dialog box to install the Backup Service on a WFE or a Database Server. To install the Backup Service on a WFE or a Database Server with the Management Console 1. In the left pane of the SP backup Management Console, click Configuration. 2. In the Configuration pane, click the name of the WFE or Database Server where you want to install the Backup Service. 3. In the ribbon, click Install Backup Service. 4. In the Install Backup Service dialog box, enter the credentials of the account that the Backup Service should use. Specify the username in <domain name>\<user name> format. 5. Click Install 6. In the Information dialog box, click OK. How do I use the SP backup installer to install the Backup Service on a WFE or a Database Server? To use the SP backup installer to install the Backup Service on a WFE or a Database Server, you must first log in to the server with an account that is a member of the local administrators group. To use the SP backup installer to install the Backup Service 1. On the WFE or Database Server, start the SP backup installer. 2. In the Idera SharePoint backup installer, click Install Backup Service. 3. In the Setup Wizard Welcome page, click Next. 4. In the License Agreement page, read the License Agreement, then if you agree with the terms of the license, click I accept the terms in the license agreement, then click Next. 5. In the Destination Folder page, you can click Change to specify a custom folder. Click Next. 6. In the Idera SharePoint backup Service Account page, enter the credentials of the account that the Backup Service should use. Specify the username in<domain name>\<user name> format. Click Next. 7. In the Service Location page, enter the computer that hosts the SP backup Management Service. You can enter the IP Name, NetBIOS name, or IP address of the host. Click Next. 8. In the Ready to Install the Program page, click Install. 9. In the Setup Wizard Completed page, click Finish

45 Upgrading Idera SharePoint backup Idera SharePoint backup is the latest version of SP backup. If you have an earlier version of SP backup, you should upgrade to this version to access the new and improved features available. For information on the new and upgraded features, see: New features on page 18 Fixed issues on page 19 For information about upgrading your installed SP backup deployment, see: Upgrading to Idera SharePoint backup on page 45 Upgrading to Idera SharePoint backup You can upgrade your existing Idera SharePoint backup deployment to the current version to access the new and improved features available. For information on the new and upgraded features, see: New features on page 18 Fixed issues on page 19 You can upgrade the following versions of SP backup to this version: Tip: This version of SP backup cannot upgrade backup sets from versions earlier than 3.0. If you used a version of SP backup earlier than 3.0 to create a backup set, contact Idera Technical Support for assistance to upgrade the backup set. How do I upgrade from version 3.0 and later versions? Follow these steps... Ensure the computers on which you want to upgrade Idera SharePoint backup meet or exceed the product requirements. See the following: Learning about the requirements on page 34 Learning about the SharePoint requirements on page 34 Learning about the Management Console requirements on page 34 Learning about the Management Service requirements on page 35 Learning about the Backup Service requirements on page 35 Learning about the Self-Service Recovery feature requirements on page 37 Learning about the Management Service permission requirements on page 37 Ensure that the account that you use to log on to the computers that host the SP backup components. The account must also have administrator privileges on the Repository Database. Identify the upgrade path your environment requires. For more information, see What upgrade options are available?

46 Follow these steps... Temporarily disable any Scheduled jobs and allow any currently running or queued backup/restore operations to complete. If you deployed the Idera SharePoint Self Service Recovery Web Part solution, remove the Web Part and use the SharePoint administration tools to retract the Solution package. Close all open applications on the SP backup component hosts. Ensure that the.net Framework 3.5 is running on the target computer. Upgrade your installation to Idera SharePoint backup using the appropriate path. For more information, see How do I upgrade a full installation? and How do I perform a custom upgrade? If you plan to use Farm Backups for your SharePoint 2010 farm, use the Management Console to deploy additional Backup Service instances on every Web Front End (WFE) and Database Server in the farm. See Installing the Backup Service manually on page 43. If you plan to use the new Self-Service Recovery feature, use the Management Console to deploy the Self-Service Recovery components manually. See Manually installing the Self-Service Recovery feature on page 69. What upgrade options are available? SP backup includes the following components: Management Console Repository Database Management Service Backup Service The type of upgrade that you need to perform depends on your environment. The following table helps you choose between a Full or custom upgrade path. Environment Simple environment, where the Management Console, the Repository Database, and the Management Service all reside on the same computer Multiple Management Console instances in an environment. Upgrade Strategy Full Custom Description You can use the installer to upgrade a simple environment. See How do I upgrade a full installation?. An installation with multiple Management Console instances requires both a Full Install and Console-only instal

47 Environment Upgrade Strategy Description lations to upgrade. See How do I upgrade a full installation? and How do I perform a custom upgrade?. Manually deployed Backup Service Custom Manually installed Backup Service instances can be remotely or manually upgraded. See How do I upgrade the deployed Backup Services?. The installed Backup Service should always be the same version as the Management Service and Management Console. After the upgrade is complete, you must restart the Management Console. How do the Backup Service upgrade paths differ? Upgrading the Backup Service may slow the normal operations of the SharePoint servers that host the Backup Service. You should consider upgrading previously deployed Backup Service installs off-hours during a single time period according to your corporate change policies. The first time that you start the Management Console when the upgrade is complete, the Management Console prompts you to remotely upgrade a previously deployed primary Backup Service automatically. See How do I upgrade the deployed Backup Services?. If you remotely deployed the Backup Service instances, the first time that you run the Management Console after the upgrade is complete, the Management Console prompts you to upgrade the primary Backup Service. This version Management Console and Management Service SP backup require the version the same version Backup Service. If you do not upgrade when prompted, no backup or restore operation can occur. If you manually deployed the Backup Service, you can remotely deploy the upgrade. You can also run the Backup Service setup program on the computer that hosts the Backup Service to manually upgrade the service. How do I upgrade a full installation? You can use the Full install to upgrade your installation to this version of SP backup if you have a centralized deployment or if you are upgrading from a trial installation. This process assumes you can upgrade all deployed Backup Service instances during the same time period. In a full installation, all of the SP backup management components are installed on the same physical computer. These components include the following:

48 Repository Database Management Service Management Console Once you perform the upgrade, scheduled backups will not run successfully until you upgrade the Backup Service instances. After you upgrade the management components, you can use the Management Console to upgrade the Backup Service instances. To perform a Full Install upgrade 1. Perform a Full install to upgrade the management components to the new version. When prompted during the install, verify the name of the Repository Database. For more information about installing, see Installing Idera SharePoint backup on page Upgrade all previously deployed Backup Service instances. See How do I upgrade the deployed Backup Services?. How do I perform a custom upgrade? When you upgrade a custom environment, you first perform a Full Installation to upgrade the core components. After this update is complete, you can use the Console-only install to upgrade any additional Management Console installations that share a single Management Service and Repository Database. Finally, you upgrade all deployed Backup Service instances. To perform a custom upgrade: 1. Perform a Full install to upgrade the management components to the new version. When prompted during the install, verify the name of the Repository Database. For more information about installing, see Installing Idera SharePoint backup on page Upgrade all previously deployed Backup Service instances. See How do I upgrade the deployed Backup Services?. 3. Upgrade all existing installations of the Management Console by performing a Consoleonly install on each host computer. How do I upgrade the deployed Backup Service instances? You can use the SP backup Management Console to upgrade a deployed Backup Service. You can also use the setup program to manually upgrade a Backup Service. When you use the Management Console to upgrade the Backup Service, you can upgrade either the primary Backup Service or all Backup Service instances. If you choose to upgrade only the primary Backup Service, you must use the SP backup installer on each Backup Service host to manually upgrade the secondary Backup Service instances. To use the Management Console to upgrade all Backup Service instances 1. Upgrade the SP backup Management Console and Management Service to the current version. 2. Run the SP backup Management Console. The Management Console lists the Backup Service deployments and prompts you to upgrade them. You can upgrade the primary Backup Service or all Backup Service instances. To use the installer to manually upgrade a Backup Service 1. Log on to the computer where you want to upgrade the Backup Service. You should use a user account that is a member of the Local Administrators group on the computer

49 2. Do one of the following: If you downloaded the SP backup installation kit, use the Windows Explorer to locate the installation kit file, and then double-click the file. You can locate the filename in the table above. In the Idera SharePoint backup Installation Kit dialog box, click Continue, then in the Select the folder dialog box, click OK. If the installation kit prompts you to create the folder, click Yes. When prompted, click OK to start setup. If you obtained the SP backup installation kit on a disc, insert the disc in your computer. If the setup program does not start automatically, double-click Setup.exe in the installation disc. 3. In the Welcome to SharePoint backup dialog box, click Install. 4. In the Install page, click Install Backup Service. 5. In the Upgrade Wizard for Idera SharePoint backup Service page, click Next. 6. In the License Agreement page, if you agree with the terms of the license agreement, click I accept the terms in the license agreement, then click Next. 7. In the Destination Folder page, select a location to install the components, then click Next. 8. In the Idera SharePoint backup Service Account page, specify the credentials that the Backup Service uses to run, then click Next. 9. In the Service Location page, specify the location of the Management Service that the Backup Service connects to. 10. In the Ready to Install the Program page, click Install. 11. In the Setup Wizard Completed page, click Finish. How do I upgrade the Self-Service Recovery Web Part? When you upgrade SP backup, you can use the Deploy SharePoint Components dialog in the Management Console to upgrade the Self-Service Recovery feature. For information about using the Deploy SharePoint Components dialog to deploy the Self-Service Recovery feature manually, see Manually installing the Self-Service Recovery feature on page 69. What do I do if I upgrade the SharePoint farm from SharePoint 2007 to SharePoint 2010? When you upgrade your SharePoint 2007 farm to SharePoint 2010, you must also make changes to your SP backup deployment. As a general guideline, you should do the following: Disable all schedule backups in SP backup. Let all backups that are in progress complete. Uninstall all copies of the Backup Service from your SharePoint 2007 farm. Upgrade the SharePoint 2007 farm to SharePoint You should follow the best practices for upgrades that Microsoft recommends when you perform the upgrade. Use the SP backup installer to reinstall the Backup Service instances on the WFE hosts and Database hosts in your farm. Enable any scheduled backups in SP backup

50 Configuring Idera SharePoint backup Once you configure Idera SharePoint backup for your environment, you can perform the following tasks: Opening the Idera SharePoint backup Management Console on page 50 Connecting a standalone Management Console to the Management Service on page 51 Configuring Idera SharePoint backup for your farm on page 52 Managing licenses on page 62 Managing the Backup Service on page 64 Specifying Idera SharePoint backup preferences on page 73 Installing the Self-Service Recovery feature on page 55 When the Management Console connects to a particular Management Service, it determines whether you already configured the Management Service. If the Management Service is not yet configured, the Configuration Wizard runs. When you run the Configuration Wizard, you locate the SharePoint Web Front End (WFE) servers and Database Servers in the farm and install the Backup Service on them. You also define the backup locations for the farm. Opening the Idera SharePoint backup Management Console You use the Idera SharePoint backup Management Console to configure SP backup and to back up and restore SharePoint content. When you open the Management Console, it checks for a connection to the SP backup Management Service. If the Management Console cannot connect to the Management Service or if no Management Service is configured, the Management Console prompts you to select the Management Service that it should use. When you install SP backup, you can choose to launch the Management Console when the installer quits. If you are using a trial license or a license that will expire soon, the Management Console warns you that the license will expire. You can contact Idera to purchase an updated license key. How do I open the SP backup Management Console? You use the Windows Start Menu to open the SP backup Management Console. To open the Management Console 1. At the Microsoft Windows desktop, click Start > All Programs > Idera > SharePoint backup > SharePoint backup. 2. If you installed only the Management Console, the Add Farm dialog box appears. You use the Add Farm dialog box to specify the farm and Management Service to which you want the Management Console to connect. To choose the farm and Management Service for a Console-only installation 1. In the Add Farm dialog box, in the Farm name field, specify a name for the new farm. 2. In the Add Farm dialog box, in the Management Service field, specify the name or IP Address of the computer that hosts the Management Service for the farm

51 3. In the Add Farm dialog box, specify the credentials that the Management Console uses to connect to the Management Service. You can click Use current credentials to connect to use the credentials of the logged-in user, or you can click Specify alternate credentials and enter a user name and password to use. 4. In the Add Farm dialog box, click OK. What permissions does the Management Console require? The SP backup Management Console uses the SharePoint and Active Directory permissions of the currently logged in user to back up or restore SharePoint objects. If the currently logged in user is unable to access content, the user is unable to back up or restore that content. Tip: Only users that are members of the SharePoint Farm Administrators group can perform farm backups. Connecting a standalone Management Console to the Management Service When you install the Idera SharePoint backup, you can choose to install the Management Console on a computer with no other components. If you install only the Management Console, you must specify the computer that hosts the Management Service before you can use the Management Console. You can connect more than one Management Console to a single Management Service. If the Management Console is not on the computer that hosts the Management Service, the Management Console prompts you to add a farm the first time you start the SP backup Management Console. When you add the farm, you specify the name of the Management Service host. When it connects to the Management Service, the Management Console prompts you to add a farm if none exists in the SP backup Repository Database. When you specify the name of the Management Service host, you should use one of the following formats: DNS Name NetBIOS Name IP Address If you installed the Management Console and the Management Service on the same computer, the Management Console contacts the local Management Service automatically. How do I open the SP backup Management Console? You use the Windows Start Menu to open the SP backup Management Console. To open the Management Console 1. At the Microsoft Windows desktop, click Start > All Programs > Idera > SharePoint backup > SharePoint backup. 2. If you installed only the Management Console, the Add Farm dialog box appears. You use the Add Farm dialog box to specify the farm and Management Service to connect to

52 To choose the farm and Management Service for a Console-only installation 1. In the Add Farm dialog box, in the Farm name field, specify a name for the new farm. 2. In the Add Farm dialog box, in the Management Service field, specify the name or IP Address of the computer that hosts the Management Service for the farm. 3. In the Add Farm dialog box, specify the credentials that the Management Console uses to connect to the Management Service. You can click Use current credentials to connect to use the credentials of the logged-in user, or you can click Specify alternate credentials and enter a user name and password to use. 4. In the Add Farm dialog box, click OK. Configuring Idera SharePoint backup for your farm If the Management Console and Management Service are hosted on the same computer, the first time you open the Idera SharePoint backup Management Console, the Welcome to Idera SharePoint backup window appears. If you use a standalone Management Console, the first time you open the SP backup Management Console, the Add Farm dialog box appears. The Add Farm dialog box lets you add a new farm and specify the Management Service to use. If the farm that you specify is not yet configured, the Welcome to Idera SharePoint backup window appears. The Welcome window lets you configure SP backup. When you start using SP backup, you must do the following: Connect SP backup to the SharePoint farm. Install one or more Backup Service instances. Optionally deploy the Self-Service Restore feature. Configure SP backup licenses. Configure the SP backup settings. Set up alerts and notifications. Configure grooming and fault tolerance settings. You use the Configure Idera SharePoint backup Wizard to perform all of these tasks. You can also use the Configuration Wizard to discover your SharePoint farm, select a Web Front End (WFE) server to host the Backup Service, and specify the Backup Service preferences. When you start the Management Console, it connects to the Management Service and determines if the Management Service is properly configured. If it is not configured, the Management Console starts the Configuration Wizard. Specifying the Central Administration settings You use the Configuration Wizard to specify how Idera SharePoint backup connects to the farm that you want to back up. You use the Central Administration page in the wizard to specify the Central Administration page URL for the farm. You also specify the credentials that SP backup uses to connect to the farm. How do I specify the URL and the account to use? You use the Central Administration page of the Configuration Wizard to specify the SharePoint

53 Site URL and the account to use. To specify the SharePoint Site URL and account 1. In the Central Administration page of the Configuration Wizard, enter the URL of the Central Administration site for the SharePoint farm in the Central Administration URL field. 2. Type the name and password of the account that SP backup should use to connect to the Management Service for the farm in the User Name and Password fields. 3. Click Next. 4. In the Web application use policy modification required dialog box, click OK. What permissions does the specified account require? The specified account needs the following permissions: Must be a member of the Share Point Farm Administrators group. Must be a local administrator on the computer that hosts the Backup Service. Must have at least db_owner permissions for all SharePoint content databases, including the Admin Content and SharePoint Config databases You can also use the tab to specify a separate account with the required SharePoint permissions. This ability to specify two accounts gives you the ability to specify the accounts with the needed permissions and work within your security model so you do not need a single account with all the required permissions. Tip: If the account that you use is not a SQL Server System Administrator, you should use the SQL Server Management Studio to grant the account access to the Repository Database that you specified when you installed SP backup. The default database name is IderaSPBackupRepository. Selecting the WFE servers where you want to install the Backup Service The WFE Servers page of the Configuration Wizard lists the Web Front End (WFE) servers in your SharePoint farm. If your SharePoint farm includes one or more separate Database servers, the Database Servers page lists the database servers. Idera SharePoint backup uses the Backup Service instances that you install to back up the Share- Point objects that you specify in the farm. If your disaster recovery planning only includes granular backups, SP backup uses the SharePoint object model to access the objects that you back up. When you perform granular backups, the Backup Service is only required on a single WFE. Additional Backup Service copies help you to ensure fault tolerance and to balance backup loads for Granular Backups. You should generally install the Backup Service on every WFE in your farm. If your disaster recovery planning includes farm backups of SharePoint 2010 farms, you must install the Backup Service on every WFE and every Database Server in your SharePoint farm. When you use the Configuration Wizard, you must install the Backup Service on at least one WFE. Tip: The first Backup Service that you install must always be on a WFE server

54 You should normally use the Configuration Wizard to install the Backup Service on every WFE and every Database Server in your SharePoint farm. You can use the Database Servers page to install the Backup Service on standalone Database Servers in your SharePoint farm. For information about the Database Servers page, see Selecting the database servers where you want to install the Backup Service on page 54. You can also use the SP backup Management Console to install the Backup Service on WFE hosts in the SharePoint farm. In addition, if you add a WFE or a Database Server to your farm, you can use the Management Console to install the Backup Service on the new server. Finally, you can use the SP backup installer to install the Backup Service on the WFE or Database Server directly. To do so, you must be able to log in to the server with an account that is a member of the Administrators group on the server. For information about installing the Backup Service, see Installing the Backup Service manually on page 43. When you install a Backup Service, you select the WFE server to install on. You also specify the user name and password that the Backup Service uses to run. The user account that you specify must have specific permissions for the farm. For information about the permissions that the Backup Service user account requires, see Learning about the Backup Service requirements on page 35. The SharePoint Services Web Application Service must be operating on the WFE where you install the Backup Service. If the server does not have the Web Application Service active, you can use the SharePoint Central Administration page to install it. In the WFE Servers page of the Configuration Wizard, review the selected servers, then click Next. Can I manually install additional Backup Service instances? Normally, you should not need to manually install additional servers. The WFE Servers page lets you install on every WFE Server in the farm. If you add a WFE or a Database Server, you can manually install an additional Backup Service in the Configuration tab in the SP backup Management Console. For information about installing the Backup Service manually, see Installing the Backup Service manually on page 43. Selecting the database servers where you want to install the Backup Service The Database Servers page of the Configuration Wizard lists the standalone Database Servers in your SharePoint farm. A standalone Database Server hosts one or more SharePoint database components, but does not host a Web Front End (WFE). Idera SharePoint backup uses the Backup Service instances that you install to back up the Share- Point objects that you specify in the farm. If your disaster recovery planning only includes granular backups, SP backup uses the SharePoint object model to access the objects that you back up. When you perform granular

55 backups, the Backup Service is only required on a single WFE. Additional Backup Service copies help you to ensure fault tolerance and to balance backup loads for Granular Backups. You should generally install the Backup Service on every WFE in your farm. If your disaster recovery planning includes farm backups of SharePoint 2010 farms, you must install the Backup Service on every WFE and every Database Server in your SharePoint farm. When you use the Configuration Wizard, you can install the Backup Service on any Database Servers in the farm. Tip: The Database Servers page only appears if your farm includes one or more Database Servers that do not also host a WFE. You should normally use the Configuration Wizard to install the Backup Service on every Database Server in your SharePoint farm. You can also use the SP backup Management Console to install the Backup Service on WFE hosts in the SharePoint farm. In addition, if you add a WFE or a Database Server to your farm, you can use the Management Console to install the Backup Service on the new server. Finally, you can use the SP backup installer to install the Backup Service on the WFE or Database Server directly. To do so, you must be able to log in to the server with an account that is a member of the Administrators group on the server. For information about installing the Backup Service, see Installing the Backup Service manually on page 43. When you install a Backup Service, you select the Database Server to install on. You also specify the user name and password that the Backup Service uses to run. The user account that you specify must have specific permissions for the farm. For information on the permissions that the Backup Service user account requires, see Learning about the Backup Service requirements on page 35. In the Database Servers page of the Configuration Wizard, review the selected servers, then click Next. Can I manually install additional Backup Service instances? Normally, you should not need to manually install additional servers. The Database Servers panel let you install on every Database Server in the farm. If you add a Database Server, you can manually install an additional Backup Service in the Configuration tab in the SP backup Management Console. For information on installing the Backup Service manually, see Installing the Backup Service manually on page 43. Installing the Self-Service Recovery feature The Idera SharePoint backup Self-Service Recovery feature lets your SharePoint users help themselves. With the Self-Service Recovery feature installed, SharePoint Site Collection Administrators and users they delegate the permission to can download to their hard disk the specific

56 library items that SP backup has backed up as part of a Granular Backup. Only authorized users can see backed up content and download it to their hard disk. The user must currently have adequate SharePoint permissions to access the object. In addition, the user must have had adequate SharePoint permissions to access the object when it was backed up. Authorized users can only use the self-service recovery tool to download content from a Granular Backup. Users cannot download content from a Farm Backup. Only the SP backup Management Console can restore content in place from a Granular Backup or restore any content from a Farm Backup. Only members of the Farm Administrators group can use the Management Console to restore content from a Farm Backup. When you install the Self-Service Recovery feature, SP backup does the following automatically: Copy the Self-Service Recovery SharePoint Solution package (.WSP file) to the SharePoint Farm Solution store. Deploy the solution to the Web Application that is the parent of any Site Collections that you specify. Activate the deployed solution as a SharePoint Feature on the Site Collections. For information about using Self-Service Recovery, see Using the Self-Service Recovery feature in the SP backup help. The Self-Service Recovery feature is optional. You do not have to install it to use SP backup. You should deploy the Self-Service Recovery feature on every Site Collection where you want to use it. You can use the SharePoint Components page in the Configuration Wizard to select the Site Collections where you want to let users access the Self-Service Recovery feature. If you want to deploy the Self-Service Recovery feature, in the SharePoint Components page, you can select the Deploy the Idera SharePoint backup Self-Service Recovery solution check box, then select the check boxes for the Site Collections and Sites where you want to deploy Self- Service Recovery. If you do not want to deploy the Self-Service Recovery feature, in the SharePoint Components page, you can clear the Deploy the Idera SharePoint backup Self-Service Recovery solution check box. After you deploy the Self-Service Recovery feature, you can configure the Self-Service Recovery settings in each Site Collection where you want to use it. If you need to, you can click Modify Self-Service Recovery preferences to configure the Self- Service Recovery settings. For information about the Self-Service Recovery settings, see Configuring the Self-Service Recovery settings on page 70. When you have configured the settings, you can click Next to continue. How do I upgrade the Self-Service Recovery feature? When you upgrade SP backup, you can use the Deploy SharePoint Components dialog in the Management Console to upgrade the Self-Service Recovery feature. For information about using the Deploy SharePoint Components dialog to deploy the Self-Service Recovery feature manually, see Manually installing the Self-Service Recovery feature on page

57 Configuring the SharePoint backup licenses Idera SharePoint backup is a licensed product. It requires a license key to use. SP backup includes a limited-time license key that lets you get started using it immediately. If you do not yet have a license key, you can start using SP backup with the included trial license key You can later purchase a license key from Idera and use the Manage License dialog to install the key. For information about managing licenses, see Managing licenses on page 62. If you already have a license key, you can use the Manage Licenses page of the Configuration Wizard to add the key. In the Manage Licenses page of the Configuration Wizard, you can click Add, then type or paste the key in the Add License Keys dialog. When you are ready to continue, click Next. Specifying the Backup Service preferences for a new farm The Preferences page of the Configuration Wizard lets you specify the Backup Service options. You can specify the following items: Where to store your backed up content The service account that each Backup Service uses on each host. The number of simultaneous threads that each Backup Service uses when performing a Granular Backup. The timeout value that a Backup Service uses when it connects to the Management Service. The port that the Management Service uses to communicate with the Backup Service on each host. The debug logging setting. To make changes to the preferences for an existing farm, you use the Idera SharePoint backup Preferences dialog box. For information about changing preferences for an existing farm, see Defining the Backup Service preferences on page 73. You can back up content from your SharePoint farms to a network location that you specify with a UNC path. You can also back up content to a Tivoli Storage Manager (TSM) client node. You must set up a TSM virtual server client node before you can back up to a TSM client node. For information about using TSM with SP backup, see Learning about Tivoli Storage Manager on page 32. Tip: If you remove a backup location that SP backup uses to store data in TSM, removing the location removes references to the data in SP backup. In addition, SP backup sets the data objects to Inactive in TSM. SP backup does not automatically delete the data itself. If you need to delete the data from TSM, you should use the TSM management tools to do so

58 For more information about using TSM, see Learning about Tivoli Storage Manager on page 32. You can specify how many simultaneous execution threads that each Backup Service uses when SP backup performs a Granular Backup. The maximum number of threads is 32. Most environments will use fewer threads. When you configure the number of threads, you must balance the backup performance with the performance of the farm as a whole. Determining the number of threads appropriate for your environment requires experiments to determine the best mix for your specific needs. For more information about configuring the number of threads, see Defining the Backup Service preferences on page 73. When you specify the timeout value, you determine how long a Backup Service should wait for the Management Service to respond when it tries to connect. When the time that you specify expires, the Backup Service stops trying to connect and logs an error. You specify the timeout in seconds. The SP backup Management Service uses the port that you specify to communicate with each Backup Service that you install. You should make sure that the firewall settings on your network allow the Management Service to reach every Backup Service that you install. The Backup Service normally logs its actions. You can control the level of detail that the Backup Service uses in logging. When you enable debug logging, the Backup Service creates debug logs in addition to regular logging. The additional detail in these logs can assist Idera Technical Support. If a problem occurs, you can use the Management Console to send the Backup Service log files to Idera Technical Support. The maximum size of a debug log is 4 MB. When the log file reaches this maximum, SP backup automatically stores the log. SP backup keeps the active log and one stored log. This means that the maximum log size on any Backup Service host is 8 MB. How do I choose where to store backed up content? You use the Preferences page of the Configuration Wizard to choose a backup location and to select the default service account. To add a backup location 1. In the Preferences page of the Configuration Wizard, click Add. 2. In the Change Backup Location dialog box, enter a name for the backup location. 3. In the Change Backup Location dialog box, do one of the following: If you want to use a network volume to store backed up information from SharePoint, select Network Location (UNC Path) from the Select the type of backup set location drop-down list, then type the UNC path of the location in the Enter the UNC path of the network location field. If you want to use a Tivoli Storage Manager (TSM) virtual client node to store backed up information from SharePoint, select Tivoli Storage Manager (TSM) from the Select the type of backup set location drop-down list, then specify the client node SP backup should use in the Enter the name of the TSM target client node field 4. If the new location should be the default location for backup sets, select the Set as the

59 default backup set location check box. 5. Click OK. To edit a backup location 1. In the Preferences page of the Configuration Wizard, click the backup set to edit, then click Edit. 2. In the Change Backup Location dialog box, enter a name for the backup location. 3. In the Change Backup Location dialog box, do one of the following: If you want to use a network volume to store backed up information from SharePoint, select Network Location (UNC Path) from the Select the type of backup set location drop-down list, then type the UNC path of the location in the Enter the UNC path of the network location field. If you want to use a Tivoli Storage Manager (TSM) virtual client node to store backed up information from SharePoint, select Tivoli Storage Manager (TSM) from the Select the type of backup set location drop-down list, then specify the client node SP backup should use in the Enter the name of the TSM target client node field 4. If the location is not the default location for backup sets and you want it to be the default, select the Set as the default backup set location check box. 5. Click OK. To set a backup location as the default 1. In the Preferences page of the Configuration Wizard, click the backup set to set as the default. 2. Click Set as default. To remove a backup location 1. In the Preferences page of the Configuration Wizard, click the backup set to remove. 2. Click Remove. 3. SP backup prompts you to confirm that you want to remove the backup location. If you remove the backup location, any sets stored in that location are not deleted. You must manually delete the sets. Click Yes to remove the backup location. How do I set the default service account? You use the Preferences page in the Configuration Wizard to set the default account that the Backup Service uses. To set the default service account In the Preferences page of the Configuration Wizard, in the Deployment area, enter the default account for SP backup to use when for new Backup Service instances. You should enter the account in <domain name>\<account name> format. How do I configure the number of threads that granular backups use? You use the Preferences page in the Configuration Wizard to set the number of threads that granular backups use. The maximum allowable number of threads is 32. Most environments will use fewer threads

60 To set the number of threads used by granular backups In the Preferences page of the Configuration Wizard, in the Granular Backup Threads area, enter the number of threads that SP backup should use when performing granular backups. You can type the number in the field or use the up and down buttons in the threads field to change the number. How do I configure the Backup Service timeout value? You use the Preferences page in the Configuration Wizard to set the Backup Service timeout value. The timeout value is in seconds. To set the Backup Service timeout value In the Preferences page of the Configuration Wizard, in the Timeouts area, enter the length of time that SP backup should wait for successful communications. You can type the number of seconds in the field or use the up and down buttons in the threads field to change the number of seconds. How do I configure the port that the Management Service uses to communicate with the Backup Service? You use the Preferences page in the Configuration Wizard to set the port that the Management Service uses to communicate with the Backup Service. To configure the port that the Management Service uses to communicate with the Backup Service? In the Preferences page of the Configuration Wizard, in the Ports area, enter the port that the Management Service uses to communicate with the Backup Service. You can type the number in the field or use the up and down buttons in the threads field to change the number. How do I configure debug logging? You use the Preferences page in the Configuration Wizard to enable and disable debug logging. To configure debug logging In the Preferences page of the Configuration Wizard, in the Debug logging area, select or clear the Enable debug logging checkbox. What should I consider when I specify where to store backup sets? Make sure the Backup Service account has write permission to the specified share and file location. In addition, make sure there is enough disk space available to store the backup sets and the network performance is optimal between the Backup Service instances and the backup set storage location. You can review the Today page in the Management Console for disk space usage and availability. As needed, you can archive backup sets to make more disk space available. Later, if you need to restore objects from an archived backup set, you can import the archived backup set and then restore the objects. For more information, see Managing Backup Set Disk Space

61 What permissions does the service account for the Backup Service require? The specified account needs the following permissions: Must be a member of the Share Point Farm Administrators group. Must be a local administrator on the computer that hosts the Backup Service. Must have at least db_owner permissions for all SharePoint content databases, including the Admin Content and SharePoint Config databases Configuring the alert settings Idera SharePoint backup generates an alert when a specified condition occurs. When SP backup generates the alert, it can send an to one or more addresses that you specify, log the alert, or both. You can use the Alerts page in the Configuration Wizard to choose the conditions that trigger an alert. When you have configured the alerts, you can click Next to continue in the wizard. For information about the conditions that can trigger an alert, see Learning about alerts on page 81. Configuring the alert notification settings When Idera SharePoint backup generates an alert, it can log the alert notification to the Application Event Log on the computer that hosts the Management Service, send an to one or more addresses that you specify, or both. You can use the Alert Notifications page in the Configuration Wizard to set up the Alert Notifications. When you have configured the settings, click Next to continue. For information about the Alert Notification settings, see Managing the alert notification settings on page 85. Configuring the grooming settings If you choose, Idera SharePoint backup can groom older alerts and backup sets automatically to conserve storage space. When it grooms data, SP backup automatically removes the old data from the backup location or the alert log. You can use the Grooming tab in the Configuration Wizard to set up the Grooming options. After you set the options, you can click Next to continue. For information about the backup set grooming options, see Learning about data grooming on page 31. For information about the alert grooming options, see Configuring alert grooming on page 87. Configuring the fault tolerance settings Idera SharePoint backup includes built-in fault tolerance that lets it continue performing Granular Backup and Restore operations on the data in your SharePoint farm if a Backup Service fails. If the Management Service is unable to contact the primary Backup Service when it performs a backup or restore operation, it can assign the job to a secondary Backup Service installed on a Web Front End (WFE) in the same farm. You can use the Fault Tolerance page in the Configuration Wizard to set the Fault Tolerance options for your farm. You can use the Set as Primary, Move Up, and Move Down buttons in the

62 Backup Services area to specify the order that the Management Service uses when it assigns jobs to a Backup Service. When you are satisfied with the Backup Service order, click Next to continue. For information about Fault Tolerance, see Configuring fault tolerance on page 68. Managing licenses Idera SharePoint backup is a licensed product. It requires a license key to use. SP backup includes a limited-time license key that lets you get started using it immediately. As the end of the trial period nears, SP backup warns you each time that you start the Management Console that the trial period ends soon. At the end of the trial period, SP backup no longer functions if you have not upgraded your license. The Manage Licenses dialog box lets you view the status of your license keys. You can also add license keys as needed. If you are using a trial license, upgrading to a full license lets you get the most from SP backup. You can also use the Manage Licenses dialog box to send an to Idera for information about purchasing additional licenses. Why might I need more than one license key? Each Web Front End (WFE) in your SharePoint farm requires a SP backup license. In addition, you have a separate license for Granular Backups and Farm Backups. When you perform Farm Backups, every server in the SharePoint farm that you back up must have a Farm Backup license. You could start with one license type, then add the other as your needs change. How do I open the Manage Licenses dialog box? You use the SP backup Management Console to open the Manage Licenses dialog box. To open the Manage Licenses dialog box In the SP backup Management Console, click Tools > License Key Manager. How do I add a license key? You use the Manage Licenses dialog box to add licenses. To add a license key 1. In the Manage Licenses dialog box, select the farm from the Farm drop-down list. 2. In the Manage Licenses dialog box, click Add. 3. In the Add License Keys dialog box, enter the license key to add. You can enter multiple license keys at the same time. Each license key must be on a separate line. 4. Click OK to close the dialog box and save the licenses. How do I remove a license key? You use the Manage Licenses dialog box to remove licenses. To remove a license key 1. In the Manage Licenses dialog box, select the farm from the Farm drop-down list. 2. In the Manage Licenses dialog box, click Remove

63 3. SP backup prompts you to confirm that you want to remove the license. Click Yes to remove the license and close the dialog box. How do I save a license key to a file? You use the License Key Manager to export licenses. When you export the license, you save it to a CSV file that you can add to your backup routine. To save a license key to a file 1. In the Manage Licenses dialog box, select the farm from the Farm drop-down list. 2. In the Manage Licenses dialog box, click the license key to save. 3. Click Save to File. 4. In the Save License(s) Information dialog box, specify a name and location for the file, then click Save. 5. In the Information dialog box, click OK. How do I contact Idera Sales for information about additional licenses? You can use the License Key Manager to send an to Idera Sales for information about purchasing an additional license. To contact Idera Sales 1. In the Manage Licenses dialog box, click Send to Idera Sales. 2. In the Send to Idera Sales dialog box, you can copy or make changes to the address, subject, or message. 3. In the Send to Idera Sales dialog box, click Send to send the you created to Idera. Adding new license keys To manage additional SharePoint servers beyond the limits of your existing license, contact Idera Sales to purchase additional licenses. You add the license key to Idera SharePoint backup to use the new license. How do I open the Add License Keys window? You use the Add License Keys window to add license keys. To open the Add License Keys window 1. In the SP backup On the Tools menu, click License Key Manager. 2. Click Add. How do I add a license key? The Add License Keys window lets you add new license key values, You can copy the license key value from the licensing , and then paste it into the Add License Key window. You can also add multiple license keys at one time. Specify one license key value on each line. To add a license key 1. In the License Key Window, type the new license key value. 2. Click OK

64 Managing the Backup Service The Idera SharePoint backup Backup Service performs backup and restore operations when directed to do so by the Management Service. The following sections describe tasks you may need to manage a Backup Service: Installing the Backup Service manually on page 43 Starting the Backup Service on page 64 Stopping the Backup Service on page 64 Starting the Backup Service The Start Backup Service dialog box lets you start a stopped Idera SharePoint backup Backup Service on the selected Web Front End (WFE) server or Database Server. The Backup Service must already be installed on the server. How do I start a Backup Service? You use the Start Backup Service dialog box to start a stopped Backup Service. To start a stopped Backup Service 1. In the SP backup Management Console, in the left pane, click Configuration. 2. In the Configuration pane, click the server where you want to start the Backup Service. 3. In the right pane, click Start Backup Service. 4. In the Start Backup Service dialog box, enter the user name and password to use to start the service. 5. Click Start. 6. In the Information dialog box, click OK. What permissions does the account that you use to start the Backup Service require? The account that you specify when you start the Backup Service needs the following permissions: Must be a member of the Share Point Farm Administrators group. Must be a local administrator on the computer that hosts the Backup Service. Stopping the Backup Service The Stop Backup Service dialog box lets you stop a running Idera SharePoint backup Backup Service on the selected Web Front End (WFE) server or Database Server. Specify a user name and password to use to stop the Backup Service, and then click Stop. Idera SharePoint backup attempts to stop the Backup Service running on the selected server. How do I stop a Backup Service? You use the Stop Backup Service dialog box to stop a Backup Service. To stop a Backup Service 1. In the SP backup Management Console, in the left pane, click Configuration. 2. In the Configuration pane, click the server where you want to start the Backup Service

65 3. In the right pane, click Stop Backup Service. 4. In the Stop Backup Service dialog box, enter the user name and password to use to stop the service. 5. Click Stop. 6. In the Information dialog box, click OK. What permissions does the account that you use to stop the Backup Service require? The account that you specify when you stop the Backup Service needs the following permissions: Must be a member of the Share Point Farm Administrators group. Must be a local administrator on the computer that hosts the Backup Service. Managing farms You use Idera SharePoint backup to back up your SharePoint 2010 farms and objects in your Share- Point 2007 farms and SharePoint 2010 farms. The SP backup Management Console can connect to and back up multiple SharePoint farms. The farms can be a mixture of SharePoint 2007 and SharePoint 2010 farms. You must add any farm that you want to back up to the Management Console. You can also remove farms that are no longer needed. See the following for additional information: Monitoring multiple farms on page 65 Adding a farm on page 66 Editing a farm on page 67 Removing a farm on page 67 Monitoring multiple farms You can use the Idera SharePoint backup Management Console to monitor and back up multiple SharePoint farms at the same time. Every farm that you monitor and back up must have a SP backup Management Service. Each Management Service has a unique Repository Database. Every farm that you monitor and back up must have at least one Backup Service. Tip: If your disaster recovery planning includes farm backups of SharePoint 2010 farms, every Web Front End (WFE) and every Database Server in the farm must have the Backup Service installed. In addition, all of the SharePoint farms that you monitor must be in the same domain or must be in a trusted domain. When you add a farm, you supply credentials to connect to the Management Service for the farm. If the farm has one or more installed Backup Service instances, you also connect to the Backup Service. If the farm does not have an installed Backup Service, you can use the Configuration Wizard to install one or more Backup Service instances. See Configuring Idera SharePoint backup for your farm on page 52. If you perform a Granular Backup, the credentials that you supply must have one or more of the following privileges:

66 Site Collection Administrator. Full Control via Web Application Policy. Farm Administrator. If the credentials that you supply do not have appropriate permissions, the Site Collection is dimmed in the Management Console. When the Site Collection is dimmed, it indicates that the Management Console is unable to perform any backup or restore operations for the Site Collection. You can edit the farm to supply alternate credentials. If you perform a Full Backup, the credentials that you supply must be a member of the Farm Administrators group. Only Farm Administrators can perform Farm Backups. How do I add a farm to the SP backup Management Console? You use the Add Farm dialog box in the Management Console to add a farm. If the farm that you add does not have any installed Backup Service instances, you can use the Configuration Wizard to configure the farm and install one or more Backup Service instances. See Configuring Idera SharePoint backup for your farm on page 52. To add a farm to the Management Console 1. Use the SP backup installer to install all of the SP backup components in the farm. The components include the Management Service and Backup Service. The installation also includes the SP backup Management Console. 2. On the computer that you want to add the farm to, in the SP backup Management Console, in the toolbar, click Add Farm. 3. In the Add Farm dialog box, enter a name for the new farm. The name you enter appears in the Management Console and is for your reference. You should also enter the DNS Name, NetBIOS Name, or IP Address of the computer that hosts the Management Service for the new farm. 4. Specify the credentials that the Management Console uses to contact the new farm. 5. Click OK. Adding a farm You can add any SharePoint farm to the Idera SharePoint backup Management Console. You must add a farm to back up the farm or the SharePoint objects that it contains. How do I add a farm? Use the Add Farm dialog box to add a farm to the SP backup Management Console. If the farm that you add does not include an installed Backup Service, use the Configuration Wizard to configure the farm and install one or more copies of the Backup Service. See Configuring Idera Share- Point backup for your farm on page 52. To add a farm 1. In SP backup Management Console, click File > Add Farm. As a shortcut, you can click the Add Farm button in the Management Console toolbar. 2. In the Add Farm dialog box, enter a name for the new farm in the Farm name field. The name is for your reference in the Management Console. You can enter any name that you choose. The name does not need to match the name of the farm in SharePoint

67 3. In the Add Farm dialog box, enter the name of the computer that hosts the Management Service in the Management Service field. 4. Click Use current credentials to connect or click Specify alternate credentials and enter the credentials that SP backup uses to connect to the SP backup Management Service. 5. Click OK. SP backup displays the Configuration Wizard if this is the first time that the Management Console connected to the farm. For more information about configuration, see Configuring Idera SharePoint backup for your farm on page 52. Editing a farm You can make changes to any SharePoint farm that you have added to the Idera SharePoint backup Management Console. You can change the name of the farm, the computer that hosts the Management Service, or the credentials that you use to connect to the farm. How do I edit a farm? You use the Edit Farm dialog box to make changes to a farm in the SP backup Management Console. To edit a farm 1. In the SP backup Management Service, do one of the following: Click File > Edit Farm. In the left pane, click Farm Backup, Granular Backup, or Configuration, then right-click any element and click Edit Farm. 2. In the Edit Farm dialog box, make any needed changes to the farm settings. 3. Click OK. Removing a farm You can delete any unused SharePoint farm from the Idera SharePoint backup Management Console. You cannot back up from or restore to a farm after you remove it. How do I remove a farm? You use the Remove Farm dialog box to remove a farm from the SP backup Management Console. To remove a farm 1. In the SP backup Management Console, do one of the following: Click the name of the farm that you want to delete, then click File > Remove Farm. In the left pane, click Farm Backup, then click SharePoint 2010 Farms. In the Farm Backup Today page, click Remove Farm. Click the name of the farm that you want to delete, then in the left pane, click Farm Backup, then right-click the farm that you want to delete, and click Remove Farm

68 In the left pane, click Granular Backup, then click SharePoint 2010 Farms or SharePoint 2007 Farms. In the Granular Backup Today page, click Remove Farm. In the left pane, click Granular Backup, then right-click the farm that you want to delete, and click Remove Farm. In the left pane, click Farm Backup, Granular Backup, or Configuration, then right-click any element and click Remove Farm. 2. In the Warning dialog box, click Yes to remove the farm. Configuring fault tolerance When you add a farm to the Idera SharePoint backup Management Console, you install the Idera SharePoint Backup Service on the SharePoint servers that make up your SharePoint farm. You can also install the Backup Service on SharePoint servers manually. For information about installing the Backup Service, see Installing the Backup Service manually on page 43. If the Management Service is unable to contact the primary Backup Service when it performs a backup or restore operation, it can assign the job to a secondary Backup Service installed on a Web Front End (WFE) in the same farm. When the Management Service assigns a job to a Backup Service, it checks Backup Service availability in the same order used for Fault Tolerance. If the first Backup Service in the Fault Tolerance list is busy, the Management Service tries the next, and so on until it locates an available Backup Service. If all of the Backup Service instances are busy, the Management Service waits for the first available Backup Service. For information about load balancing, see Understanding load balancing on page 80. Tip: Fault Tolerance only applies to Granular Backups. Farm Backups are always processed by the Backup Service installed on the server. How can I select the failover order for the Backup Service instances installed on a single SharePoint farm? You use the Configuration pane in the SP backup Management Console to control the failover order for the Backup Service instances installed on the WFEs in a single SharePoint farm. To change the failover order for a farm 1. In the SP backup Management Console, in the left pane, click Configuration. 2. In the Configuration pane, do one of the following: Click the name of the farm whose fault tolerance settings you want to change. Click the name of a server in the farm whose fault tolerance settings you want to change. Click SharePoint 2010 Farms or SharePoint 2007 Farms, then click the name of the farm whose fault tolerance settings you want to change. 3. In the right pane, in the ribbon, click Fault Tolerance

69 4. In the Backup Services field, review the failover order for the Backup Service instances. Click a Backup Service, then click Move Up or Move Down to change the failover order. Click Set as Primary to designate that Backup Service as the primary service for the farm. When you set a service as primary, it moves to the first place in the list of Backup Service instances. Managing self-service recovery The Idera SharePoint backup Self-Service Recovery feature lets SharePoint Site Collection Administrators and other users download SharePoint library items from a SP backup to their hard disk. Before you can use the Self-Service Recovery feature, the SP backup administrator must install it and configure the options. After the feature is installed, the Site Collection Administrator of each Site Collection where the feature is enabled can download backed-up library item files. The Site Collection Administrator can also delegate authority to individual users to download files. Delegated users can download files from the backup sets that SP backup creates if both their current permissions for the files and their permissions at the time of the backup allow them to view the files. You may need to do the following to manage Self-Service Recovery: Manually installing the Self-Service Recovery feature on page 69 Delegating permission for Self-Service Recovery on page 72 Manually installing the Self-Service Recovery feature The Idera SharePoint backup Self-Service Recovery feature lets your SharePoint users help themselves. With the Self-Service Recovery feature installed, SharePoint Site Collection Administrators and users they delegate the permission to can download to their hard disk the specific library items that SP backup has backed up as part of a Granular Backup. Only authorized users can see backed up content and download it to their hard disk. The user must currently have adequate SharePoint permissions to access the library item. In addition, the user must have had adequate SharePoint permissions to access the item when it was backed up. Authorized users can only use the self-service recovery tool to download content from a Granular Backup. Users cannot download content from a Farm Backup. Only the SP backup Management Console can restore content in place from a Granular Backup or restore any content from a Farm Backup. Only members of the Farm Administrators group can use the Management Console to restore content from a Farm Backup. When you install the Self-Service Recovery feature, SP backup does the following automatically: Copy the Self-Service Recovery SharePoint Solution package (.WSP file) to the SharePoint Farm Solution store. Deploy the solution to the Web Application that is the parent of any Site Collections that you specify. Activate the deployed solution as a SharePoint Feature on the Site Collections. For information about using Self-Service Recovery, see Using the Self-Service Recovery feature in the SP backup help

70 The Self-Service Recovery feature is optional. You do not have to install it to use SP backup. You should deploy the Self-Service Recovery feature on every Site Collection where you want to use it. If you need to, you can configure the Self-Service Recovery settings. For information about the Self-Service Recovery settings, see Configuring the Self-Service Recovery settings on page 70. You can use the Configuration Wizard to deploy the Self-Service Recovery feature. You can also use the Configuration tab in the Management Console to manually install, repair, or update the Self- Service Recovery feature. How do I manually install, repair, or uninstall the Self-Service Recovery feature? You use the Configuration pane in the Management Console manually install, repair, and uninstall the Self-Service Recovery feature. To manually install the Self-Service Recovery feature 1. In the SP backup Management Console, click Configuration. 2. In the Configuration pane, click Deploy SharePoint Components. 3. In the Deploy SharePoint Components dialog box, select the Deploy the Idera Share- Point backup Self-Service Recovery solution checkbox, then select the checkboxes for the Site Collections and Sites where you want to enable the Self-Service Recovery feature. 4. In the Deploy SharePoint Components dialog box, click Deploy. To repair the Self-Service Recovery feature 1. In the SP backup Management Console, click Configuration. 2. In the Configuration pane, click Deploy SharePoint Components. 3. In the Deploy SharePoint Components dialog box, select the Repair the Self-Service Recovery solution option. 4. In the Deploy SharePoint Components dialog box, click Update. To uninstall the Self-Service Recovery feature 1. In the SP backup Management Console, click Configuration. 2. In the Configuration pane, click Deploy SharePoint Components. 3. In the Deploy SharePoint Components dialog box, select the Remove the Self-Service Recovery solution option. 4. In the Deploy SharePoint Components dialog box, click Update. How do I upgrade the Self-Service Recovery feature? You can use the Deploy SharePoint Components dialog to upgrade the Self-Service Recovery feature. When you install or repair the Self-Service Recovery feature, Self-Service Recovery components are updated automatically. Configuring the Self-Service Recovery settings You can use the Idera SharePoint backup Management Console to configure the settings for the Self-Service Recovery feature. You can configure the following settings: Management You can specify the name of the Management Service host that the

71 Service Host name Management Service Port Number of items that appear when you browse backed-up content. Number of items that appear when you search for content. The ULS logging level that Self-Service Recovery uses. Self-Service Recovery feature should access. If you change the Management Service host name, the Self-Service Recovery feature uses backups from that SP backup deployment. If that SP backup does not backup the site collection, no content appears in the Self-Service Recovery feature in the site collection. When you specify the Management Service Host name, you can use any of the following formats: Machine name Fully-qualified name IP Address The port that the Self-Service Recovery feature should use to contact the Management Service. You should ensure that your network configuration allows the Self-Service Recovery to use this port to access the Management Service. If you change the Management Service Port here, you must also change the Management Service Port on the Management Service. You can specify how many items appear in the Self-Service Recovery feature when you browse the backed-up content. The more items that appear in the list, the longer it takes SharePoint to display the page. You can specify how many items appear in the Self-Service Recovery feature when you search for backed-up content. The more items that appear in the list, the longer it takes SharePoint to display the page. When it encounters an error, the Self-Service Recovery feature logs the error to the SharePoint Unified Logging System (ULS) logs. You can specify the level of the content added to the ULS logs. You can select one of the following log levels: Undefined Exception Critical Warning Informational When you select a level, items of that level and more serious are added to the ULS logs. How do I configure the Self-Service Recovery settings? You use the Self-Service Recovery Settings dialog box in the Management Console to configure

72 the Self-Service Recovery settings. You can configure the settings when you deploy the Self-Service Recovery feature or at a later time. To configure the Self-Service Recovery settings in the Configuration Wizard 1. When you use the Idera SharePoint backup Configuration Wizard, the SharePoint Components page lets you deploy the Self-Service Recovery feature. In the SharePoint Components page, click Modify Self-Service Recovery preferences. 2. In the Self-Service Recovery Settings dialog box, configure the settings, then click Save. 3. In the Configuration Wizard, in the SharePoint Components page, click Next to continue the wizard. To configure the Self-Service Recovery settings 1. In the SP backup Management Console, click Configuration. 2. In the Configuration tab, click Deploy SharePoint Components. 3. In the Deploy SharePoint Components dialog box, click Modify Self-Service Recovery preferences. 4. In the Self-Service Recovery Settings dialog box, configure the settings, then click Save. 5. In the Deploy SharePoint Components dialog box, click Cancel. 6. In the Configuration Wizard, in the SharePoint Components page, click Next to continue the wizard. Delegating permission for Self-Service Recovery The Idera SharePoint backup Self-Service Recovery feature lets authorized users download content from backup sets. Site Collection Administrators can always use the Self-Service Recovery feature to download content from backup sets. Members of the Site Collection Administrators group can view and download any files that SP backup has backed up in the current Site Collection. Site Collection Administrators can also delegate permission to download backed-up content to specific users. The content that delegated users can see and download depends on the following: The current permissions that the user has for the content. The permissions the user had at the time the backup was created. To view the contents of a site or a library, the user must either have current access to the site or library, or the user must have had access at the time that the content was backed up. To download a backed-up file, the user must have current access and also access at the time that the file was backed up. If either set of permissions does not allow access, the user cannot download the backed up content. How do I delegate permission to perform Self-Service Recovery to a user? You use the Site Settings page in the SharePoint Site Collection to delegate permission to a user. You must be a member of the Site Collection Administrators group to delegate permission to perform Self-Service Recovery. The SP backup Administrator must install and configure Self-Service Recovery before you can delegate permissions to use Self-Service Recovery

73 To delegate permission to perform Self-Service Recovery 1. In the Site Collection in SharePoint, click Site Actions > Site Settings. 2. In the Site Settings page, in the Users and Permissions area, click Self-service recovery permissions. 3. In the Self-Service Recovery Permissions page, in the Self-Service Recovery Users field, enter the names of users to delegate permission to use Self-Service Recovery. You can use the Check Names and Browse icons to locate the correct user names. 4. In the Self-Service Recovery Permissions page, click OK. Specifying Idera SharePoint backup preferences You can customize Idera SharePoint backup to meet the needs of your environment. You use the SP backup Preferences dialog box to configure the preferences. For more information, see: Defining the Backup Service preferences on page 73 Defining the Management Service preferences on page 76 Defining the Management Console preferences on page 78 Configuring the Backup Service settings for Multiple Farms on page 78 Understanding load balancing on page 80 Defining the Backup Service preferences You can configure the preferences for the Idera SharePoint backup Backup Service. You can specify the location on your network where SP backup stores backup sets. You can also configure the service account that the Backup Service uses. You can back up content from your SharePoint farms to a network location that you specify with a UNC path. You can also back up content to a Tivoli Storage Manager (TSM) client node. You must set up a TSM virtual server client node before you can back up to a TSM client node. For information about using TSM with SP backup, see Learning about Tivoli Storage Manager on page 32. If you make changes to the default backup set storage location, future backup operations use the new location. Any existing backup sets remain in the original location. When you perform restore operations, you can access both the existing backup sets in the original location and the new backup sets. You can specify a location other than the default for each backup set. You can specify how many simultaneous execution threads that each Backup Service uses when SP backup performs a Granular Backup. The maximum number of threads is 32. Most environments will use fewer threads. When you configure the number of threads, you must balance the backup performance with the performance of the farm as a whole. Determining the number of threads appropriate for your environment involves experiment to determine the best mix for your specific needs. When you specify the timeout value, you determine how long a Backup Service should wait for the Management Service to respond when it tries to connect. When the time that you specify expires, the Backup Service stops trying to connect and logs an error. You specify the timeout in seconds

74 The SP backup Management Service uses the port that you specify to communicate with each Backup Service that you install. You should make sure that the firewall settings on your network allow the Management Service to reach every Backup Service that you install. The Backup Service normally logs its actions. You can control the level of detail that the Backup Service uses in logging. When you enable debug logging, the Backup Service creates debug logs in addition to regular logging. The additional detail in these logs can assist Idera Technical Support. If a problem occurs, you can use the Management Console to send the Backup Service log files to Idera Technical Support. The maximum size of a debug log is 4 MB. When the log file reaches this maximum, SP backup automatically stores the log. SP backup keeps the active log and one stored log. This means that the maximum log size on any Backup Service host is 8 MB. You can configure Backup Service preferences individually for each farm that you add to the Management Console. How many backup execution threads should I use? The number of backup threads appropriate for a particular farm varies with a wide range of factors, including but not limited to the following: The performance of the SharePoint and SQL servers that make up the farm. The data transfer rate of the hard disks on the SharePoint and SQL Servers that make up the farm. The other processes on the SharePoint servers that make up the farm. The other processes that access the SQL Servers that the farm uses. The network bandwidth between the SharePoint servers and the SQL Servers. The size of the SharePoint Content Databases. The default setting for the number of threads should provide acceptable performance in most environments, but the setting may not provide optimum performance. You can perform an experiment to determine the optimum number of threads for your environment requires experiment on your part. You can use the Overview tab in the Granular Backup page to review how long a backup job takes. You can create a single backup job that you run repeatedly, changing the number of threads for each run until you determine the optimum setting for your environment. How do I configure the Backup Service preferences? You use the SP backup Management Console to configure the Backup Service preferences. To view the Backup Service preferences 1. In the SP backup Management Console, do one of the following: Click the name of the farm whose Backup Service preferences you want to set, then click Tools > Preferences, then click Backup Service. In the left pane, click Configuration, then click the name of the farm whose Backup Service preferences you want to set. In the right pane, click Configuration, then click Backup Service. 2. In the Backup Service Preferences dialog box, review the current preferences. 3. Click OK to close the dialog box

75 To add a new backup location 1. In the Backup Service Preferences dialog box, click Add. 2. In the Add Backup Location dialog box, enter a name for the backup location. 3. In the Add Backup Location dialog box, do one of the following: If you want to use a network volume to store backed up information from SharePoint, select Network Location (UNC Path) from the Select the type of backup set location drop-down list, then type the UNC path of the location in the Enter the UNC path of the network location field. If you want to use a Tivoli Storage Manager (TSM) virtual client node to store backed up information from SharePoint, select Tivoli Storage Manager (TSM) from the Select the type of backup set location drop-down list, then specify the client node SP backup should use in the Enter the name of the TSM target client node field 4. To set the new location as the default location, select the Set the default backup set location check box. 5. In the Backup Service Preferences dialog box, click OK. To delete a backup location 1. In the Backup Service Preferences dialog box, click the backup location that you want to remove. 2. Click Remove. 3. SP backup prompts you to confirm that you want to remove the backup location. Click Yes. 4. In the Backup Service Preferences dialog box, click OK. To set a backup location as the default 1. In the Backup Service Preferences dialog box, click the backup location to set as the default. 2. Click Set as default. 3. In the Backup Service Preferences dialog box, click OK. To specify a new default service account for any new Backup Service that you install 1. In the Backup Service Preferences dialog box, in the Deployment area, enter the new default service account the SP backup should use for new Backup Service instances. 2. Click OK. To set the number of threads used by granular backups 1. In the Backup Service Preferences dialog box, in the Granular Backup Threads area, enter the number of threads that SP backup should use when performing granular backups. You can type the number in the field or use the up and down buttons in the threads field to change the number. 2. In the Backup Service Preferences dialog box, click OK. To set the Backup Service timeout value 1. In the Backup Service Preferences dialog box, in the Timeouts area, enter the length of time that SP backup should wait for successful communications. You can type the number

76 of seconds in the field or use the up and down buttons in the threads field to change the number of seconds. 2. In the Backup Service Preferences dialog box, click OK. To configure the port that the Management Service uses to communicate with the Backup Service? 1. In the Backup Service Preferences dialog box, in the Ports area, enter the port that the Management Service uses to communicate with the Backup Service. You can type the number in the field or use the up and down buttons in the threads field to change the number. 2. In the Backup Service Preferences dialog box, click OK. To configure debug logging 1. In the Backup Service Preferences dialog box, in the Debug logging area, select or clear the Enable debug logging checkbox. 2. In the Backup Service Preferences dialog box, click OK. What permissions does the Backup Service require? The service account that you specify for the Backup Service must have the following permissions: Must be a Local Administrator on the SharePoint Web Front End (WFE) that hosts the Backup Service. Must be a member of the SharePoint Farm Administrators group. Must have db_owner access to all SharePoint content databases, including the Admin Content and SharePoint Config databases. Defining the Management Service preferences You can configure the preferences for the Idera SharePoint backup Management Service. You can specify the SQL Server that SP backup uses for the Repository Database. You can also configure the data grooming options for the farm. The Management Service uses the Repository Database to store configuration information and backup set identification data. You can set the Management Service preferences separately for each farm that you back up. What Management Service preferences can I set? You can set the following preferences for the Management Service: Repository SQL Server host Repository Database name SQL Server The SQL Server that hosts the SP backup Repository Database. The specific database on the SQL Server that contains the SP backup Repository Database. The default database name is IderaSPbackupRepository. The type of authentication used for the SQL Server. You can use

77 Authentication type Grooming options Windows or SQL Server authentication. If you use Windows authentication, SP backup uses the service account that you set for the Management Service to access the SQL Server. If you use SQL Server authentication, you must specify a User Name and Password to use to connect to the SQL Server. Lets you control if and when SP backup deletes out-of-date backup sets from the backup location. For additional information about data grooming options, see Learning about data grooming on page 31. Tip: SP backup can use Tivoli Storage Manager (TSM) to store backup set content. If you enable data grooming for a backup set that SP backup stores in TSM, SP backup removes references to the data in SP backup. In addition, SP backup sets the data objects to Inactive in TSM. SP backup does not automatically delete the data itself. If you need to delete the data from TSM, you should use the TSM management tools to do so. For more information about using TSM, see Learning about Tivoli Storage Manager on page 32. How do I set the Management Service preferences? You use the SP backup Management Console to configure the Management Service preferences. To set the Management Service preferences 1. In the SP backup Management Console, do one of the following: In the Farm Backup, Granular Backup, or Configuration panes, click the name of the farm whose Management Service preferences you want to set, then click Tools > Preferences, then click Management Service. In the left pane, click Configuration, then click the name of the farm whose Management Service preferences you want to set, then click Management Service. 2. In the dialog box, make any required changes to your preferences. 3. If you made changes to the Repository Database Connection settings, click Test Connection to verify that the new settings work properly. 4. Click OK to close the dialog box and save the changes you made to the Management Service preferences. What permissions are required for the SQL Server connection and the Management Service? The account that the Management Service uses to access the SQL Server must have specific privileges granted to it. If you use Windows authentication for the SQL Server, SP backup uses the service account that you set for the Management Service to access the SQL Server. If you use SQL Server authentication, you specify a user name and password to use to access the server

78 The account that you specify must be a member of the db_owner role for the database that you specify for the SP backup Repository Database. In addition, the service account that you specify for the Management Service must have Local Administrator permissions on the computer that hosts the Management Service. Defining the Management Console preferences You can configure the preferences for the Idera SharePoint backup Management Console independently for each user on each computer that hosts the Management Console. The preferences that you can set include the following: Automatically refresh status Number of seconds between refreshes Limit the number of matches Hide wizard welcome pages When selected, the SP backup Management Console automatically refreshes status information at an interval that you specify. The time that the Management Console waits before it refreshes status. This option is not available if you disable automatic refresh. When selected and you perform a search in a backup set, the Management Console only displays the number of matches that you specify. Select each check box to hide or to show the Welcome page in the specified wizard. How do I set the Management Console preferences? You use the Management Console preferences pane in the preferences dialog box to configure the Management Console preferences. The preferences are specific to each user on each Management Console host. To set the Management Console preferences 1. In the SP backup Management Console, do one of the following: Click Tools > Preferences, then click Console. In the left pane, click Configuration, then click the name of any farm, then click Console. 2. In the dialog box, make any changes to your preferences. 3. Click OK to close the dialog box and save the changes you made to the Management Console preferences. Configuring the Backup Service settings for Multiple Farms Idera SharePoint backup lets you configure the Backup Service settings for each farm independently. You can set the backup location and service account independently for each farm. How do I configure the Backup Service preferences? You use the SP backup Management Console to configure the Backup Service preferences

79 To view the Backup Service preferences 1. In the SP backup Management Console, do one of the following: Click the name of the farm whose Backup Service preferences you want to set, then click Tools > Preferences, then click Backup Service. In the left pane, click Configuration, then click the name of the farm whose Backup Service preferences you want to set. In the right pane, click Configuration, then click Backup Service. 2. In the Backup Service Preferences dialog box, review the current preferences. 3. Click OK to close the dialog box. To add a new backup location 1. In the Backup Service Preferences dialog box, click Add. 2. In the Add Backup Location dialog box, enter a name for the backup location. 3. In the Add Backup Location dialog box, do one of the following: If you want to use a network volume to store backed up information from SharePoint, select Network Location (UNC Path) from the Select the type of backup set location drop-down list, then type the UNC path of the location in the Enter the UNC path of the network location field. If you want to use a Tivoli Storage Manager (TSM) virtual client node to store backed up information from SharePoint, select Tivoli Storage Manager (TSM) from the Select the type of backup set location drop-down list, then specify the client node SP backup should use in the Enter the name of the TSM target client node field 4. To set the new location as the default location, select the Set the default backup set location check box. 5. In the Backup Service Preferences dialog box, click OK. To delete a backup location 1. In the Backup Service Preferences dialog box, click the backup location that you want to remove. 2. Click Remove. 3. SP backup prompts you to confirm that you want to remove the backup location. Click Yes. 4. In the Backup Service Preferences dialog box, click OK. To set a backup location as the default 1. In the Backup Service Preferences dialog box, click the backup location to set as the default. 2. Click Set as default. 3. In the Backup Service Preferences dialog box, click OK. To specify a new default service account for new Backup Service instances 1. In the Backup Service Preferences dialog box, in the Deployment area, enter the new default service account the SP backup should use for new Backup Service instances. 2. Click OK

80 What permissions does the Backup Service require? The service account that you specify for the Backup Service must have the following permissions: Must be a Local Administrator on the SharePoint Web Front End (WFE) that hosts the Backup Service. Must be a member of the SharePoint Farm Administrators group. Must have db_owner access to all SharePoint content databases, including the Admin Content and SharePoint Config databases. Understanding load balancing When you install Idera SharePoint backup, you normally install the Backup Service instances on multiple Web Front End (WFE) servers in your SharePoint farm. When your SP backup deployment includes multiple Backup Service instances, The Management Service uses automatically assigns backup tasks to the next available Backup Service. Using multiple Backup Service instances helps you balance the load that is assigned to each of the servers in your SharePoint farm. When the Management Service assigns a job to a Backup Service, it checks Backup Service availability in the same order used for Fault Tolerance. If the first Backup Service in the Fault Tolerance list is busy, the Management Service tries the next, and so on until it locates an available Backup Service. If all of the Backup Service instances are busy, the Management Service waits for the first available Backup Service. You do not need to manage load balancing manually. For information about configuring the fault tolerance order, and thus the order that the Management Service uses to assign jobs to Backup Service instances, see Configuring fault tolerance on page 68. Tip: Load Balancing only applies to Granular Backups. Farm Backups are always processed by the Backup Service installed on the server. Managing alerts Idera SharePoint backup can generate an alert when a condition that you specify occurs. When an alert occurs, you can specify that SP backup does one or more of the following: Send an to one or more addresses. Write the alert to the application event log on the Management Service host. You can specify that one or more of the following triggers an alert: Success of a backup, restore, or preview operation. Failure of a backup, restore, or preview operation. Success of a backup or restore operation. Canceled backup or restore operation. Operations that take longer than a specified time. Low disk space. A secondary Backup Service is used for backup. Full backup triggered by the size of a differential backup

81 You can explore the following for more information about alerts: Learning about alerts on page 81 Viewing alerts in the Management Console on page 83 Configuring the alert settings on page 84 Managing the alert notification settings on page 85 Configuring alert grooming on page 87 Learning about alerts An alert is a message from Idera SharePoint backup when a specified condition occurs. You can choose what triggers the alert and also what happens when SP backup generates the alert. The Alerts tab in the Alert Settings dialog box lets you configure when SP backup generates alerts. Alert Notifications are grouped in the following categories: Operation Status Alerts General Alerts What do the alerts inform me about? Operation Status Alerts inform you about backup, restore, and preview failures. These alerts also inform you about errors that SP backup encounters during a backup, restore, or preview. Finally, the alerts inform you when a backup, restore, or preview is successful, and when a backup or restore is canceled. General Alerts notify you about conditions that are not specific to a single backup or restore operation. Rather, General Alerts warn you about issues that are common to all backups. You specify alert settings for each farm separately. What triggers an Operation Status Alert? The following events can trigger an Operation Status Alert: Failed Warning Successful Canceled When selected, SP backup generates an alert when an operation fails. Backup, restore, and preview operations can all generate Failed alerts. When selected, SP backup generates an alert when a backup or restore operation succeeds, but encounters errors. When selected, SP backup generates an alert when an operation succeeds. Backup, restore, and preview operations can all generate Successful alerts. When selected, SP backup generates an alert when a user cancels a backup or restore operation. What triggers a General Alert? You can specify the triggers for General Alerts. Any of the following conditions can trigger a General Alert:

82 Secondary Backup Service used for operation Operation took longer than <number> <unit> Differential backup set size triggered a full backup for next scheduled time Warning alert when disk free space falls below <number> GB. Error alert when disk free space falls below <number> GB. When selected, SP backup generates an alert if the default Backup Service is unavailable and SP backup uses a secondary Backup Service to perform a backup or restore operation. When selected, SP backup generates an alert when a backup takes longer than the amount of time that you specify. When selected, SP backup generates an alert when the size of a differential backup triggers a full backup during the next scheduled backup. You specify when the differential backup size triggers a full backup when you create the scheduled backup.. When selected, SP backup generates a warning alert when the free space it can use to store backup files is lower than the size you specify. The size is in gigabytes (GB). The Backup Service checks the available free space one time each day. When selected, SP backup generates a warning alert when the free space it can use to store backup files is lower than the size you specify. The size is in gigabytes (GB). How do I configure alerts? You use the Alerts page in the Alert Settings dialog box to configure alerts. To configure alerts 1. In the SP backup Management Console, do one of the following: In the Farm Backup pane, the Granular Backup pane, or the Configuration pane, click the name of the farm whose alert settings you want to configure, then click Tools > Alert Settings. In the Farm Backup pane or the Granular Backup pane, click the name of the farm whose alert settings you want to configure, then click Alerts, then click Configure Alert Settings. In the Farm Backup pane, click any server icon in the farm whose alert settings you want to configure, then in the ribbon, click Alerts, then click Configure Alert Settings. In the Granular Backup pane, click any server icon in the farm whose alert settings you want to configure, then in the ribbon, click Alerts, then click Configure Alert Settings 2. In the Alert Settings dialog box, click Alerts. 3. In the Alerts pane, configure the settings for the farm alerts. 4. Click OK to close the dialog box and save the changes

83 Viewing alerts in the Management Console The Management Console lets you view all of the Alert Notifications generated by Idera SharePoint backup. Tip: Deleted alerts do not appear in the Alerts view. You can delete alerts manually. In addition, Alert Grooming can delete alerts automatically. How do I view Alerts? The Alerts view in the SP backup Management Console lets you review and delete alerts and configure alert triggers. The Alerts view also lets you filter Alerts to display only those alerts that are most important to you. To view Alerts In the SP backup Management Console, do one of the following: In the Farm Backup pane or the Granular Backup pane, click the name of the farm whose alerts you want to view, then click Alerts. In the Farm pane, click any server icon in the farm whose alerts you want to view, then in the ribbon, click Alerts. In the Granular Backup pane, click any server icon in the farm whose alerts you want to view, then in the ribbon, click Alerts. How do I filter the displayed alerts? You can use the Alerts view to filter Alerts and display only those alerts that are most important to you. To filter alerts in the Alerts view. 1. In the Alerts view, in the filter area of the ribbon, select one or more of the following check boxes to display alerts in that category: Critical Alerts Warning Alerts Success Alerts 2. In the Filter area of the ribbon, click Date Range. In the pop-up menu, do one of the following: 3. Click Apply. Select a predefined range from the Range drop-down list. Select Custom from the Range drop-down list, then specify the start date in the From field and the end date in the To field. How do I view Alert Notification details? The Alerts view lets you view the details of any alert. To view Alert Notification details 1. In the Alerts view, click any alert to select it. 2. In the View area of the ribbon, click Refresh

84 How do I delete an alert? You use the Alerts view to delete an alert. To delete an alert 1. In the Alerts view, click any alert to select it. 2. In the Action area of the ribbon, click Delete Alert. 3. In the Message dialog box, click Yes to confirm that you want to delete the alert. How do I go to the operation that triggered an alert? You can jump from the Alerts view see the operation that triggered the alert in the Overview tab. To go to the operation that triggered an alert 1. In the Alerts view, click any alert to select it. 2. In the Action area of the ribbon, click Go to Operation. How do I configure Alert settings? You use the Alert Settings dialog box to configure the alert settings. For more information about configuring Alert settings, see Learning about alerts on page 81. How do I configure Alert grooming settings? You use the Alert Settings dialog box to configure the Alert grooming settings. For more information about configuring the Alert grooming settings, see Configuring alert grooming on page 87. Configuring the alert settings The Idera SharePoint backup Management Console lets you configure the conditions that trigger alerts. You can set the alert settings individually for each farm. For more information about the items that can trigger Alerts in SP backup, see Learning about alerts on page 81. How do I configure the alert settings for a farm? Use the Alert Settings dialog box to configure the alert settings for a farm. To configure the alert settings for a farm 1. In the SP backup Console, do one of the following: In the Farm Backup, Granular Backup, or Configuration pane, click the name of the farm whose alert settings you want to configure, then click Tools > Alert Settings. In the Farm Backup or Granular Backup pane, click the name of the farm whose alert settings you want to configure, then click Alerts, then click Configure Alert Settings. In the Farm Backup pane, click any Web Application icon in the farm whose alert settings you want to configure, then in the ribbon, click Alerts, then click Configure Alert Settings

85 In the Granular Backup pane, click any server icon in the farm whose alert settings you want to configure, then in the ribbon, click Alerts, then click Configure Alert Settings 2. In the Alert Settings dialog box, click Alerts. 3. In the Alerts pane, configure the settings for the farm alerts. 4. Click OK to close the dialog box and save the changes. Managing the alert notification settings The Alert Notification tab of the Alert Settings dialog box lets you specify how Idera SharePoint backup handles alerts. You can specify that alerts are entered in the Alert Log, sent as an , or both. If you choose to send an , you must specify the following settings: Alert Notification Options Option Sender Name Reply-to address Recipient(s) Message footer SMTP Server Address SMTP Server Port Use an SSL encrypted connection SMTP Server requires authentication Description If the SMTP server that you specify allows anonymous s, the name that you specify appears in the as the sender of the alert message. If your SMTP server requires authentication, the sender name will be the name of the authorized user. The address that receives any replies to the alert notification. This must be a valid address. Enter one or more recipients of the alert . If you enter more than one recipient, separate addresses with semicolons (;). The specified text appears below the alert in the message. The address of the SMTP mail server that SP backup uses to send the . The TCP/IP port that SP backup uses to connect to the SMTP server. When selected, SP backup uses a Secure Socket Layer (SSL) connection to connect to the SMTP server you specify. The SMTP server must be configured to allow SSL connections. When selected, SP backup uses the User name and password that you specify for the SMTP Server when it sends the alert . If the SMTP server that you specify uses integrated security, the reply-to address that you specify must be a valid account that matches the User name and password that you specify. You specify alert settings individually for each farm. How do I configure the Alert Notification Settings? You use the Alert Notification tab of the Alert Settings dialog box to configure the Alert Notification

86 Settings. To configure the Alert Notification Settings 1. In the SP backup Management Console, do one of the following: In the Farm Backup, Granular Backup, or Configuration pane, click the name of the farm whose alert settings you want to configure, then click Tools > Alert Settings. In the Farm Backup or Granular Backup pane, click the name of the farm whose alert settings you want to configure, then click Alerts, then click Configure Alert Settings. In the Farm pane, click any Web Application icon in the farm whose alert settings you want to configure, then in the ribbon, click Alerts, then click Configure Alert Settings. In the Granular Backup pane, click any server icon in the farm whose alert settings you want to configure, then in the ribbon, click Alerts, then click Configure Alert Settings 2. In the Alert Settings dialog box, click Alert Notification. 3. In the Alert Notification tab, specify the alert notification options. 4. Click Test Settings to send a test using the settings you specify. 5. Click OK to close the dialog box and save the changes. How do I test alert notification settings? You use the Test Settings button in the Alert Notification tab of the Alert Settings dialog box to test the settings you specified for alerts. To test the alert notification settings 1. In the SP backup Management Console, do one of the following: In the Farm Backup, Granular Backup, or Configuration pane, click the name of the farm whose alert settings you want to configure, then click Tools > Alert Settings. In the Farm Backup or Granular Backup pane, click the name of the farm whose alert settings you want to configure, then click Alerts, then click Configure Alert Settings. In the Farm pane, click any Web Application icon in the farm whose alert settings you want to configure, then in the ribbon, click Alerts, then click Configure Alert Settings. In the Granular Backup pane, click any server icon in the farm whose alert settings you want to configure, then in the ribbon, click Alerts, then click Configure Alert Settings 2. In the Alert Settings dialog box, click Alert Notification. 3. Click Test Settings to send a test using the current settings. 4. Click OK to close the dialog box

87 Configuring alert grooming Idera SharePoint backup alert grooming lets you automatically remove any alert notifications that are older than the number of days specified. Groomed alerts no longer appear in the Alerts page in the Management Console. By default, SP backup grooms alerts older than 30 days, automatically deleting older alerts. To change alert grooming, you must configure the settings separately for each farm. How do I configure the Alert Grooming settings? You use the Alert Settings dialog box in the SP backup Management Console. To configure Alert Grooming settings 1. In the SP backup Management Console, do one of the following: In the Farm Backup, Granular Backup, or Configuration pane, click the name of the farm whose alert settings you want to configure, then click Tools > Alert Settings. In the Farm Backup or Granular Backup pane, click the name of the farm whose alert settings you want to configure, then click Alerts, then click Configure Alert Settings. In the Farm Backup pane, click any Web Application icon in the farm whose alert settings you want to configure, then in the ribbon, click Alerts, then click Configure Alert Settings. In the Granular Backup pane, click any server icon in the farm whose alert settings you want to configure, then in the ribbon, click Alerts, then click Configure Alert Settings 2. In the Alert Settings dialog box, click Alert Grooming. 3. Click Do not groom alerts or click Groom alerts older than <> days and choose the number of days to groom alerts after. 4. Click OK to close the dialog box and save the changes you made to the Alert Grooming settings. Managing Backup Set disk space The Today pages in the Farm Backup and Granular Backup views in the Idera SharePoint backup Management Console let you monitor the disk space that your backup sets use. You can also view the disk space that remains in the backup location that you specified. SP backup lets you archive older backup sets to alternate media. You can save archived backup sets that are no longer actively used. You can then reuse the disk space those backup sets used for newer backups. If circumstances require it, you can import the archived backup set and restore objects from the archived set. For more information, see the following: Archiving Backup Sets on page 88 Importing Backup Sets on page

88 Archiving Backup Sets While SP backup does not offer backup set archiving functionality, you can archive older backup sets using Windows Explorer or any other file management tool. When you archive a backup set, you can move the backup set to another disk, allowing you to conserve space on your backup disk and archive the backup set for the future. Archived backup sets continue to appear in the SP backup Management Console, but you cannot review or restore the contents of those sets. If you need to access the contents of an archived backup set, you must import the set. For more information about importing a backup set, see Importing Backup Sets on page 88. Each backup set in the backup set location is stored in a folder with a unique name. The name is based on the name of the backup set and a time stamp. How do I archive a backup set? You can use Windows Explorer or any other file management tool to archive backup sets. You do not use the SP backup Management Console to archive backup sets. To archive a backup set 1. Open Windows Explorer or any other file management tool. 2. Access the directory that contains your backup sets. 3. Use the file management tool to copy that directory to another location. 4. In the SP backup Management Console, delete the operation that uses the backup set. Note that the Management Console also deletes the original copy of the backup set directory. Importing Backup Sets You can import a backup set that you have removed from Idera SharePoint backup. When you import a backup set, you make it available for SP backup to use for backup and restore operations. You might import a backup set in the following cases: Reinstating an archived backup set to review or restore its contents. Moving a backup set to a new installation of SP backup. When you import a backup set from a differential backup, you must ensure that you also import the associated full backup. Tip: If you import a backup set created by SP backup 3.0 that includes a Farm Component backup, SP backup only successfully imports full backups. It does not successfully import backup sets that include differential backups of Farm Component backups. Both Full and Differential backups are imported from granular backups and are imported for all backup sets and all backup types created by SP backup 3.1 and newer. How do I import a backup set? You use the Import Backup Sets dialog box to import a backup set

89 When you import backup sets, you copy all of the backup sets that you want to import into a single directory. In the Import Backup Sets dialog box, you specify that directory as a UNC path and SP backup imports every backup set in the directory. If the Repository Database includes information about a backup set that you import, SP backup updates the Repository Database with the new information. To import backup sets 1. Using the Windows Explorer or another file management tool, move all of the backup sets you want to import into a single directory. Note the UNC path of this directory. 2. In the SP backup Management Console, click File > Import Backup Sets. 3. In the Import Backup Sets dialog box, do one of the following: Select the location that contains the Backup Sets to import from the Backup Set Location drop-down list. Click Manage Locations, then in the Backup Service Preferences dialog box, specify a new Backup Location, then select that location from the Backup Set Location drop-down list. 4. Click Import. SP backup imports all backup sets from the specified location

90 Index: adding backup service Index A adding farm 66 license keys 63 alerts configuring 83-84, 87 configuring grooming 87 configuring settings 84 details 83 filtering 83 general 81 generated 81 grooming 83, 87 managing 80 notifications 85 operation status 81 triggers types 81 viewing 83 architecture 28 archiving 88 B backup location Tivoli 31-32, 57, 76 backup service assigning a web application to 80 configuring 28, 78 fault tolerance 68 granular backups

91 Index: backup sets configuring installing 53 installing manually 53 installing on database server 54 managing 64 ports 32 preferences 73 requirements starting 64 stopping 64 backup sets archiving 88 data grooming 31 importing 88 managing space used 87 benefits 7 C components 28 configuring 50 adding a farm 66 alert grooming 87 alert notifications 85 alerts 84 archiving backup sets 88 backup service preferences 73 connect console to management service 51 data grooming 31 discover farm wizard 66 fault tolerance 68 issues 24 load balancing

92 Index: Contacting Idera errors management console 51 management console preferences 78 preferences 73 removing a farm 67 start the backup service 64 stop the backup service 64 tips 20 Tivoli 32 web part 55, 69 Contacting Idera 16 Customer Service Portal 16, 26 D data grooming backup sets 31 Tivoli 31-32, 76 disaster planning 8, 13 disaster recovery 8, 13 discover farm wizard 52, 54, 57, 66 disk space managing documentation 16 E encryption communications 32 enterprise manager tips 20 errors alerts

93 Index: farm Idera SharePoint backup F farm adding 57, alert notification settings 85 discovering 57 editing 65, 67 managing 65 removing 65, 67 farm backup 65 and disaster planning 8 installing backup service for 53 restore and rebuild 13 fault tolerance 68 features 7 FIPS 32 fixed issues 19 G generated alerts 81 granular backup 65 and disaster planning 8 installing backup service for 53 limitations 24 grooming backup sets 31 I Idera 3, 7, support 26 Idera SharePoint backup architecture 28 benefits

94 Index: Idera Support limitations components 28 defined 7 fixed issues 19 known issues 24 performance 8 release notes 18 starting console 50 welcome 7 what's new in this release 18 Idera Support 26 installing backup service 40-41, 43, 53 backup service requirements issues 24 management console management service standalone SharePoint 41 tips 20 upgrading 45 web part 55, 69 K knowledge base 26 known issues 24 L licenses adding managing removing 62 saving to a file 62 limitations

95 Index: load balancing ports load balancing 80 M management console 28 connecting to management sevice 51 multiple farm 65 opening 50 ports 32 requirements 34 management service 28 connecting console 51 permission requirements 37 ports 32 preferences 76 requirements 35 managing disk space 88 licenses 62 multiple farms 78 N notifications alerts 85 P performance 8 permissions 28, 76 backup service 43, 64 management console 50 management service 37 planning 8, 13 ports

96 Index: preferences scalability preferences 73 backup service in discover farm wizard 57 data grooming 31 management console 78 management service 76 R recovery planning 8 release notes fixed issues 19 install and configuration 20, 24 known issues 24 recommended solutions 26 tips 20 what's new 18 repository database 28 host 76 name 76 permissions 76 requirements backup service management console 34 management service 35 management service permissions 37 SharePoint 34 web part 37 restore from a farm backup 13 S scalability

97 Index: security workarounds security encryption 32 ports 32 server alert notification settings 85 settings alert notifications 85 SharePoint supported versions 34 Support 16 T tips 20 Tivoli 31-32, 57, 76 U upgrading 45 web part 55, 69 W web application alert notification settings 85 web part 28 installing 55, 69 requirements 37 service 32 what's new in this release 18 workarounds