Accessing SharePoint Data from SQL Database Snapshots

Overview

Prerequisites

The following are prerequisites to using this feature:

Microsoft SharePoint

These versions of Microsoft SharePoint are supported for snap mining:

• MOSS 2007
• WSS v3.0
• SharePoint 2010 Foundation
• SharePoint Server 2010

Create a snapshot

A snapshot needs to be created for snap mining. It can be created before or after configuring the subclient for snap mining. Snapshots are created in one of these ways:

• Hardware supported storage array
• Software storage array (Data Replicator)
• NetApp snapshots

Hardware Supported Storage Arrays

A snapshot can be created with SnapProtect backup using a supported storage arrays.

For step-by-step instructions on creating a snapshot with a hardware storage array, refer to SnapProtect Backup - Microsoft SQL Server.

Data Replicator

A snapshot can be created with SnapProtect backup when Data Replicator is selected as the storage array. Data Replicator provides the snapshot functionality without the need for any specialized hardware.

For step-by-step instructions on creating a snapshot with Data Replicator as the software storage array, refer to SnapProtect^™ Backup - Data Replicator.

Configure Snap Mining

Method 1: Mining on a Proxy

Select one of the following configurations to run a snap mining job on the proxy computer. Then configure the subclient of the SharePoint Server iDataAgent.

• Configure on Source but Mine on Proxy
• Configure on Proxy and Mine on Proxy

Configure on Source but Mine on Proxy Server

The SQL Server iDataAgent creates the snapshot on the source computer. To run the snap mining job on a proxy but configure it on the source computer, install the following components:

Source Computer

• SQL Server application
• SQL Server iDataAgent
• SharePoint Server iDataAgent
• MediaAgent
• VSS Provider (required for hardware storage arrays)

• ContinuousDataReplicator (if Data Replicator is the storage array)

Proxy Computer

• SQL Server application
• SharePoint Server iDataAgent
• MediaAgent

• ContinuousDataReplicator (if Data Replicator is the storage array)

The configuration of the subclient content of the SharePoint Server iDataAgent is performed on the source client. Mounting of the snapshot and backing it up are performed on the proxy computer.

Configure on Proxy and Mine on Proxy Server

The SQL Server iDataAgent creates the snapshot on the source computer. To configure and run the snap mining job on a proxy, install the following components:

Source Computer

• SQL Server application
• SQL Server iDataAgent
• MediaAgent
• VSS Provider (required for hardware storage arrays)

• ContinuousDataReplicator (if Data Replicator is the storage array)

Proxy Computer

• SQL Server application
• SharePoint Server iDataAgent
• MediaAgent

• ContinuousDataReplicator (if Data Replicator is the storage array)

The SharePoint Server iDataAgent is installed on the proxy server and configuration of the subclient content is performed on the proxy server. Mounting of the snapshot and backing it up are also performed on the proxy server.

Configure Subclient

A Snap Mining job is configured from a subclient of the SharePoint Server iDataAgent.

• It is not recommended to mix snap mining subclients and traditional subclients within the same backupset. 
• Snap mining can be performed for databases configured in the subclient in which Snap Mining is enabled.
• Typically, the subclient is configured first before the snapshot is created. The only exception to this rule would be for NetApp snapshots that are discovered using External Data Connector. In this case, the subclient can be configured at any time.

1.	From the CommCell Browser, right-click a subclient of the SharePoint Server iDataAgent and select Properties. This subclient will be used to run the snap mining data protection job.
2.	Click the Content tab in Subclient Properties. Click Populating...> Proxy Client. Select the SQL DB client. This is the source client computer where the SharePoint Databases are located. Select the Agent that was used to create the SnapProtect backup. In this case, it is SQL Server. Select the Instance of the SQL Server iDataAgent used to create the SnapProtect backup. Select the subclient on the source computer to use for mining the SnapProtect backup from the SQL DB subclient to use drop-down list. If you are using a proxy computer to run the snap mining job, click Proxy Client and select the proxy computer.  In the Offline Mining section: Specify the SQL Instance Name that will be used to mine the offline databases. Enter the credentials in User Name and Password to access the offline databases so that the snapshot is successfully mounted and attached. Click OK to save your changes.

Method 2: Mining on a Single Computer

• SQL Server application
• SQL Server iDataAgent
• SharePoint Server iDataAgent
• VSS Provider (required for hardware storage arrays)
• MediaAgent

• ContinuousDataReplicator (if Data Replicator is the storage array)

In this configuration, the SQL Server and SharePoint Server iDataAgents are installed on the same computer, so creating the snapshot and configuring the subclient is performed on this computer. Mounting of the snapshot and backing it up are also performed on this computer.

Configure Subclient

A Snap Mining job is configured from a subclient of the SharePoint Server iDataAgent.

• It is not recommended to mix snap mining subclients and traditional subclients within the same backupset. 
• Snap mining can be performed for databases configured in the subclient in which Snap Mining is enabled.
• Typically, the subclient is configured first before the snapshot is created. The only exception to this rule would be for NetApp snapshots that are discovered using External Data Connector. In this case, the subclient can be configured at any time.

