Download External Data Connector (NetApp)

Features - External Data Connector
External Data Connector (NetApp)
TABLE OF CONTENTS
OVERVIEW
SYSTEM REQUIREMENTS
INSTALLATION
DISCOVER NETAPP SNAPSHOTS
Overview
What Gets Discovered
Your First Discovery
Preparing for SnapProtect Backup and Snap Mining
Managing NetApp Snapshots
SNAPPROTECT BACKUP - EXCHANGE DATABASE
Overview
Proxy Server
Advantages of using SnapProtect Backup
Prerequisites
License Requirements
Snapshot Engines Requirements
Backup Content
Installation
Configuration
Setup the Array Information
Enable Client for SnapProtect Backup
Create a Snapshot Copy
Configure Backup Copy
Enable SnapProtect Backup For a Subclient
Performing SnapProtect Backup
Run a Full SnapProtect Backup immediately
Schedule a Full SnapProtect Backup
View Job History
Browse and Restore
SNAPPROTECT BACKUP - EXCHANGE DATABASE - ADVANCED
Overview
How does SnapProtect Backup Work
Backup Copy Operations
Inline Backup Copy
Offline Backup Copy
Features Supported by Backup Copy Operations
Managing Snapshots
List Snapshots
Mount Snapshots
Delete Snapshots
Revert a Snapshot
Snap Reconciliation
Related Reports
Additional Options
SNAPPROTECT BACKUP - SQL SERVER
Overview
Proxy Server
Advantages of using SnapProtect Backup
Page 1 of 25
Features - External Data Connector
Prerequisites
License Requirements
Snapshot Engines Requirements
Backup Content
Installation
Configuration
Setup the Array Information
Enable Client for SnapProtect Backup
Create a Snapshot Copy
Configure Backup Copy
Enable SnapProtect Backup For a Subclient
Performing SnapProtect Backup
Run a Full SnapProtect Backup immediately
Schedule a Full SnapProtect Backup
View Job History
Browse and Restore
SNAPPROTECT BACKUP - SQL SERVER - ADVANCED
Overview
How does SnapProtect Backup Work
Backup Copy Operations
Inline Backup Copy
Offline Backup Copy
Features Supported by Backup Copy Operations
Managing Snapshots
List Snapshots
Mount Snapshots
Delete Snapshots
Revert a Snapshot
Snap Reconciliation
Related Reports
Additional Options
SNAPPROTECT BACKUP - ORACLE
Overview
Proxy Server
Advantages of using SnapProtect Backup
Prerequisites
License Requirements
Snapshot Engines Requirements
Backup Content
Installation
Configuration
Setup the Array Information
Enable Client for SnapProtect Backup
Create a Snapshot Copy
Configure Backup Copy
Enable SnapProtect Backup For a Subclient
Performing SnapProtect Backup
Run a Full SnapProtect Backup immediately
Schedule a Full SnapProtect Backup
View Job History
Browse and Restore
SNAPPROTECT BACKUP - ORACLE - ADVANCED
Overview
How does SnapProtect Backup Work
Setting Up the Proxy for SnapProtect
Backup Copy Operations
RMAN Snap to Tape Copy
Inline Backup Copy
Page 2 of 25
Features - External Data Connector
Offline Backup Copy
Features Supported by Backup Copy Operations
Managing Snapshots
List Snapshots
Mount Snapshots
Delete Snapshots
Revert a Snapshot
Snap Reconciliation
Restoring data From a Snapshot
Restore Data From SnapShot Using RMAN
Restore Data From SnapShot Using File System
Related Reports
Additional Options
SNAPPROTECT BACKUP - SAP FOR ORACLE
Overview
Proxy Server
Advantages of Using SnapProtect Backup
Prerequisites
License Requirements
Snapshot Engines Requirements
Installation
Configuration
Setup the Array Information
Enable Client for SnapProtect Backup
Create a Snapshot Copy
Configure Backup Copy
Enable SnapProtect Backup For a Subclient
Performing SnapProtect Backup
Run a Full SnapProtect Backup Immediately
Schedule a Full SnapProtect Backup
View Job History
Browse and Restore
SNAPPROTECT BACKUP - SAP FOR ORACLE - ADVANCED
Overview
How does SnapProtect Backup Work
Backup Copy Operations
Inline Backup Copy
Offline Backup Copy
Features Supported by Backup Copy Operations
Managing Snapshots
List Snapshots
Mount Snapshots
Delete Snapshots
Revert a Snapshot
Snap Reconciliation
Command Line Backups
Using SAP Command Line
Related Reports
Additional Options
SNAP MINING - EXCHANGE
Overview
Prerequisites
License Requirements
Create a Snapshot
Hardware Supported Engine
Data Replicator
Discover NetApp Snapshot
Configure Snap Mining
Page 3 of 25
Features - External Data Connector
Mining on a Proxy
Mining on a Single Computer
Run a Snap Mining Job
View Job History
Best Practices for Snap Mining
SNAP MINING - SHAREPOINT
Overview
Prerequisites
Configuring Snap Mining
Same Client - Mined on Proxy Server
Different Clients - Mined on Proxy Server
Same Client - Mined on Source
Running a Snap Mining Data Protection Job
Viewing Job History
Page 4 of 25
Features - External Data Connector
Overview - External Data Connector (NetApp)
TABLE OF CONTENTS
Introduction
Protection and Mining Support
INTRODUCTION
External Data Connector (EDC) provides the facility to collect and merge NetApp Snapshots to a CommCell. These snapshots may then be protected or mined
using the CommCell's SnapProtect and Snap Mining features.
PROTECTION AND MINING SUPPORT
External Data Connector provides protection and mining support as follows:
SNAPPROTECT BACKUP
z
Exchange Database
z
SQL Server
z
Oracle
z
SAP for Oracle
SNAP MINING
z
Microsoft Exchange Mailbox
z
Microsoft SharePoint Server (for mining of the SQL database)
Page 5 of 25
Features - External Data Connector
System Requirements - External Data Connector
NetBackup
Tivoli Storage Manager
NetApp SnapManager
EMC Networker
Supported Features
The following requirements are for External Data Connector:
NETBACKUP
After the discovery process is complete, NetBackup components, such as client computers, backup schedules, and media are mapped to the appropriate
CommCell entity. The following versions of NetBackup are supported for these NetBackup component groupings:
NETBACKUP GROUPING
Configuration
DESCRIPTION
Clients, Policy Types, Policies, Policy Attributes
(compression, encryption), Policy Schedules (frequency,
calendar), Backup Types, Media Server.
SUPPORTED NETBACKUP VERSIONS*
5.1, 6.0, 6.5, 7.0, 7.1
Jobs
Backup and Admin Policy Job information is migrated for
CommCell reporting purposes.
Lifecycle Policies, Storage Units, Robots, and Media Status
are migrated for CommCell reporting purposes.
6.0, 6.5, 7.0, 7.1
Media
6.0, 6.5, 7.0, 7.1
*Both Windows and Unix platforms are supported.
HARD DRIVE
1 GB minimum of hard disk space for software
1 GB minimum of hard disk space on the CommServe computer for merge operations
100 MB of additional hard disk space for log file growth
717 MB of temp space required for install or upgrade (where the temp folder resides)
MEMORY
512 MB RAM minimum required beyond the requirements of the operating system and running applications
PERIPHERALS
DVD-ROM drive
Network Interface Card
MISCELLANEOUS
NETWORK
TCP/IP Services configured on the computer.
.NET FRAMEWORK
.NET Framework 2.0 is automatically installed. Note that .NET Framework 2.0 can co-exist with other versions of this software.
DISCLAIMER
Minor revisions and/or service packs that are released by application and operating system vendors are supported by our software but may not be individually listed in our System
Requirements. We will provide information on any known caveat for the revisions and/or service packs. In some cases, these revisions and/or service packs affect the working of our software.
Changes to the behavior of our software resulting from an application or operating system revision/service pack may be beyond our control. The older releases of our software may not support
the platforms supported in the current release. However, we will make every effort to correct the behavior in the current or future releases when necessary. Please contact your Software
Provider for any problem with a specific application or operating system.
Additional considerations regarding minimum requirements and End of Life policies from application and operating system vendors are also applicable
Page 6 of 25
Features - External Data Connector
Discover NetApp Snapshots
TABLE OF CONTENTS
Overview
What Gets Discovered
Your First Discovery
Components Collected During Discovery
Preparing for SnapProtect Backup, Restore, and Snap Mining
Managing NetApp Snapshots
OVERVIEW
Once External Data Connector is installed on the NetApp Server, NetApp snapshots can be incorporated into your CommCell by performing a discovery
operation. The discovery process collects information from the NetApp server and transfers this information to the CommServe database. Once complete, the
CommServe creates CommCell entities that correspond to the original NetApp entities associated with each snapshot. Discovery is performed at the subclient
level and can be run on-demand or scheduled to run at a specified time.
The discovery process occurs in two phases, described below:
PHASE I: QUERY
During the Query phase, information about the snapshots are compiled in the form of .xml files for the data type selected during installation. This data is then
transferred to the CommServe computer. Discovery jobs may be restarted from the beginning of the transfer phase if necessary.
PHASE II: MERGE
During the Merge phase, External Data Connector maps each NetApp snapshot to a subclient as content.
WHAT GETS DISCOVERED
External Data Connector supports NetApp snapshots containing unique naming conventions.
WHAT DOES NOT GET DISCOVERED
The following NetApp Snapshots are not supported for discovery:
z
Snapshots with generic naming conventions.
z
Single Exchange snapshots containing multiple storage groups from distinct array volumes.
For example:
{
Storage Group 1 contains lun1 and lun2 from file server volume volume1.
{
Storage Group 2 contains disk1 and disk2 from file server volume volume2.
In this configuration, if both storage groups are contained in a single snapshot, that snapshot cannot be discovered or migrated using External Data
Connector.
However, by contrast, storage groups snapped in a single snapshot in the following scenarios are supported for discovery and migration:
{
Storage Group 1 contains lun1 and lun2 from file server volume volume1.
{
Storage Group 2 contains disk1 and disk2 from file server volume volume1.
OR
z
{
Storage Group 1 contains lun1 from file server volume volume1 and lun2 from file server volume volume2.
{
Storage Group 2 contains disk1 from file server volume volume1 and disk2 from file server volume volume2.
The Unconditional Overwrite option is not supported for restores of SQL databases from NetApp snapshots. When performing restores of these snapshots,
the original database must not exist in the destination location.
YOUR FIRST DISCOVERY
When run for the first time, the discovery process is performed in full, collecting information on all snapshots. Subsequent discovery operations can later be
performed incrementally, collecting only new or changed information.
Page 7 of 25
Features - External Data Connector
RUNNING YOUR FIRST DISCOVERY IMMEDIATELY:
1.
2.
From the CommCell Console, right-click on the External Data Connector node,
select New Instance, and select the desired instance type:
z
SnapManager for Oracle
z
SnapManager for SAP/Oracle
z
SnapManager for Microsoft Exchange
z
SnapManager for MSSQL
From the General tab of the External Data Connector dialog box, enter the
following information:
z
A name for the instance.
z
The user name for database access.
z
The password for database access.
Click OK.
An instance, default backup set, and subclient are now created and ready for the
discovery process.
3.
Right-click the subclient for which you want to discover NetApp data and click
Discover.
4.
From the Job Initiation tab of the Discovery Options dialog box, select
Immediate.
SCHEDULING YOUR FIRST DISCOVERY:
1.
2.
From the CommCell Console, right-click on the External Data Connector node,
select New Instance, and select the desired instance type:
z
SnapManager for Oracle
z
SnapManager for SAP/Oracle
z
SnapManager for Microsoft Exchange
z
SnapManager for MSSQL
From the General tab of the External Data Connector dialog box, enter the
following information:
z
A name for the instance.
z
The user name for database access.
z
The password for database access.
Click OK.
An instance, default backup set, and subclient are now created and ready for the
discovery process.
Page 8 of 25
Features - External Data Connector
3.
Right-click the subclient for which you want to discover NetApp data and click
Discover.
4.
From the Job Initiation tab of the Discovery Options dialog box, select
Immediate.
5.
Select Schedule to schedule the discovery for a specific time.
6.
From the Schedule Details dialog box that appears, select the appropriate
scheduling options.
7.
Click Options to view the Advanced Schedule Options dialog box.
Specify the following options:
z
Range of recurrence: Specify the date on which you want this schedule to take
effect.
z
Repeat: Select the value for which you want to run the job repeatedly on the day
in which the job is scheduled to run.
z
Time Zone: Select a specific time zone from which the job schedule time will be
based.
You can also confirm and/or edit (where applicable) your choices from the Job
Summary tab. For a monthly or yearly schedule, you can select either a standard
calendar or a custom calendar.
Click OK once all the desired options have been configured.
8.
Page 9 of 25
Click OK.
Features - External Data Connector
Your discovery operation will execute according to the specified schedule. You can
track the progress of the backup job from the Job Controller window. When the
backup has completed, the Job Controller displays Completed.
COMPONENTS COLLECTED DURING DISCOVERY
After the discovery process is complete, NetApp SnapManager components, such as backup jobs, are mapped to the appropriate CommCell entity. The following
versions of NetApp SnapManager are supported for these NetApp component groupings:
NETAPP GROUPING
Configuration
DESCRIPTION
For Oracle and SAP, database configuration properties are
migrated to create Simpana® clients, backup sets,
instances, subclients, and subclient content.
SUPPORTED NETAPP VERSIONS
NetApp SnapManager for Exchange (Version 6)*
NetApp SnapManager for SQL (Version 5)*
NetApp SnapManager for
For Exchange and SQL, server configuration properties are
migrated to create Simpana® clients, backup sets,
NetApp SnapManager for
subclients, and subclient content.
Backup job information is migrated, as well as their
NetApp SnapManager for
respective snapshots. The imported snapshots can then use
NetApp SnapManager for
SnapProtect features.
Jobs
Oracle (Version 3)**
SAP (Version 3)**
Exchange (Version 6)*
SQL (Version 5)*
NetApp SnapManager for Oracle (Version 3)**
NetApp SnapManager for SAP (Version 3)**
*Windows platform is supported.
**Unix platform is supported.
PREPARING FOR SNAPPROTECT BACKUP, RESTORE, AND SNAP MINING
Once you have performed your first discovery, several entities are created in the CommCell Console to facilitate future SnapProtect backup, restore, and snap
mining operations, each described below.
SUBCLIENTS
Subclients contain information on the discovered snapshot content. Future SnapProtect backup and snap mining operations are facilitated at the subclient
level.
ORACLE AND SAP FOR ORACLE CONTENT
Oracle and SAP for Oracle subclients can contain one of three data sets, depending on the snapshots discovered:
z
Full
z
Partial
z
Offline (with or without Archive Files)
STORAGE POLICIES
A Storage Policy directs the subclient content to the appropriate media. This storage policy is created in an unconfigured state as a placeholder; a new
storage policy must be created and assigned to the subclient before SnapProtect backup or snap mining operations can be performed.
PREPARE FOR SNAPPROTECT BACKUP AND SNAP MINING
To prepare for SnapProtect backup and snap mining, you must first associate the storage policy you designated during the software installation to the
appropriate subclient. To do so:
1.
From the CommCell Browser, right-click the subclient whose associated storage policy you want to change, then click Properties from the shortcut menu.
2.
Click the Storage Device tab of the Subclient Properties dialog box.
3.
From the Storage Policy list of the Data Storage Policy tab, select a data storage policy to associate with this subclient. If necessary, click the Create
Storage Policy button to create a new storage policy to which the subclient can then be associated.
4.
From the Changing a Storage Policy window select the next type of backup operation. Click OK.
5.
If applicable for your agent, you can change the number of data streams from the Number of Data/Database Backup Streams field.
6.
If applicable for your agent, click the Log Storage Policy tab and select a storage policy to associate with this transaction log subclient from the
Transaction Log Storage Policy list. Also, you can set the Number of Transaction Log Backup Streams from this tab.
7.
Click OK to save your changes and close the Subclient Properties Storage Device tab.
PREPARE FOR SNAPPROTECT RESTORE
Page 10 of 25
Features - External Data Connector
To prepare for SnapProtect restore, a backup copy or offline mining operation must be run prior to the restore since the restore operation itself does not
prepare the NetApp snapshot.
MANAGING NETAPP SNAPSHOTS
Once you have prepared for SnapProtect Backup and Snap Mining, you are ready to begin using these features on your snapshots. The following sections
provide links to the feature documentation supported for your NetApp snapshot data type:
SNAPPROTECT BACKUP
Exchange Database
SQL Server
Oracle iDataAgent
SAP for Oracle iDataAgent
SNAP MINING
Microsoft Exchange Mailbox
Microsoft SharePoint Server (for mining of the SQL database)
Page 11 of 25
Features - External Data Connector
Accessing Exchange Data from Database Snapshots
TABLE OF CONTENTS
Overview
RELATED TOPICS
SnapProtect™ Backup - Exchange Database
Prerequisites
Create a Snapshot
Use SnapProtect backup to create a point-in-time snapshot
of the data using hardware storage arrays to provide
snapshot functionality for data protection operations.
Hardware Supported Storage Array
Data Replicator
Discover NetApp Snapshot
Configure Snap Mining
Mining on a Proxy
Mining on a Single Computer
Configuring Wait Time for Parallel Snap
Mining
Configuring for Parallel Snap Mining Preparation Timeout
Run a Snap Mining Job
View Job History
Best Practices
FAQ
OVERVIEW
Snap mining allows you to protect data from an offline copy of the Exchange database. The offline copy is a point-in-time snapshot of the data to be used for
data protection operations. With snap mining, impact to the Exchange Server can be reduced in a production environment thus improving performance.
PREREQUISITES
The following are prerequisites to using this feature:
z
z
Mailboxes that are mined from a Microsoft Exchange 2003 32-bit Server database requires the 32-bit Exchange Mailbox iDataAgent.
Mailboxes that are mined from a Microsoft Exchange 2007 64-bit Server or Microsoft Exchange 2010 64-bit Server databases require the 64-bit Exchange
Mailbox iDataAgent.
z
Ensure that the Operating System on the computer on which the Exchange Server is installed and the computer where the snap is mounted is the same.
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:
z
Hardware supported storage array
z
Software storage array (Data Replicator)
z
NetApp snapshots
HARDWARE SUPPORTED STORAGE ARRAYS
A snapshot can be created with SnapProtect backup using a supported storage array.
For step-by-step instructions on creating a snapshot with a hardware storage array, refer to SnapProtect Backup - Microsoft Exchange Database.
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.
Data Replicator is not supported when mining a snapshot on a single source computer.
NETAPP SNAPSHOTS
Snapshots can also be created by discovering NetApp snapshots with External Data Connector.
Page 12 of 25
Features - External Data Connector
Once your first discovery of NetApp snapshots using External Data Connector installed on a NetApp Server is done and the information was transferred to the
CommServe database, snap mining operations from these snapshots are possible. For step-by-step instructions on discovering NetApp snapshots, see Discover
NetApp Snapshots.
When performing a Snap Mining operation on a proxy and the source is an NetApp snapshot discovered using
External Data Connector, Exchange Management Tools must be installed on the proxy and jcb.dll must be copied
from the Exchange Server onto the proxy. This applies to Exchange Server 2007.
CONFIGURE SNAP MINING
You can mine data from a snapshot directly on the computer hosting the snapshot or from a proxy computer.
z
Method 1: Mining on a Proxy
z
Method 2: Mining on a Single Computer
METHOD 1: MINING ON A PROXY
Running the data protection job on a proxy server improves performance as it offloads processing on the production Exchange server.
Select one of the following configurations to run a snap mining job on the proxy computer. Then configure the subclient of the Exchange Mailbox iDataAgent.
z
Configure on Source but Mine on Proxy
z
Configure on Proxy and Mine on Proxy
CONFIGURE ON SOURCE BUT MINE ON PROXY
In this configuration, the Exchange Database 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
z
Microsoft Exchange Server
z
Exchange Database iDataAgent
z
Exchange Mailbox iDataAgent
z
MediaAgent
z
VSS Provider (required for hardware storage arrays)
z
ContinuousDataReplicator (if Data Replicator is the storage array)
Proxy Computer
z
Exchange Mailbox iDataAgent
z
MediaAgent
z
ContinuousDataReplicator (if Data Replicator is the storage array)
The Exchange Database and Exchange Mailbox Agents are installed on same source client. The Exchange Mailbox iDataAgent is also installed on the proxy
server so that the subclient is configured 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
In this configuration, the Exchange Database iDataAgent creates the snapshot on the source computer.
To configure and run the snap mining job on a proxy computer, install the following components:
Source Computer
z
Microsoft Exchange Server
z
Exchange Database iDataAgent
z
MediaAgent
z
VSS Provider (required for hardware storage arrays)
z
ContinuousDataReplicator (if Data Replicator is the storage array)
Proxy Computer
z
Exchange Mailbox iDataAgent
z
MediaAgent
z
ContinuousDataReplicator (if Data Replicator is the storage array)
The Exchange Mailbox iDataAgent is installed on the proxy server so 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
Page 13 of 25
Features - External Data Connector
A Snap Mining job is configured from a subclient of the Exchange Mailbox iDataAgent.
z
Regardless of the settings in Agent properties (General tab), the Deleted Item Retention will always be protected in a snap mining operation.
z
It is recommended to create one snap mining subclient for each database subclient, since only one subclient can mine from a snapshot at a time.
z
It is not recommended to mix snap mining subclients and traditional subclients within the same backupset.
z
Snap mining can be performed for databases configured in the subclient in which Snap Mining is enabled.
z
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.
Keep in mind that once snap mining is enabled for a subclient, it cannot be reversed.
1.
From the CommCell Browser, right-click a subclient of the Exchange Mailbox
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.
z
Click Perform backup using mining off snapshot.
z
Select the Exchange DB client. This is the source computer where the Exchange
Database is installed and where the snapshot was created.
z
Select the Agent that was used to create the SnapProtect backup. In this case, it
is Exchange Database.
z
Select the subclient on the source computer to use for mining the SnapProtect
backup in Exchange DB subclient to use.
z
If you configured the snap mining job on a source computer but to be run on a
proxy, select Proxy Client and select the proxy computer from the drop-down list.
z
z
The content of a subclient that will be used for snap
mining should not be manually assigned. If any
mailboxes are assigned to a subclient before running a
snap mining data protection job, they may not be
included in the job.
z
If the target database for the snap mining data
protection job contains a mailbox that currently exists
in another subclient, it will not be included in the data
protection job. It is recommended to remove it from
the other subclient's content so that the next snap
mining data protection job will pick it up.
Click OK to save your changes.
METHOD 2: MINING ON A SINGLE COMPUTER
When running a snap mining job on a single computer, install the following components.
z
Microsoft Exchange Server
z
Exchange Database iDataAgent
z
Exchange Mailbox iDataAgent
z
VSS Provider (required for hardware storage arrays)
z
MediaAgent
z
ContinuousDataReplicator (if Data Replicator is the storage array)
In this configuration, the Exchange Database and Mailbox 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 Exchange Mailbox iDataAgent.
Page 14 of 25
Features - External Data Connector
z
Regardless of the settings in Agent properties (General tab), the Deleted Item Retention will always be protected in a snap mining operation.
z
It is recommended to create one snap mining subclient for each database subclient, since only one subclient can mine from a snapshot at a time.
z
It is not recommended to mix snap mining subclients and traditional subclients within the same backupset.
z
Snap mining can be performed for databases configured in the subclient in which Snap Mining is enabled.
z
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.
Keep in mind that once snap mining is enabled for a subclient, it cannot be reversed.
1.
From the CommCell Browser, right-click a subclient of the Exchange Mailbox
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.
z
Click Perform backup using mining off snapshot.
z
Select the Exchange DB client. This is the source computer where the Exchange
Database is installed and where the snapshot was created.
z
Select the Agent that was used to create the SnapProtect backup. In this case, it
is Exchange Database.
z
Select the subclient on the source computer to use for mining the SnapProtect
backup in Exchange DB subclient to use.
z
If you configured the snap mining job on a source computer but to be run on a
proxy, select Proxy Client and select the proxy computer from the drop-down list.
z
z
The content of a subclient that will be used for snap
mining should not be manually assigned. If any
mailboxes are assigned to a subclient before running a
snap mining data protection job, they may not be
included in the job.
z
If the target database for the snap mining data
protection job contains a mailbox that currently exists
in another subclient, it will not be included in the data
protection job. It is recommended to remove it from
the other subclient's content so that the next snap
mining data protection job will pick it up.
Click OK to save your changes.
CONFIGURING WAIT TIME FOR PARALLEL SNAP MINING
In cases where multiple Exchange Mailbox subclients are configured to mine from the same Exchange Database subclient the first job will prepare the snapshot
to be used by all other concurrently running jobs. While this preparation is ongoing the other subclients will wait for preparation to complete. By default they
will check the status of preparation every 15 minutes.
Once the snapshot is prepared the remaining subclients can continue with the backup phase. To change the frequency for checking the preparation status the
key WAITTIME_PARALLEL_SNAPMINING can be created on the client for the appropriate agent.
z
From the CommCell Browser, navigate to Client Computers.
z
Right-click the <Client> in which you want to add the registry key, and then click Properties.
z
Click the Registry Key Settings tab.
z
Click Add.
z
Enter WAITTIME_PARALLEL_SNAPMINING in the Name field.
z
Enter <Instance Root>\MSExchangeMBAgent in the Location field (For Exchange Mailbox iDataAgent).
z
Enter REG_DWORD in the Type filed.
z
Enter n in the Value field.
Where n is the number of minutes the other jobs will wait before checking for the availability of metadata for snap mining.
z
Click OK.
Page 15 of 25
Features - External Data Connector
CONFIGURING FOR PARALLEL SNAP MINING PREPARATION TIMEOUT
It is also advisable to set up a timeout value in case of parallel snap mining. This timeout value specifies the amount of time after which the mailbox subclients
waiting for the snap preparation will start their own snap preparation process.
z
From the CommCell Browser, navigate to Client Computers.
z
Right-click the <Client> in which you want to add the registry key, and then click Properties.
z
Click the Registry Key Settings tab.
z
Click Add.
z
Enter TIMEOUT_PREPARATION_PARALLEL_SNAPMINING in the Name field.
z
Enter <Instance Root>\MSExchangeMBAgent in the Location field (For Exchange Mailbox iDataAgent).
z
Enter REG_DWORD in the Type filed.
z
Enter n in the Value field.
Where n is the number of minutes after which the jobs in the waiting state will timeout.
Click OK.
z
RUN A SNAP MINING JOB
Run a snap mining job by selecting the subclient that was configured.
The procedure to run a snap mining data protection job is the same for all configurations, except for the
configuration where the subclient is configured on the proxy server instead of the source computer.
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:
z
Items that failed during the job
z
Items that succeeded during the job
z
Details of the job
z
Media associated with the job
Page 16 of 25
Features - External Data Connector
z
Events of the job
z
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.
BEST PRACTICES
It is not recommended to use Regular Expression or Active Directory group auto-discovery affinity on a backupset which contains subclients configured for Snap
Mining as the subclient content association may not behave as expected and some mailboxes may fail to be protected. In this case, it is recommended to use
Database affinity as the auto-discovery method.
FAQ
z
Exchange 2010 message moderation approval requests may fail to restore if they were protected by a Snap Mining operation.
z
Mailbox Quotas are not supported by Snap Mining.
KEYWORDS
Snap Mining, Mining Exchange Data, Exchange Snap Mining.
Back to Top
Page 17 of 25
Features - External Data Connector
Accessing SharePoint Data from SQL Database Snapshots
TABLE OF CONTENTS
Overview
RELATED TOPICS
SnapProtect™ Backup - Microsoft SQL Server
Prerequisites
Microsoft SharePoint
Use SnapProtect backup to create a point-in-time snapshot
of the data using hardware storage arrays to provide
snapshot functionality for data protection operations.
Create a Snapshot
Hardware Supported Storage Array
Data Replicator
Discover NetApp Snapshot
Configure Snap Mining
Mining on a Proxy
Mining on a Single Computer
Run a Snap Mining Job
View Job History
Mining a SnapProtect Backup from SharePoint
Mounting a Snapshot of a SharePoint Content Database
Attaching the Snapshot to a Database on a SQL Server Instance
Accessing the Snapshot from SharePoint Central Administration
Best Practices
OVERVIEW
Snap mining allows a granular-level SharePoint Document data protection job to be run from an offline snapshot of SharePoint SQL databases. With snap
mining, performance is improved since processing calls are no longer required from the production back-end SQL Server during a data protection job of an
offline SnapProtect backup. Processing also improves on SharePoint Front-End Web Servers when the data protection job is run on a proxy server.
PREREQUISITES
The following are prerequisites to using this feature:
MICROSOFT SHAREPOINT
These versions of Microsoft SharePoint are supported for snap mining:
z
MOSS 2007
z
WSS v3.0
z
SharePoint 2010 Foundation
z
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:
z
Hardware supported storage array
z
Software storage array (Data Replicator)
z
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.
Data Replicator is not supported when mining a snapshot on a single source computer.
Page 18 of 25
Features - External Data Connector
NETAPP SNAPSHOTS
Snapshots can also be created by discovering NetApp snapshots with External Data Connector.
Once your first discovery of NetApp snapshots using External Data Connector installed on a NetApp Server is done and the information was transferred to the
CommServe database, snap mining operations from these snapshots are possible. For step-by-step instructions on discovering NetApp snapshots, see Discover
NetApp Snapshots.
CONFIGURE SNAP MINING
You can mine data from a snapshot directly on the computer hosting the snapshot or from a proxy computer.
z
Method 1: Mining on a Proxy
z
Method 2: Mining on a Single Computer
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.
z
Configure on Source but Mine on Proxy
z
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
z
SQL Server application
z
SQL Server iDataAgent
z
SharePoint Server iDataAgent
z
MediaAgent
z
VSS Provider (required for hardware storage arrays)
z
ContinuousDataReplicator (if Data Replicator is the storage array)
Proxy Computer
z
SQL Server application
z
SharePoint Server iDataAgent
z
MediaAgent
z
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
z
SQL Server application
z
SQL Server iDataAgent
z
MediaAgent
z
VSS Provider (required for hardware storage arrays)
z
ContinuousDataReplicator (if Data Replicator is the storage array)
Proxy Computer
z
SQL Server application
z
SharePoint Server iDataAgent
z
MediaAgent
z
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.
Page 19 of 25
Features - External Data Connector
CONFIGURE SUBCLIENT
A Snap Mining job is configured from a subclient of the SharePoint Server iDataAgent.
z
It is not recommended to mix snap mining subclients and traditional subclients within the same backupset.
z
Snap mining can be performed for databases configured in the subclient in which Snap Mining is enabled.
z
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.
Keep in mind that once snap mining is enabled for a subclient, it cannot be reversed.
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.
z
Click the Content tab in Subclient Properties.
z
Click Populating...> Proxy Client.
z
z
{
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
When running a snap mining job on a single computer, install the following components:
z
SQL Server application
z
SQL Server iDataAgent
z
SharePoint Server iDataAgent
z
VSS Provider (required for hardware storage arrays)
z
MediaAgent
z
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.
z
It is not recommended to mix snap mining subclients and traditional subclients within the same backupset.
Page 20 of 25
Features - External Data Connector
z
Snap mining can be performed for databases configured in the subclient in which Snap Mining is enabled.
z
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.
Keep in mind that once snap mining is enabled for a subclient, it cannot be reversed.
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.
z
Click the Content tab in Subclient Properties.
z
Click Populating...> Proxy Client.
z
z
{
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.
Page 21 of 25
Features - External Data Connector
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:
z
Items that failed during the job
z
Items that succeeded during the job
z
Details of the job
z
Media associated with the job
z
Events of the job
z
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:
1.
From the CommCell Browser, navigate to Client Computers | <Client> | SQL
Server.
2.
Right-click <Instance>, point to All Tasks, and then click List Snaps.
3.
Right-click the snapshot that you wish to mount and click Mount.
4.
Click Yes.
5.
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.
Page 22 of 25
Features - External Data Connector
6.
If you do not wish to save any changes made to the mounted snapshot after the
snapshot is unmounted, select Protect Snapshot during mount.
7.
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.
Page 23 of 25
Features - External Data Connector
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.
z
To view the contents of the snapshot, select Browse content.
z
To back up the snapshot, select Backup site collection.
z
To restore the contents of the snapshot, select Export site or list.
Page 24 of 25
Features - External Data Connector
BEST PRACTICES
During snap mining backup, views that reside on a Web Server’s file system will not be backed up.
Back to Top
Page 25 of 25