There are a number of different options that affect how Recovery Manager will perform a restoration. Depending on the type of backup, version of SharePoint, permissions and free space available on SQL server Recovery Manager can act differently.

These are the following options available:

  • How information from backup file is being read:

       OLR mode – non-OLR mode

  • Where cache and temporary databases are creates:

      Original – Dedicated

  • How information is applied to SharePoint:

      SharePoint API – Direct SQL

More details about each of these and how to switch between modes are in RMSP Options

Let’s review some scenarios:

Scenario 1

SharePoint 2007 farm

No LiteSpeed installed

Behavior:

In this scenario Recovery Manager works in Originalnon-OLR mode. Data is applied to SharePoint in Direct SQL mode.

How it works:

During analysis/restore RM creates a temporary database (RM_TEMP_CONTENT_B71BB5DA_XXXX) on the production SQL server and restores a backup file into the database. It analyzes information about backup and writes to cache database (RM_Cache_CF2BEBF5). The data is restored from the temporary database directly to SharePoint SQL database.

Scenario 2

SharePoint 2007 farm

LiteSpeed Professional (v 5.2 or higher) or Recovery Manager Backup Reader installed on production SQL server.

Note:

Scenario 1 will become Scenario 2 if you install Recovery Manager Backup Reader on production SQL server. You do not need to install Backup reader if you have LiteSpeed installed.

For more information where LiteSpeed/Backup Reader has to be installed, refer to Recovery Manager Backup Reader

Behavior:

In this scenario Recovery Manager works in Original server mode, reads data from backup in OLR modeusing LiteSpeed. Data is applied to SharePoint in Direct SQL mode.

How it works:

During analysis/restore, RM reads data using LiteSpeed directly from a backup without creating a temporary database. It analyzes information about backup and writes to cache database (RM_Cache_CF2BEBF5) that is created on production SQL. The data is restored directly to SharePoint SQL database.

In some cases, the use of OLR is not possible or is not recommended:

  • - You have compressed Native SQL backups cannot be read by LiteSpeed.
  • - You are restoring to SharePoint 2010 in API mode (Scenario 4).
  • - You are going to restore a whole site collection or working with a backup file which size is more than 100GB. (Lack of performance – reading backup in this case is more time consuming operation than reading entries from a temporary database.)

If either of above examples are applied to you, and you do not want temporary databases to be created on the production SQL server then you could use Dedicated mode (refer to scenario 3)

Scenario 3

Do not want RM databases to be created on Production SQL.

Do not have LiteSpeed (or Recovery Manager Backup Reader) on a Production SQL server.

Behavior:

In Dedicated SQL mode RM creates a temporary (RM_TEMP_CONTENT_B71BB5DA_XXXX) and cache (RM_Cache_CF2BEBF5) databases on SQL server where the Quest repository database (Default name = QMC_Repository) is located.

Note: The OLR mode + Dedicated mode scenario is not supported. If you have LiteSpeed installed, but want to use Dedicated server mode you should disable OLR mode.

 

Scenario 4

SharePoint 2010

Behavior:

For SharePoint 2010 the default option to apply data to SharePoint is SharePoint API mode. This mode does not affect how RM reads data from backups, but how this data gets created in SharePoint. RM creates SharePoint objects and then applies them to SharePoint (no Direct SQL writes).

Note: If you have OLR mode enabled, RM will ignore it and will work in non-OLR + Original (Scenario 1) ornon-OLR + Dedicated (Scenario 3) depending on your settings.

To apply data in SharePoint API mode, Recovery Manager or the Recovery Manager Agent should be installed on any one of SharePoint WFE servers.

Note: Only one agent needs to be installed within the SharePoint farm. (On any front end server)