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

Quest Support policy

For customers with a valid support agreement, Quest provides call-in or email support for the current major and minor release, when patched to the latest maintenance release. That release is known as N. Quest also fully supports N - 1 and N - 2. Intermediate versions receive limited support.

Quest describes its product lifecycle (PLC) support policy on its Support website (visit https://support.quest.com/rapid-recovery/, click Policies & PLC, and then expand Software Product Support Lifecycle Policy). To understand full support, limited support, and discontinued support, consult the policy referenced above.

Supportability and interoperability with Rapid Recovery

Following the Quest PLC N - 2 policy for Rapid Recovery, DocRetriever for SharePoint is interoperable with Rapid Recovery Core and Agent as follows:

With these requirements in mind, consider the Core version relative to the version of DocRetriever. Using the latest generally available release of DocRetriever, you can reliably restore SharePoint data from recovery points stored in the repository of a Rapid Recovery Core version as listed in the following table.

Table 1. Interoperability between DocRetriever Console and Agent and the Core version

DocRetriever version

Core version

Description

For this release

N

N

The latest generally available release of Rapid Recovery Core version.

Rapid Recovery Core version 6.1.2

N

N - 1

The prior major and minor Core release, patched to the latest maintenance release.

Rapid Recovery Core version 6.0.2

N

N - 2

Two prior major and minor Core versions, patched to the latest maintenance release.

AppAssure Core version 5.4.3

It may be possible to recover SharePoint data in older recovery points. However, users proceed at their own risk, as this behavior is outside of the Quest Support policy.

Understanding DocRetriever deployment architecture

Using DocRetriever, you can recover SharePoint data from a recovery point (from Rapid Recovery or AppAssure Core), or from an offline backup in another recovery resource.

This section describes the components required for using DocRetriever and the modes in which it is supported.

Understanding the required components

The following components are required to use DocRetriever. The configuration may differ based on your business needs.

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.

The architecture used in your environment may differ based on the mode in which you plan to use DocRetriever for SharePoint.

DocRetriever can be used in two modes:

Standard mode. Using standard mode, you can recover SharePoint data from a recovery point saved through the Core that backs up your front-end SharePoint web server. While Quest recommends this method as the most effective approach for recovering data, you can also recover SharePoint data from one or more offline recovery sources.

Standalone mode. Using standalone mode, your data is not protected in a Rapid Recovery Core or AppAssure Core and does not rely on recovery points for data recovery. In such cases, you can use DocRetriever to view and recover SharePoint information from one or more offline recovery sources.

For information about recovery sources, see Data recovery sources and compatibility.

Understanding standard mode architecture

When DocRetriever is used in standard mode, at least two servers are required.

Core server with SQL Server. The Rapid Recovery Core is located on one server. The Core must have a fully licensed version of SQL Server installed locally. You must be able to perform SQL Attachability checks on this server from the Core.

SharePoint web server with DocRetriever Agent. The SharePoint front-end web server contains the SharePoint information you want to protect. In standard mode, this machine must have the DocRetriever Agent software installed. This machine is also typically protected by the Core. It therefore must contain the Rapid Recovery Agent software, or it is a VM protected agentlessly on the Core.

Machine with DocRetriever Console. The DocRetriever Console is the tool you use to browse, open, and restore SharePoint data from a recovery point or offline backup. The machine with the DocRetriever Console must have a fully licensed version of SQL Server installed locally. The DocRetriever Console can be installed on any network-accessible machine that an administrative user wants to use to restore backed-up SharePoint data.

In standard mode, if the SharePoint administrator wants to browse, open, and restore SharePoint backups from a machine other than the Core server, then a third machine is required. On that third machine, you must install the DocRetriever Console, the service database associated with the DocRetriever Console, and the Local Mount Utility that is included with Rapid Recovery Core.

Figure 2. DocRetriever in standard mode, DocRetriever Console separate

If you have a large enterprise with many web servers that you want to protect with Rapid Recovery or AppAssure Core and with DocRetriever, then install the DocRetriever Agent software on every front-end web server for which you want to recover data using DocRetriever. You can install the DocRetriever Console on the Core server.

Figure 3. DocRetriever in standard mode, multiple SharePoint web servers

Some simple SharePoint configurations include the SQL Server on a separate machine accessible to the front-end web servers over the network.

Figure 4. Simple DocRetriever configuration with separate SQL Server

Complex SharePoint configurations with several front-end web servers may also use a SQL Server on a separate machine. Your network administrator may choose among various configurations that best serve the needs of the enterprise. DocRetriever architecture supports all of these configurations.

Figure 5. Complex DocRetriever configuration with separate SQL Server

Related Documents