1.	From the CommCell Browser, right-click a subclient of the SharePoint Server iDataAgent and select Properties. This subclient will be used to run the snap mining data protection job.
2.	Click the Content tab in Subclient Properties. Click Populating...> Proxy Client. Select the SQL DB client. This is the source client computer where the SharePoint Databases are located. Select the Agent that was used to create the SnapProtect backup. In this case, it is SQL Server. Select the Instance of the SQL Server iDataAgent used to create the SnapProtect backup. Select the subclient on the source computer to use for mining the SnapProtect backup from the SQL DB subclient to use drop-down list. If you are using a proxy computer to run the snap mining job, click Proxy Client and select the proxy computer.  In the Offline Mining section: Specify the SQL Instance Name that will be used to mine the offline databases. Enter the credentials in User Name and Password to access the offline databases so that the snapshot is successfully mounted and attached. Click OK to save your changes.

Run a Snap Mining Job

Run a snap mining job by selecting the subclient that was configured.

1.	Right-click the subclient that was configured and select Backup.
2.	Click Full backup type.
3.	Click OK. You can track the progress of the backup job from the Job Controller window. If you are using a stand-alone drive, you are  prompted to load a specific cartridge into the drive. If you are using a library, you will not receive this prompt. The system loads the tapes automatically. Your cartridges should be appropriately labeled. This will enable you to locate the correct cartridge for a restore job, if necessary. Once completed, the details of the job can be viewed in the Job History window.
4.	Run a Browse and Restore operation.

View Job History

Once a snap mining job has completed, it may be useful to view specific historical information about the job, such as the following:

• Items that failed during the job
• Items that succeeded during the job
• Details of the job
• Media associated with the job
• Events of the job
• Log files of the job.

This information can be viewed in the Job History window. The history provided depends on the entity from which the job history is viewed. For example, viewing job history from the subclient level will yield information for the jobs performed for that subclient. Conversely, viewing job history from the instance level will yield information for jobs run from all subclients within that instance.

To view the backup job history:

1. From the CommCell Browser, right-click the entity (client computer, iDataAgent, instance, or subclient) whose backup history you want to view, click View, and then click View Job History.
2. From the Job History filter window select the filter options, if any, that you want to apply, and then click OK.

   The system displays the Job History window.

3. Once you have chosen your filter options, they are displayed in the Job History window.

   To view the additional options discussed above, right-click the desired job choose the appropriate option.

4. Click OK.

Mining a SnapProtect Backup from SharePoint

You can restore a SnapProtect backup of a SharePoint content database without restoring a configuration database, and then mine the contents of the snapshot with SharePoint Central Administration.

1. Restore a snapshot of a SharePoint content database to a mount location.
2. Using SQL Server Management Studio, attach the snapshot of the SharePoint content database to a SQL server instance.
3. Using SharePoint Central Administration, browse or back up files from the snapshot of the SharePoint content database that are attached to the SQL server instance.

Mounting a Snapshot of a SharePoint Content Database

Perform the following operation on an SQL Server iDataAgent that contains a snapshot of a SharePoint content database.

You can mount any available snapshot to access the data included in the snapshot. It is recommended that you select the option to protect a snapshot when it is mounted, as this will ensure that the changes made to the snapshot when it is mounted are not retained when you unmount the snapshot and the snapshot is usable for data protection operations. Follow the steps given below to mount snapshots:

From the CommCell Browser, navigate to Client Computers | <Client> | SQL Server. Right-click <Instance>, point to All Tasks, and then click List Snaps. Right-click the snapshot that you wish to mount and click Mount. Click Yes. In the Mount Path dialog box, specify the destination client and the path on the client in the Destination Client and Destination Path fields. On a Windows platform, enter a CIFS Share Name for the Agent. If you do not wish to save any changes made to the mounted snapshot after the snapshot is unmounted, select Protect Snapshot during mount. Click OK. If you do not select Protect Snapshot during mount, the changes made to snapshot when it is mounted will be retained after the snapshot is unmounted and the snapshot can no longer be used for restore.

Attaching the Snapshot to a Database on a SQL Server Instance

You must attach the snapshot of the SharePoint content database using SQL Server Management Studio.

To attach the snapshot to a database on a SQL server instance:

1.	Open Microsoft SQL Server Management Studio.
2.	From the Server type list, select Database Engine.
3.	In the Server name list, specify a server, and then click Connect.
6.	In Object Explorer, right-click Databases,and then click Attach.
7.	In the Attach Databases dialog box, click Add.
8.	In the Locate Database Files dialog box, navigate to the disk drive where the snapshot of the SharePoint content database resides, and then select the .mdf file for the snapshot.
9.	Click OK.
10.	Click OK. The snapshot is now attached to the SQL Server instance.

Accessing the Snapshot from SharePoint Central Administration

Once you have attached the SharePoint content database snapshot to a SQL server instance, you can then view, back up, or restore the contents. You must perform these steps inside SharePoint Central Administration.

To access the SharePoint content database snapshot from the SharePoint Central Administration application:

1.	Open the SharePoint Central Administration application.
2.	Click Backup and Restore.
3.	Under Granular Backup, click Recover data from an unattached content database.
4.	In the Database Server box, enter the name of the Database Server where the content database is located.
5.	In the Database Name box, enter the name of the content database.
6.	Under Database authentication, select an authentication type, and if required, enter the appropriate credentials.
7.	Select one of the options, and then click Next. To view the contents of the snapshot, select Browse content. To back up the snapshot, select Backup site collection. To restore the contents of the snapshot, select Export site or list.

Best Practices

During snap mining backup, views that reside on a Web Server’s file system will not be backed up.

Back to Top