Chat now with support
Chat with Support

Rapid Recovery 6.1.2 - DocRetriever for SharePoint User Guide

Introduction to DocRetriever for SharePoint Installing and configuring DocRetriever
System requirements Supported items Roadmap for installing DocRetriever for SharePoint Obtaining DocRetriever installation software Guidelines for upgrading DocRetriever for SharePoint Setting up Windows user accounts for use with DocRetriever Installing, uninstalling, and repairing DocRetriever for SharePoint Creating a local service database for DocRetriever Configuring DocRetriever Console settings Manually specifying the SharePoint database location
Recovering SharePoint data with DocRetriever Working with DocRetriever log files About us Glossary

Understanding DocRetriever standalone mode architecture

In standalone mode, DocRetriever does not rely on Rapid Recovery or AppAssure for recovery. Instead of using a recovery point as a data recovery source, you browse a standard or differential backup made natively from SharePoint, or a SQL database itself. A simple implementation of DocRetriever in standalone mode may include a single server. In this configuration, the front-end SharePoint web server contains the SharePoint farm, the DocRetriever Console, the local service database supporting the console, and the DocRetriever Agent.

Figure 6. DocRetriever in standalone mode, one server

Alternatively, the SharePoint administrator may install the DocRetriever Console (and its associated service database) on a separate workstation from the web server and the DocRetriever Agent software.

Figure 7. DocRetriever in standalone mode, two machines

Product features of DocRetriever

DocRetriever includes the following features and functionality.

Flexible SharePoint data recovery

As a SharePoint administrator, when you manually restore SharePoint data without the use of DocRetriever, you can typically only restore information at the site collection level. Using DocRetriever, the scope of data recovery is greatly expanded over traditional recovery methods. You can restore SharePoint data from the highest level (a SharePoint site collection that may contain one or more SharePoint sites) down to the lowest component (a single document, an item list, a library, and so on).

DocRetriever supports SharePoint data recovery from the versions of Microsoft SharePoint listed in the topic System requirements.

When you manually restore backed-up SharePoint data, the restored backup typically replaces any changes in data that have taken place in your live SharePoint environment. Any additions, modifications, or deletions that were completed since the backup was taken are lost. But using DocRetriever, you have more options than restoring all or nothing. In the DocRetriever Console, you browse through the backed-up SharePoint site. You can select some or all of the data, and restore it in a location you specify. When you restore, SharePoint permissions are kept intact, without having to rebuild the entire production database. You can skip existing items, restore multiple versions of the same document, or combinations of each.

You can also use DocRetriever to migrate SharePoint site collections from one location to another, copying or moving that data with ease.

DocRetriever performs all restore operations through the supported SharePoint APIs for compliance.

Familiar user interface

The DocRetriever Console closely follows the SharePoint user interface, letting you browse through SharePoint content with a clear understanding of context, structure, and permissions.

DocRetriever enables full content searches so you can find any object in seconds.

Multiple data sources for recovery

DocRetriever provides access to SharePoint information that is backed up in any of several data sources which are sorted into two categories: recovery points, or recovery sources.

Recovery points. Quest recommends recovering SharePoint data from a recovery point. A recovery point is a backup taken using Rapid Recovery or AppAssure Core. To successfully recover and restore SharePoint data, the recovery point must include backup information from a SharePoint front-end web server that is protected by a Rapid Recovery Core. To restore the data, the DocRetriever Agent software must be installed on at least one SharePoint web server.

NOTE: For information about installing and configuring a Rapid Recovery Core, see the Rapid Recovery Installation and Upgrade Guide. For information about setting a backup strategy or using Rapid Recovery to back up data, see the Rapid Recovery User Guide.

To restore from a specific recovery point, you must first mount the recovery point as a writable volume. If the DocRetriever Console is installed on the machine with the Rapid Recovery Core, mount this volume from within the Rapid Recovery Core.

If the Console is installed on a different machine, then the relevant core is considered to be remote. To mount the recovery point of a remote core, use the Local Mount Utility (LMU) that is included with Rapid Recovery.

Once the appropriate recovery point is mounted as a writable volume, you can access the information from DocRetriever by selecting File > Open > Recovery Point Location. For more information, see Opening recovery points in DocRetriever.

Recovery sources. If restoring data from a recovery point is not an option, you can recover SharePoint data from a recovery source. Recovery sources include a SharePoint content database, SharePoint farm, SQL backup, or a standard or differential SharePoint backup.

You can open a recovery source from the DocRetriever Console by selecting File > Open > Recovery Source Location. There are different requirements for connecting to each recovery source type. These details are provided in the procedure for opening each recovery source. For more information, see Opening SharePoint recovery sources in DocRetriever, and then refer to the section for each specific recovery source type.

There are different strategies for selecting a recovery source. Ultimately, the suggested approach is to experiment with recovering data and use the recovery source that is most successful in your environment. The following are some recovery source guidelines:

Event logging and auditing

DocRetriever audits and logs all operations for easy access to what objects have been added or modified.

For more information about logging, see Working with DocRetriever log files.

Data recovery sources and compatibility

Recommended recovery sources

For best results, Quest recommends attempting recovery of SharePoint data from a recovery point. DocRetriever was designed first to take advantage of snapshot data saved to a repository by a Rapid Recovery or AppAssure Core.

If that option is not possible, you can then try recovery from an offline recovery source such as a SharePoint farm, content database, SQL backup file, or a SharePoint backup, in that order of preference.

Supported sources for data recovery

Using DocRetriever, you can recover SharePoint objects from the following sources:

Databases from supported versions of Microsoft SQL Server, as described in System requirements, with backward compatibility. SQL Server support is dependent on which version is associated with the DocRetriever Console.

Scenarios for using DocRetriever

Using DocRetriever, you can recover and restore SharePoint data. The first issue to consider is scope.

You may want to recover a single inadvertently deleted document. You may need to recover dozens of documents used by a specific employee, in response to a legal request supporting a claim or lawsuit. Or you may have experienced a data loss and need to recover order information or transactions since the last backup. Regardless of the scope of data you need to recover, DocRetriever is a powerful tool to aid your enterprise in fast, easy data recovery. The approach to recovering and restoring your data is the same for each of these scenarios.

The next issue to consider is purpose. The most common situation is for users to retrieve information from an offline backup and to restore some or all of that information to a live SharePoint site.

DocRetriever can also be used to migrate SharePoint data, copying or moving data from one SharePoint farm to another.

The following scenarios discuss some common situations for using DocRetriever to recover, copy, or move SharePoint data, and provide simple roadmaps to accomplish each objective.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating