Getting Started with Idera SharePoint backup

(1)

(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, SQLcon-fig, SQL comparison toolset, SQL compliance manager, SQLcompliance, SQLcm, SQL defrag man-ager, SQL diagnostic manman-ager, SQLdm, SQL mobile manman-ager, 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. © 2013 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 peri-odically 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 doc-ument at any time.

(4)

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 back-ups, monitor operations, broadcast notifications, and empower their users with self-service granular restore capabilities.

SP backup includes the following: l Full farm protection.

l Granular backup and restore.

l 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 Man-agement 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:

l Automated backup of SharePoint 2010 farm components. l Automated backup of site collections and Web sites.

l Reduced time and size of backups using differentials to capture only those objects that changed since your last full backup.

l Powerful IntelliSearch™ for finding the backed up content you need.

l Self-service SharePoint recovery through an intuitive Self-Service Recovery feature. l Detailed restore capabilities and options for the specific objects you need.

l Comprehensive reporting and operation monitoring provided within the Management Con-sole.

l Easy installation and use.

How does Idera SharePoint backup help me?

Microsoft SharePoint helps you to improve the efficiency of your organization through com-prehensive 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 pow-erful solution that you need.

(8)

admin-istration costs. For SharePoint 2010 farms, SP backup lets you backup and restore the com-ponents that make up your farm.

SP backup incorporates proven SharePoint experience and knowledge in a comprehensive, auto-mated, and effective solution. With SP backup, you can do the following:

l Automate the SharePoint backup process to protect changing content. l Reduce storage requirements for backed up SharePoint objects. l Quickly locate and recover backed up SharePoint objects. l Deliver self-service SharePoint content recovery to save time.

l Eliminate training needs with the intuitive Management Console, Self-Service Recovery fea-ture, and wizards.

l 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 bal-ance the business needs of your enterprise with the technical and financial costs required to imple-ment the plan. Your disaster recovery plan must answer many questions, including the following:

l How long will it take? l What can I afford to lose? l What will it cost?

l 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 recov-ery plan. Backup and recovrecov-ery are technical, process answers to a business question. These tech-nical 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 con-tinuity plan. You create your business concon-tinuity 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?

(9)

consider, including the following:

Term Definition Comments

Recov-ery Point Objec-tive (RPO)

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.

When you specify the RPO, you answer the question "How much data am I willing to lose?"

Recov-ery Time Objec-tive (RTO)

The RTO is the goal amount of time to recover from a disaster. It is meas-ured in time from the present.

When you specify the RTO, you answer the question "How long do I have to restore an agreed-upon level of functionality?

Disaster Recov-ery(DR) targets

The DR targets are the items in your SharePoint deploy-ment that you pro-tect from loss or failure.

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 impor-tance 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 oper-ations. As such, it is not suitable for all parts of your DR strategy. SP backup is not a High Avail-ability (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:

(10)

l Search databases l Service applications

l .NET Framework Configuration l Certificate Store

l Internet Information Services (IIS) Configuration l IIS Metabase

l SharePoint Registry entries l SharePoint Root

l SharePoint Web Application Roots

SP backup does not backup certain other components, including the following: l Microsoft FAST Search Server for SharePoint

l 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:

Per-formance of the SQL Server that hosts the Share-Point data-bases.

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.

Backup loca-tion file per-formance.

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, con-current 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 per-formance of the backup location host can be a significant bot-tleneck.

Network per-formance.

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.

Individual farm server

per-formance.

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 work-load of the Backup Service hosts.

(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:

l Site Collections l Sites

l Lists l Libraries l 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 pen-alties when moving very large amounts of data from or to a SharePoint farm.

Granular Backup is a best fit in the following cases:

Use Comments

Restore data lost through accidental deletion, end-user error, or unintended system action including automated deletion by Site Use Confirmation and Deletion.

Restore is initiated by the backup administrator or a Site Collection admin-istrator.

RPOs are driven by the backup schedule. RTOs are driven by the speed of the restore through the object model. Restore data following a large-scale data loss. 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.

Cross-platform or cross-version recovery of Share-Point data. For example, moving between ShareShare-Point 2007 and SharePoint 2010.

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

(12)

Granular Backups are a poor fit in the following cases:

Backup of the entire Share-Point Farm or the Farm Com-ponents.

Only the SharePoint content is backed up. Con-figuration or farm-level data is not included in back-ups.

Fast recovery, with a short RTO.

Granular Backups have a low RTO for limited amounts of data. For large-scale restoration, the RTO is high.

High availability. 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:

l Content Databases l Service Applications

l Farm Configuration information l Search components

Farm Backups use the Microsoft Volume Shadow Copy Service (VSS) to back up the com-ponents 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:

Back up the entire SharePoint farm. 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 envi-ronment.

Large scale backup of SharePoint Con-tent databases

RPO is driven by the backup schedule. Lets you quickly restore Content data-bases in place to recover lost or corrupt data.

(13)

"Bare metal" restore scenarios. 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.

Very high speed restore with a very low RTO.

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-con-figured 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: l Restore a Web application.

l http://technet.microsoft.com/en-us/library/cc825314.aspx l http://msdn.microsoft.com/en-us/library/ee748618.aspx l Configuration-only restore. l http://technet.microsoft.com/en-us/library/ee428326.aspx l http://sharepointinterface.com/2010/09/10/configuration-only-backup-and-restore-in-sharepoint-2010/

l Restore a service application.

l http://msdn.microsoft.com/en-us/library/ee428305.aspx l Provision search.

l http://blogs.technet.com/b/wbaer/archive/2009/11/23/step-by-step-provisioning-the-search-service-application.aSpx

l http://technet.microsoft.com/en-us/library/ee748654.aspx

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:

l Antivirus configuration.

l Information rights management (IRM) configuration.

(14)

l Customizations deployed as trusted solutions. l 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:

l Attach the source farm configuration database to a SQL Server deployment. l Perform a configuration-only backup on the new farm with the

Backup-SPCon-figurationDatabase cmdlet. When you perform the backup, you specify the SQL Server

where the source farm configuration DB is located.

l 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:

l Attach the restored content databases to the desired SQL Server instance or instances. l Use the Configuration Browser in the SP backup Management Console to view the

con-figuration settings in the backup set, and then use the settings as a guide to create the Web Applications in the SharePoint Central Administration.

l Use the Manage Content Database Settings tool in the SharePoint Central Administration to remove the default database that was created.

l 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:

(15)

l 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 com-ponents to restore in the SP backup Management Console. You restore the farm comcom-ponents to a new SharePoint farm, replacing the existing components.

In general, you can use the following guidelines when you restore search out of place:

l 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.

l When the search service is built, do the following:

l 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.

l Delete the search service application databases.

l Restore the prior search databases and their index files out-of-place. l Reattach the restored database files to the desired SQL Server instance or

instances.

l Delete the existing index files.

l 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.

l Restart the search service and the time service. l 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 per-form 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.

(16)

use the original setup instructions for your decentralized customization to perform the cus-tomization 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 (www.idera.com/support).

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 (www.idera.com/support).

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 (www.idera.com).

Sales 713.523.4433

1.877.GO.IDERA (464.3372)

(only in the United States and Canada) Sales Email [email protected]

Support 713.533.5144

1.877.GO.IDERA (464.3372)

(only in the United States and Canada) www.idera.com/support

Web site www.idera.com

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

(17)

Convention Specifying

Bold Window items

Italics Book and CD titles Variable names New terms

Fixed Font File and directory names Commands and code examples Text typed by you

Straight brackets, as in [value]

Optional command parameters

Curly braces, as in {value}

Required command parameters

Logical OR, as in value 1 | value 2

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 Micro-soft Windows Servers, including SQL Server, SharePoint, PowerShell and MicroMicro-soft 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 avail-ability and reduce administrative overhead and expense. Our award-winning products install in min-utes, 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

(18)

3.2.1 Release Notes

Idera SharePoint backup helps you to automate your SharePoint backups. SP backup includes flex-ible SharePoint restore and recovery.

l New features on page 18 l Fixed issues on page 19 l Tips on page 20

l Known Issues on page 24

l Granular backup and restore limitations on page 24 l Recommended Idera Solutions on page 26

New features

Idera SharePoint backup provides the following new features.

3.2.1 new features

There are no new features for this release.

3.2 new features

l 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.

l Faster performance on Granular Backup and Restore. l Support for restoring multiple list item versions.

l Support for Tivoli Storage Manager destinations for backup sets. l Automate load balancing for granular backups.

l Improved data grooming options, including the ability to retain a specified number of backup sets and per-backup job grooming settings.

l Integrated view of Farm Component and Granular backup operations in the Operation Queue tab.

l First-time configuration wizard to help you deploy and configure SP backup.

3.1 new features

l Expanded support for SharePoint 2010 farms, including the following components: l SharePoint Root (14-hive).

l Internet Information Services (IIS) configuration. l SharePoint site webroot folders.

l .NET Global Assembly Cache (GAC). l Certificate Stores for SSL certificates. l SharePoint-relevant registry entries.

l Related .NET Framework items, including machine.config files.

l Improved restore capabilities for farm component backups, especially search components. l Automated in-place restore of the SharePoint farm, including the farm configuration

(19)

l In-place restore of Search components.

l Enterprise-scale improvements for SQL clustering, service scalability, and VSS integration. l Improved handling of Volume Shadow Copy (VSS) configuration issues.

l Improved Backup Service database permission handling. l SQL Server cluster support.

l SQL Server alias support, including IP addresses and fully-qualified domain names (FQDN). l Improved Wide Area Network (WAN) and slow-link deployment scenarios.

l Improved handling of multi-farm networks.

l Automatic handling of farms with multiple products that use VSS. l Improved handling of lists that contain one million or more items.

3.0 new features

l Farm backup for SharePoint 2010 farms, including configuration information, databases, and more.

l Integrates powerful SQL safe™ compression and encryption for SharePoint 2010 farm com-ponent backups.

l Real-time status updating that includes current progress and operation throughput. l A Today page that reports farm component backup coverage for SharePoint 2010 farms. l Improvements to scalability and fault-tolerance for all backup operations.

Fixed issues

This build includes many fixed issues, including the following:

3.2.1 Fixed issues

l Improved support when restoring Web sites created with user templates deployed in a solu-tion.

l Fixed an issue preventing certain Web apps from displaying objects and causing SP backup to display an error message.

l Fixed an issue preventing backup set grooming and causing users to run out of disk space. l Fixed an issue causing the Management Console to hang when attempting to view the

gran-ular backup operation status.

l Fixed an issue preventing some Web app and site collections from appearing in SP backup Self-Service Recovery.

l Fixed an issue that caused SP backup to search for a backup file even after the site backup fails.

l Fixed an issue causing grooming to fail when a user deletes backup sets outside of the Man-agement Console.

3.2 Fixed issues

l List item versions are now included in Granular Backups.

l SP backup can now restore the Master Pages Gallery as an individual object. l Support for restoring multiple list item versions.

(20)

-3.1 Fixed issues

l Improved restore capabilities for farm component backups, especially search components. l Enterprise-scale improvements for SQL clustering, service scalability, and VSS integration. l Improved handling of Volume Shadow Copy (VSS) configuration issues.

l Improved Backup Service database permission handling.

l Improved Wide Area Network (WAN) and slow-link deployment scenarios. l Improved handling of multi-farm networks.

l Automatic handling of farms with multiple products that use VSS. l Improved handling of lists that contain one million or more items.

3.0 Fixed issues

l Farm component protection for SharePoint 2010 farms, including configuration information, databases, and more.

l Integrates powerful SQL safe™ compression and encryption for SharePoint 2010 farm com-ponent backups.

l Real-time status updating that includes current progress and operation throughput. l A Today page that reports farm component backup coverage for SharePoint 2010 farms. l Improvements to scalability and fault-tolerance for all backup operations.

Tips

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 (www.idera.com/support). Installation and configuration issues

l 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.

l 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.

l 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

l SP backup does not back up FAST Server Search components.

l 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.

(21)

l 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.

l 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.

l 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.

l If ActiveX Scripting is set to prompt, the help may not load properly, and the help window displays a blank screen.

l 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

l 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. l 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

l 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 dis-able the “User Account Control: Run all administrators in Admin Approval Mode” local secu-rity policy.

l 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 Man-agement Console before you restore SharePoint objects from that backup set.

l If the SQL Browser Service is stopped or is disabled on the computer that hosts the Repos-itory Database, the error message "An error occurred connecting to the ReposRepos-itory Data-base. Please verify the preferences are set correctly for Repository Database

Connection." appears. The Management Console relies on the SQL Browser service to

(22)

-nect to the Repository Database. Restart the SQL Browser Service and start the Man-agement Console again.

Backup Service Considerations

l Before you upgrade your SharePoint 2007 farm to SharePoint 2010 Foundation or 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. l 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.

l 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

l 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.

l 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

l 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.

l If the SharePoint Farm includes multiple Search services that are both running simul-taneously, 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.

l Farm Backup does not back up all of the SharePoint components. The WSS_Logging data-base does not appear in the list of selectable components, and it cannot be backed up by SP backup.

l If you restore a database that uses alternative authentication, you may need to manually restore the database connection with your SharePoint farm.

l When you use the Farm Configuration browser to view the contents of an XML file, the Man-agement Console opens the file in memory on the ManMan-agement 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.

(23)

yet available, the Farm Backup may fail. Ensure that all of the SQL Servers have com-pletely started, then repeat the backup.

l 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 ponent and then use another product that uses VSS to perform a backup of the same com-ponent, 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.

l 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 Com-ponents, the backup includes new components automatically.

l 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. l 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.

l If you import a backup set created by SP backup 3.0 or 3.1 that contains a Farm Com-ponent 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

l 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 2010.

l 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.

l 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 unsup-ported 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. l 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.

l 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)

-templates include Wiki sites, Site Directories, Report Centers, Search Centers, Search Centers with Tabs, Collaboration Portals, Publishing Portals, Publishing Portals with Work-flows and News Sites.

Known Issues

Idera strives to ensure our products provide quality solutions for your SharePoint needs. The fol-lowing known issues for Idera SharePoint backup are described in this section.

Farm Backup and Restore Considerations

l If you use a scheduled Farm Backup with differential backups to back up a SharePoint com-ponent 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 third-party 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 back-ups 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 under-stand the abilities and limits of the tool that you select. Idera is committed to giving you the infor-mation 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 lim-itations. 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 com-plementary, 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 com-ponent backup without additional steps. You can use farm comcom-ponent 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?

(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 http://support.microsoft.com/kb/841057.

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 con-straints 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 individ-ual 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 incon-sistencies. 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 http://www.idera.com-/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 (www.idera.com/support).

Number Title 0000410-0

What ports are used by SharePoint backup?

0000366-6

Idera SharePoint Backup Console constantly displays the "Loading ..." message when you attempt a backup or restore.

0000376-2

Users receive 'Access is Denied' or '403 Forbidden' error while sites are being backed up with SharePoint Backup.

0000409-9

Warning during backup, "Unable to export the XML for web part."

0000343-3

(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 com-plex. 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

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 per-missions.

For more information about permissions, see Learning about the requirements on page 34. The SP backup components include the following:

Man-agement 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.

(29)

Multiple copies of the Management Console can all contact a single Management Service. You can let each of the SharePoint admin-istrators 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 Con-sole and Management Service on a computer, or you can install the Management Console only. If you install only the Management Con-sole, you must install the Management Service on another computer.

Man-agement 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 net-work. 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 Con-sole 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.

Backup Service

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 Serv-ice (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 back-ups. 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 Serv-ice. 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 Serv-ice assigns the required policies to the Backup ServServ-ice 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 priv-ileges for the new Web Application.

Repository Database

The SP backup Repository Database stores configuration infor-mation, 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 Repos-itory 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 con-tent.

Self-Service Recovery feature

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.

(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 Defin-ing the Management Service preferences on page 76.

For information about configuring grooming for a scheduled backup, see Specifying backup sched-ule 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 proc-ess, and can interfere with your enterprise network.

Tip: SP backup can use Tivoli Storage Manager (TSM) to store backup set con-tent. 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 groom-ing.

To configure the Data Grooming preferences

1. In the SP backup Management Console, do one of the following:

l 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.

l 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 Man-agement Service checks for expired backup sets.

3. Click OK to close the dialog box and save the changes you made to the Data Grooming set-tings.

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 Destination

Por-t Management Console

Self-Service Recovery fea-ture Backup Service Management Serv-ice 748-4

Management Service Backup Service 748-5

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

(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:

l Install and configure the TSM client software on every server in your SharePoint farm where the Backup Service is installed.

l On the TSM server, create a single virtual client node that the clients share. l Grant access to the virtual client node to every server that hosts a Backup Service. l 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.

l 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, soft-ware, and permission requirements. When you install multiple components on a single host com-puter, 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. l Learning about the SharePoint requirements on page 34

l Learning about the Management Console requirements on page 34 l Learning about the Management Service requirements on page 35 l Learning about the Backup Service requirements on page 35

l Learning about the Self-Service Recovery feature requirements on page 37 l 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:

l Windows SharePoint Services (WSS) 3.0 l Microsoft Office SharePoint Server (MOSS) 2007 l Microsoft SharePoint Foundation 2010

l 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, Win-dows Vista, or WinWin-dows 7 can only host the Management Console.

The computer where you install the Management Console must meet the following minimum requirements:

l 2.0 GHz or faster CPU.

l 2 GB or more memory. The required memory size varies, depending on the size of the Share-Point objects you back up.

l 50 MB free hard disk space.

l Microsoft .NET framework 3.5 SP1.

l Monitor capable of displaying 16-bit or more colors at a resolution of 1024 X 768 or higher. l One of the following Windows versions, either 32-bit or 64-bit:

(35)

l Windows Server 2008 SP2 l Windows Server 2008 R2. l 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 require-ments:

l 2 GB or more memory. The required memory size varies, depending on the size of the Share-Point objects you back up.

l Microsoft .NET framework 3.5 SP1.

l Monitor capable of displaying 16-bit or more colors at a resolution of 1024 X 768 or higher. l One of the following Windows versions, either 32-bit or 64-bit:

l Windows Server 2003 SP2 l Windows Server 2008 SP2 l Windows Server 2008 R2.

In addition, the Management Service stores preferences and other information in a Repository Data-base. 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:

l Microsoft SQL Server 2005 SP3 l Microsoft SQL Server 2008 SP1 l Microsoft SQL Server 2008 R2

In addition, Microsoft SQL Server 2000 SP4 is supported only if you use Microsoft SharePoint 2007.

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:

l 2 GB or more memory. The required memory size varies, depending on the size of the SharePoint objects you back up.

Getting Started with Idera SharePoint backup

Legal Notice

Contents

Welcome to Idera SharePoint backup

Using this Documentation

Contacting Idera

Using the Help

Understanding the document conventions

Idera Products

3.2.1 Release Notes

3.2.1 new features

3.2 new features

3.1 new features

3.0 new features

3.2.1 Fixed issues

3.2 Fixed issues

-3.1 Fixed issues

3.0 Fixed issues

Learning about the components and architecture

-Learning about the requirements