SMSP Platform Backup and Restore

SMSP Platform Backup and Restore
SnapManager® 8.1 for Microsoft® SharePoint®
Platform Backup and Restore
User’s Guide
NetApp, Inc.
495 East Java Drive
Sunnyvale, CA 94089 USA
Telephone: +1 (408) 822-6000
Fax: +1 (408) 822-4501
Support telephone: +1 (888) 4-NETAPP
Documentation comments: [email protected]
Information Web: http://www.netapp.com
Part number: 215-08734_A0
May 2014
Table of Contents
Overview ....................................................................................................................................................... 6
About Platform Backup and Restore ............................................................................................................ 8
Before You Begin......................................................................................................................................... 10
Configuration .......................................................................................................................................... 10
Agents ..................................................................................................................................................... 10
Permissions ............................................................................................................................................. 10
Getting Started............................................................................................................................................ 11
Launching Platform Backup and Restore ................................................................................................ 11
User Interface Overview ......................................................................................................................... 12
Notes for Customers Updating to SharePoint 2013 ................................................................................... 13
Configuring Devices and Setting up Storage Policies .................................................................................. 14
About the Verification and Index Policy ..................................................................................................... 15
Configuring a Verification and Index Server Profile ................................................................................ 15
Configuring a Verification and Index Server Group Profile..................................................................... 17
Command with Operation .......................................................................................................................... 19
Configuring a Command Profile .............................................................................................................. 20
Command Arguments Used to Pass Information to the Program or Script ........................................... 22
Migrator Tools............................................................................................................................................. 25
Migrate Database.................................................................................................................................... 25
Migrate Index .......................................................................................................................................... 27
Selecting Content to Back Up ..................................................................................................................... 29
Using the Custom Database Feature ...................................................................................................... 32
SharePoint Components Supported for Backup ......................................................................................... 34
Using Plan Builder to Back Up Data ............................................................................................................ 36
Using Wizard Mode to Create a Backup Plan ......................................................................................... 36
Using Form Mode to Create a Backup Plan ............................................................................................ 49
Backing up Databases First, and then Index Components...................................................................... 49
Running a Backup Job Immediately ........................................................................................................ 50
Managing Plans ........................................................................................................................................... 51
2
SMSP 8.1 Platform Backup and Restore User’s Guide
Configuring the Run Now Interface ........................................................................................................ 53
Generating an Index.................................................................................................................................... 57
Checking the Generate Index Job Status ................................................................................................ 60
Configuring the Maximum Number of Snapshots Cloned for Index Generation ................................... 61
Configuring the Maximum Number of Database Indices to Generate in Parallel .................................. 61
Performing a Restore .................................................................................................................................. 62
Building a Restore Plan ........................................................................................................................... 64
Building a Restore Plan at Database Level .............................................................................................. 66
Building an In Place Platform Granular Restore Plan.............................................................................. 71
Building an Out of Place Platform Granular Restore Plan ...................................................................... 80
Restoring a Database to a Point in Time ................................................................................................. 89
Restoring from an Alternate Storage Location ....................................................................................... 89
Cloning SharePoint Components for Restore ......................................................................................... 91
Options for Restoring Backed-up Web Front-end Files .......................................................................... 97
Restoring Backed-up BLOB Data ............................................................................................................. 98
Restoring Backed-up Stub Database ....................................................................................................... 99
Restoring Backed-up Database Master Key .......................................................................................... 101
Deselecting the Restore Granular Content Feature ............................................................................. 102
Restore Details for Specific Farm Components .................................................................................... 103
Backup and Restore FAST Search Server for SharePoint 2010 Farms ...................................................... 104
Backing Up the FAST Search Server ...................................................................................................... 104
Restoring the FAST Search Server ......................................................................................................... 106
Supported and Unsupported List .......................................................................................................... 107
About Platform Backup and Restore for SQL Mirroring Database ........................................................... 109
About Platform Backup and Restore for Failover Database ..................................................................... 110
Checking a Job Status ................................................................................................................................ 112
Troubleshooting for Platform Backup and Restore .................................................................................. 113
Cannot See the Farm in Migrate Index Wizard ..................................................................................... 113
Cannot Load Remote Backups .............................................................................................................. 113
Appendix A: About Find Site Collection .................................................................................................... 114
Appendix B: About Advanced Search ....................................................................................................... 116
Appendix C: Supported SharePoint Components ..................................................................................... 120
SMSP 8.1 Platform Backup and Restore User’s Guide
3
SharePoint 2010 Components Supported in Platform Backup and Restore ........................................ 120
SharePoint 2013 Components Supported in Platform Backup and Restore ........................................ 126
Platform Restore Support Table ........................................................................................................... 130
Appendix D: SharePoint 2013 Social Features Supported in Platform Backup and Restore .................... 159
Appendix E: SharePoint Object Security and Property ............................................................................. 161
Appendix F: Using Hot Key Mode in Platform Backup and Restore ......................................................... 162
Backup Tab ............................................................................................................................................ 162
Restore Tab ........................................................................................................................................... 163
Plan Manager Tab ................................................................................................................................. 165
Copyright Information .............................................................................................................................. 166
Trademark Information............................................................................................................................. 167
4
SMSP 8.1 Platform Backup and Restore User’s Guide
SMSP 8.1 Platform Backup and Restore User’s Guide
5
Overview
SnapManager for SharePoint is an enterprise-strength backup, recovery, and data management solution
for SharePoint Foundation 2010 and SharePoint Server 2010 (all current and future service packs), as
well as SharePoint Foundation 2013 and SharePoint Server 2013 (all current and future service packs).
Operating on NetApp’s latest distributed software platform, SnapManager for SharePoint is accessible
from anywhere in the network through Internet Explorer® (other browsers are supported), and can
monitor multiple SharePoint environments across a network. SnapManager for SharePoint Manager’s
main features include the following:
6
•
The ability to centrally manage SharePoint backup and recovery jobs including
scheduling, monitoring, reporting (logging and e-mail notifications), user account
management, and software Agent management across multiple SharePoint farms from
a single accessible-from-anywhere Web interface
•
Fast backup speeds leveraging NetApp Snapshot backups, as well as real- time granular
restore of items, item versions, lists, libraries, sites, and site collections directly onto the
production server or an alternate location
•
Backup coverage of all SharePoint 2010 and 2013 databases
•
Backup of SharePoint search index files
•
Backup of various SharePoint component settings including SharePoint and third-party
solutions, IIS settings on Web front-end servers, SharePoint Global Search settings, and
InfoPath Forms Services
•
SnapMirror replication for backups of SharePoint databases and search indexes, Storage
Manager BLOB data and Connector BLOB data, and verification of SnapMirror
destination targets
•
SnapVault data set for backups of: SharePoint databases and search indexes, Storage
Manager BLOB data and Connector BLOB data, and verification of SnapVault targets
•
Configure multiple schedules for different restore granularity levels in a single backup
plan
•
Separately schedule verification jobs apart from backup or restore jobs
•
Separately schedule granular indexing jobs apart from backup jobs
•
Ability to browse and restore individual items from backup directly without generating
an index at backup time
•
Different retention settings for the same backup components in multiple plans
•
Extend contents from the primary SQL content database storage to more affordable file
system based locations (for example, NetApp CIFS devices) leveraging RBS
SMSP 8.1 Platform Backup and Restore User’s Guide
•
End-user-initiated archiving can delete historical contents (from items to site
collections), or move them based on fully customizable business rules or an on-demand
basis with tiered storage management and the support of backup and recovery
•
Connector can attach any NetApp CIFS Share to SharePoint, taking advantage of all
SharePoint content management and presentation features without any ingestion of
content into the SharePoint content database
•
Integration with NetApp SnapLock technology
•
Integration with NetApp ASUP system for streamlined support
•
Integration with SCOM (Microsoft System Center Operations Manager) event log
•
Support to backup and restore FAST Search Server Farms
In addition, SnapManager for SharePoint offers the option to evaluate various DocAve products for 90
days, including Migration, Granular Backup and Restore, Administration, Compliance products, and
Report Center.
SMSP 8.1 Platform Backup and Restore User’s Guide
7
About Platform Backup and Restore
Platform Backup and Restore protects your organization from disasters with a comprehensive toolset for
backing up and restoring your entire SharePoint environment. Platform Backup and Restore backs up all
content, customizations, solutions, and features, as well as back-end SQL databases, all configurations,
index/job servers, front-end IIS settings, file system resources, and custom application databases. It
allows for restore of an entire platform or individual SharePoint environment components.
It is important to fully understand the implications of using NetApp storage volumes and their LUNs
during the backup and restore process. During the backup process, a snapshot backup is created for
SharePoint databases and SharePoint index files; these snapshots are stored in a NetApp storage
volume. The backup set can contain one or multiple Data ONTAP® LUNs with multiple databases.
During backup, SnapManager for Microsoft SQL Server is used to perform database snapshot backups
and SnapDrive is used to perform SharePoint index snapshot backups. The backup data of the other
SharePoint components is sent to the configured storage policy and stored together with the backup job
metadata and index.
*Note: If SharePoint databases share a same LUN with SQL Server system databases, only stream-based
backup and restore can be utilized. SnapManager for SharePoint does not support this configuration.
Always put SharePoint databases on LUNs separate from the SQL Server system database LUN.
*Note: SnapManager for SharePoint also supports VMDK disks. These disks interact with SMSP
identically to LUNs, except that SnapVault integration is not supported on VMDK disks. In the following
sections, all the areas that mention LUNs will also apply to VMDK disks. For more information about
VMDK disks, refer to the SnapDrive Installation and Administration Guide.
8
SMSP 8.1 Platform Backup and Restore User’s Guide
Figure 1: Platform Backup and Restore data flow diagram.
SMSP 8.1 Platform Backup and Restore User’s Guide
9
Before You Begin
Refer to the SnapManager for SharePoint Installation Guide for system and farm requirements that
must be in place prior to installing and using Platform Backup and Restore.
Configuration
In order to use Platform Backup and Restore, the SnapManager for SharePoint platform must be
installed and configured properly on your farm. Platform Backup and Restore will not function without
SnapManager for SharePoint present on the farm.
Agents
SnapManager for SharePoint Agents are responsible for running SnapManager for SharePoint jobs and
interacting with the SharePoint object model. For more information on SnapManager for SharePoint
Agents, refer to the SnapManager for SharePoint Installation Guide.
Permissions
Refer to the SnapManager for SharePoint Installation Guide for information on the required Platform
Backup and Restore permissions.
AvePoint recommends using Health Analyzer to verify that you meet the prerequisites necessary to use
SnapManager for SharePoint Platform Backup and Restore.
*Note: Only users in the SnapManager for SharePoint Administrators group can use Health Analyzer.
For more information about Health Analyzer, refer to the SnapManager for SharePoint Control Panel
User’s Guide.
10
SMSP 8.1 Platform Backup and Restore User’s Guide
Getting Started
Refer to the sections below for important information on getting started with Platform Backup and
Restore.
Launching Platform Backup and Restore
To launch Platform Backup and Restore and access its functionality, follow the instructions below:
1. Log in to SnapManager for SharePoint. If you are already in the software, click the Platform tab.
2. From the Platform tab, click Data Protection to view the backup modules.
3. Click Platform Backup & Granular Restore to launch this module.
Figure 2: SnapManager for SharePoint module launch window.
SMSP 8.1 Platform Backup and Restore User’s Guide
11
User Interface Overview
The Platform Backup and Restore user interface launches with the Backup tab active. This tab displays
your farm environment and allows for quick access to a list of Platform Backup and Restore features.
Figure 3: Platform Backup and Restore user interface.
1. The SharePoint tree (Scope panel) displays all content within your farms. Use this panel to
select the content that you wish to perform actions on. Selecting content often reveals new tabs
and functionality on the ribbon.
2. The ribbon shows the available actions and wizards for the selected nodes. This content is
dynamic; it will often change depending on what is selected on the SharePoint tree.
3. The workspace shows all form-based content that is used during the configuration of actions
performed in SnapManager for SharePoint products.
*Note: Maintenance jobs will not be counted in the workspace Dashboard.
12
SMSP 8.1 Platform Backup and Restore User’s Guide
Notes for Customers Updating to SharePoint 2013
If you are running SMSP Platform Backup and Restore with SharePoint 2010 and plan on updating to
SharePoint 2013, take the following information into consideration when planning your update:
•
Customers leveraging Platform Backup and Restore will need to install SMSP Agents and
create new data protection plans in the new SharePoint 2013 environment.
•
Customers must retain the legacy SharePoint 2010 platform for item-level recovery
from legacy (pre-migration) backup data.
•
The platform will not support restoring SharePoint 2010 data “out of place” to a
SharePoint 2013 farm.
SMSP 8.1 Platform Backup and Restore User’s Guide
13
Configuring Devices and Setting up Storage Policies
In order to perform a backup job using Platform Backup and Restore, it is necessary to first configure
one or more physical/logical devices and then set up a storage policy.
SnapManager for SharePoint has the ability to treat multiple NetApp LUNs and CIFS shares as a single
logical unit when saving backup data. This is especially useful for very large backup plans, as many small
drives can be combined. A storage policy must be defined before creating a backup plan.
Platform Backup and Restore can only write to a Data ONTAP device.
For instructions on defining devices and setting up storage policies, refer to the SnapManager for
SharePoint Control Panel User’s Guide.
14
SMSP 8.1 Platform Backup and Restore User’s Guide
About the Verification and Index Policy
If you do not want to use the default SQL Server for backup verification and index generation, you can
set up a verification and index policy to use one or more SQL Servers.
Configuring a Verification and Index Server Profile
To configure a verification and index server profile, complete the steps below:
1. Click Verification and Index Policy in the Settings group on the Backup or Restore tab. The
Verification and Index Policy Configuration window appears.
Figure 4: Selecting Verification and Index Policy from the Backup tab.
2. Click Create from the Manage group, and then select the Verification and Index Server from the
drop-down list. The Verification and Index Policy Configuration page appears. Configure the
following settings:
Figure 5: Selecting Verification and Index Server from the drop-down list.
SMSP 8.1 Platform Backup and Restore User’s Guide
15
Figure 6: Configuring the Verification and Index Server profile.
a. Verification and Index Server Profile Name – Enter a Name and optional Description for
the verification and index server profile.
b. Server Name – Enter a SQL Server name or instance to be used as the server for
verification and index generation in the Server Name field. The format is Server or
Server\Instance.
*Note: SnapManager for SQL Server must be installed on the verification server.
c. Database Access Credentials – Select the authentication method used to create the
database.
o
Windows authentication (recommended) (the default option) – Use this
method to confirm the user identity using Windows.
o
SQL authentication – SQL Server confirms the user identity according to the
selected Managed Account. The designated account must be added to the
sysadmin role in SQL Server.
d. Allow all Farms to Use this Server – By default, all farms are allowed to use the
specified server for the backup verification and index generation. To choose the farms
16
SMSP 8.1 Platform Backup and Restore User’s Guide
where you want to use this verification and index server, click the Farm drop-down list
and select the specified farms.
e. Click OK to save the configured verification and index server profile. Otherwise, click
Cancel.
Configuring a Verification and Index Server Group Profile
Verification and index server group enables you to use more than one SQL Server for database backup
verification and index generation. To configure a verification and index server group, complete the steps
below:
1. Click Verification and Index Policy in the Settings group on the Backup or Restore tab. The
Verification and Index Policy Configuration window appears.
2. Click Create from the Manage group, and then select the Verification and Index Server Group
from the drop-down list. The Verification and Index Policy Configuration page appears.
Configure the following settings:
Figure 7: Configuring the Verification and Index Server Group profile.
SMSP 8.1 Platform Backup and Restore User’s Guide
17
a. Verification and Index Server Group Profile Name – Enter a Name and optional
Description for the verification and index server group profile.
b. Farm – Select a farm from the drop-down list to load and create the verification and
index servers.
c. Database Server Mappings – Configure the mappings for the SQL Servers and
verification and index servers. The verification and index server specified for the
corresponding SQL Server will mount the temporary database to the specified mount
point directory to verify the backed up database and generate the granular index.
Complete the steps below:
i.
In the Database Server Mappings field, click Add on the left-corner to add a
mapping into the table.
ii.
Select a SQL Server from the SQL Server drop-down list, and then select a
verification and index server profile from the Verification and Index Server
Profile drop-down list. Enter the mount point directory for mounting the
temporary database on the specified verification and index server. You can
perform the following actions on the configured mappings:

Delete – Delete the selected mappings.

Clear Selection – Clear all of the selections.
3. Click OK to save the configured verification and index server group profile. Otherwise, click
Cancel.
18
SMSP 8.1 Platform Backup and Restore User’s Guide
Command with Operation
For a SnapManager for SharePoint database backup, restore, or verification operation, you have the
option to automatically run a command before the operation starts or after the operation completes.
Enabling the Run command with operation option prompts you to select a command profile, which
must be configured before the backup, restore, or verification operation can begin.
A command profile contains the following information:
•
The type of the command, which is either a Pre-Operation command or Post-Operation
command
•
The host system from which the command is to be run
•
The full path of the command that you want SMSP to run before or after the database
backup, restore, or verification operation
•
Any parameters that are to be passed to the command
•
Because the command (your own program or script) is invoked from within the context
of a specific database backup, restore, or verification, you can pass the command
information about the components of that operation. In your script, any occurrence of
the text string %1 corresponds to the first parameter passed; the text string %2
corresponds to the second parameter, and so on.
After you have completed configuring the command and parameters, the database backup, restore, or
verification operation can be started.
*Note: The Post-Operation command or script will run only after a successful backup, restore, or
verification. If the backup or restore is not completed successfully, or if the verification fails, then the
Post-Operation command or script is not run.
SMSP 8.1 Platform Backup and Restore User’s Guide
19
Configuring a Command Profile
To configure a command profile:
1. Click Command With Operation in the Settings group on the Backup tab. The Command With
Operation window appears.
2. Click Create from the Manage group. The Create a New Command Profile window appears.
Figure 8: Create a New Command Profile window.
3. Enter a Name for the command profile and select one or more Agents where you want to Run
command with operation. Then, click the Configure button on the ribbon. You can also click the
Configure link following the Agent name in the Agent column to configure the detailed settings
for only that Agent.
4. Select the Operation Type for the command profile. The operation type specifies when this
command profile can be loaded.
5. If desired, configure the Pre-Operation Command settings.
a. Run Pre-command or Script ─ Select the Run pre-command or script before the
SnapManager Operation starts checkbox to enable the pre-operation function.
b. Pre-command Errors ─ If the Treat pre-command errors as fatal by stopping the
remaining SnapManager operations option is selected, the backup, restore, or
verification operation will not run if the pre-command does not complete successfully.
20
SMSP 8.1 Platform Backup and Restore User’s Guide
c. Specify a Computer ─ Specify the hostname or IP address of one computer where you
want to run the command (your own program or script) in the Specify a computer to
run command textbox.
d. Specify a Program or Script ─ Specify the full path to the command in the Specify a
program or script you want to run textbox.
e. SnapManager Variables and Command Arguments ─ Select the sequence of
SnapManager variables that you want to pass to the command in the SnapManager
variables field, and then click Add to Command Arguments to add the selected
variables to the Command arguments field.
6. If desired, configure the Post-Operation Command settings.
a. Run Post-command or Script ─ Select the Run post-command or script after the
SnapManager Operation completes checkbox to enable post-operation function.
b. Post-command Errors ─ If the Treat post-command errors as fatal by stopping the
remaining SnapManager operations option is selected, the backup, restore, or
verification operation will be considered failed if the pre-command does not complete
successfully.
c. Specify a Computer ─ Specify the hostname or IP address of one computer where you
want to run the command (your own program or script) in the Specify a computer to
run command textbox.
d. Specify a Program or Script ─ Specify the full path to the command in the Specify a
program or script you want to run textbox.
e. SnapManager Variables and Command Arguments ─ Select the sequence of
SnapManager variables that you want to pass to the command in the SnapManager
variables field, and then click Add to Command Arguments to add the selected
variables to the Command arguments field.
7. Click OK to save the configuration; you will be redirected to the Create a New Command Profile
page.
8. Click OK to save the configured command profile; you will be redirected to the Command With
Operation page.
9. In the Command With Operation page, you can choose to edit the created command profiles or
delete the command profiles that are no longer useful.
SMSP 8.1 Platform Backup and Restore User’s Guide
21
Command Arguments Used to Pass Information to the Program or
Script
The Run command with operation feature supports the following variables, which can pass operationspecific information to your program or script.
Variable
$SqlSnapshot
Description
Expands to the name of a SQL Server database
Snapshot copy. This argument is used for backup and
verification operations.
Examples:
sqlsnap winsrvr2 01-31-2005_15.03.09
sqlsnap_winserver_recent
*Note: The number of database Snapshot copies in a
SnapManager backup set depends on the number of
volumes used to store the databases included in the
backup.
For a restore operation, this argument specifies the
name of the Snapshot copy to be restored.
Example:
sqlsnap winsrvr2 01-31-2005_15.03.09
sqlsnap winsrvr2 recent
$InfoSnapshot
Expands to the name of a SnapInfo directory
Snapshot copy.
Examples:
sqlinfo winsrvr2 01-31-2005_15.03.09
sqlinfo winsrvr2 recent
$SnapInfoName
Expands to the name of the SnapInfo directory.
Examples:
WINSRVR2 recent
WINSRVR2_11-23-2004_16.21.07 Daily
*Note: If you use this variable, you must also provide
the correct path to the directory.
$SnapInfoPath
22
Expands to the name of the SnapInfo subdirectory.
SMSP 8.1 Platform Backup and Restore User’s Guide
Variable
Description
This argument is used in backup and verification
operations.
Example:
I:\SMSQL_SnapInfo\SQL WINSRVR2\DB North wind
For restore operation, this argument specifies the
path to the Snapshot copy information metadata that
is being used for the database restore.
Example:
U:\SMSQL_SnapInfo\VDISK E\FG \05-142010_15.33.41\SnapInfo 05-142010_15.33.41.sml
$LogBackupFile
Expands to the full path name of the transaction log
backup file.
Example:
I:\SMSQL_SnapInfo\SQL WINSRVR2\DB North
wind\LogBackup\ 11-012004_13.34.59 Northwind.TRB
$Database
Specifies the logical name of the database processes.
*Note: To prevent PowerShell from interpreting the
value of this parameter, be sure to enclose the entire
parameter value with single quotes. For example,
PreCmdArg ‘$Database $ServerInstance’
Example:
DatabaseAccounting
If you want to have more than one database
expanded, repeat the parameter as many times as
you want.
Example:
AccountingDB1 AcmeServer1/SqlInst1
FinanceDB2
AcmeServer1/SqlInst2
SMSP 8.1 Platform Backup and Restore User’s Guide
23
Variable
$ServerInstance
Description
Specifies the name of the SQL Server instance that is
actually processed.
Example:
ACMESERVER1\SQLINSTANCE1
$OperationStatus
Provides the status of the SMSQL operation.
Example:
5234
$PreCommandStatus
Provides the pre-command status to the postcommand if the post-command is executed based on
the status of the earlier pre-command.
Example:
5234
*Note: Several parameters like the $SnapInfoPath and $LogBackupFile variables are automatically
enclosed within double quotes so that the actual path name can contain spaces without affecting the
script invocation on the Windows command line. If you do not want the double quotes to appear in your
command line, remove them from the Command arguments field.
The following are some helpful notes on the Command with Operation function:
24
•
The machine specified in the Specify a computer to run command textbox must have
SMSQL installed to run the command.
•
If SMSQL 5.2P1 or higher is on a machine running a database backup, restore, or
verification job, both the pre-command and the post-command are executed.
SMSP 8.1 Platform Backup and Restore User’s Guide
Migrator Tools
SharePoint databases/indexes must be located on storage systems running Data ONTAP (LUNs and CIFS
shares) for them to be backed up by SnapManager for SharePoint. If SharePoint databases/indexes are
not located on storage systems running Data ONTAP, then they must be migrated to these storage
systems.
Use SnapManager for Microsoft SQL Server (SMSQL) to migrate SQL Server databases from a local disk
to storage systems running Data ONTAP, as well as separate the database files and log files onto
separate LUNs.
The SnapManager for SharePoint’s Migrate Index tool can be used to facilitate the index migration
process. You can find the Migrate Index tool by navigating to SnapManager for SharePoint > Platform
Backup & Granular Restore > Platform Backup.
The SnapManager for SharePoint Migrate Index tool provides a way of moving SharePoint indexes to
LUNs. Clicking the Migrate Index button on the ribbon will lead you to the Migrate Index Wizard.
Migrate Database
The Migrate Database tool migrates SharePoint databases to Data ONTAP storage systems (LUNs). Such
databases include the SharePoint Configuration database, service application database, or Web
application content database. With this feature you can also move a database from local disk to an SMB
share.
*Note: The Migrate Database tool does not support the migration of the databases in the AlwaysOn
Availability Group and the SQL Mirroring Databases.
*Note: SharePoint services on all servers in the farm will be automatically stopped during the migration
process. Services are restarted after completion of the migration. For servers in the farm that do not
have SnapManager for SharePoint Agents installed, you must stop the services before you click Start and
then restart the services manually after the migration job is finished.
To access the Migrate Database tool, click Migrate Database in the Migrator Tools group on the Backup
tab. To use the Migrate Database tool, complete the steps below:
1. Migrate Database ─ In the Farm Selection field, select the farm that contains the SharePoint
databases you want to migrate. All of the SnapManager for SharePoint Agents installed on the
SQL Servers of the specified farm are loaded in the Agent Selection field. Choose one Agent
from the Agent selection drop-down list to migrate the databases on the specified Agent server.
2. Click Next. The Database Association page appears.
3. Database Association ─ Select the checkbox of the database or the database file that you want
to migrate. The To (Available Disk) field becomes enabled. Select a LUN from the To (Available
SMSP 8.1 Platform Backup and Restore User’s Guide
25
Disk) drop-down list. The selected database will be migrated from the location displayed in
From (Location) to the LUN specified in the To (Available Disk) field.
Figure 9: The Database Association interface.
4. Click Next. The SnapInfo Directory Types page appears.
5. SnapInfo Directory Types ─ Select the SnapInfo directory types from Single SnapInfo Directory
and Advanced SnapInfo Directories.
•
Single SnapInfo Directory ─ All of the SQL instances are forced to use the same SnapInfo
directory after the migration.
•
Advanced SnapInfo Directories ─ You can configure different SnapInfo directories for
different SQL intances after the migration.
6. Click Next; the Set Up SnapInfo Directory page appears.
7. Set Up SnapInfo Directory ─ In the Available Disk field, select the SnapInfo directory for the
specified SQL Server instance. The current SnapInfo directory is displayed in the Snap Info
column in the table; the newly defined SnapInfo directory will be displayed in the Result
SnapInfo Directory field.
8. Click Next and the Notification page appears.
9. Notification ─ To inform specified users of the database migration job, configure the
Notification settings. Select a previously configured notification profile from the Select a profile
with address only drop-down list, or create a new e-mail notification profile by clicking the New
Notification Profile link. Click View to view the detailed configuration of the selected
notification profile.
10. After you are satisfied with the configuration, click Start to start the database migration job.
26
SMSP 8.1 Platform Backup and Restore User’s Guide
Migrate Index
The Migrate Index tool is used for migrating the SharePoint Foundation Help Search index and Search
Service Application index to a LUN.
1. Click Migrate Index in the Migrator Tools group on the Backup tab. The Migrate Index page
appears.
Figure 10: The Migrate Index screen.
Complete the steps below:
2. Migrate Index ─ In the Farm Selection field, select the farm that contains the SharePoint indexes
you want to migrate. All SnapManager for SharePoint Agents installed on the SharePoint
Foundation Help Search index server and Search Service Application index server are loaded in
the Agent Selection field. Choose one Agent from the Agent selection drop-down list to migrate
the indexes on the specified Agent server.
*Note: SharePoint Foundation farms will not be loaded in the Farm Selection drop-down list, as
the Migrate Index tool does not support migrating SharePoint Foundation farm index files.
3. Click Next. The Index Association page appears.
4. Index Association ─ Select the checkbox of the index you want to migrate. The To (Available
Disk) field becomes enabled. Select a LUN from the To (Available Disk) drop-down list. The
selected index will be migrated from the location displayed in From (Location) to the LUN
specified in the To (Available Disk) field.
5. Click Next. The Notification page appears.
6. Notification ─ To inform specified users of the index migration job, configure the Notification
settings. Select a previously configured notification profile from the Select a profile with
address only drop-down list, or create a new e-mail notification profile by clicking the New
Notification Profile link. Click View to view the detailed configuration of the selected
notification profile.
7. After you are satisfied with the configuration, click Start to start the index migration job.
SMSP 8.1 Platform Backup and Restore User’s Guide
27
*Note: To create a new content database, create a new empty SQL database using the
LATIN1_General_CI_AS_KS_WS collation and move it onto the storage system that is running Data
ONTAP. Next, in Microsoft SharePoint, choose to create a new content database and point it to the precreated databases. For more information regarding this option, consult Microsoft SharePoint
documentation. This is the recommended approach when storage admins and SharePoint admins are
different people/teams. For more information, refer to Microsoft article Deploy by using DBA-created
databases (SharePoint Foundation 2010).
28
SMSP 8.1 Platform Backup and Restore User’s Guide
Selecting Content to Back Up
After launching the Platform Backup and Restore user interface, the Scope panel on the left of the
screen displays the root node of the farm. Note that you cannot select nodes on both a SharePoint 2010
tree and SharePoint 2013 tree simultaneously.
Figure 11: SharePoint 2010 tree and SharePoint 2013 tree.
Figure 12: SharePoint 2010 tree and SharePoint 2013 tree.
To select the content to back up:
1. Click the farm node to expand the tree; this displays all SharePoint components (databases,
services, solutions, etc.) that can be backed up.
•
By default, the Verify Storage Layout option is selected, which means that
SnapManager for SharePoint tries to obtain information for all databases and indexes
regarding storage from SnapManager for Microsoft SQL Server and SnapDrive,
SMSP 8.1 Platform Backup and Restore User’s Guide
29
respectively. This process may take some time to complete, depending upon the
number of databases on the SQL Servers.
•
When the Verify Storage Layout option is not selected, SnapManager for SharePoint will
retrieve only the farm tree structure from SharePoint, which means that the farm tree
loads faster. However, because the storage layout is unknown in this case, you must
ensure that all components are correctly configured on the LUN.
•
If the Verify Storage Layout option is selected, certain icons are displayed to indicate
the storage status, as shown in the following table.
Type
In LUN or on SMB 3 Share
with SnapMirror and
SnapVault enabled
In LUN or on SMB 3 Share
with SnapMirror enabled
In LUN or on SMB 3 Share
with SnapVault enabled
In LUN or on SMB 3 Share
Invalid. No database or index
in LUN, or no database on
SMB 3 Share
Browse the tree without
selecting the Verify Storage
Layout option, or unknown
error occurs while browsing
No Agent is installed, the
database cannot be backed
up
Database
Index
*Note: If any newly created SharePoint objects are not displayed in the tree, right-click the root
Farm (Farm name) node and click Refresh to refresh the tree.
2. If desired, select the Include New node to include any newly created SharePoint objects (child
nodes) in the Platform backup plan. By default, the Include New node is selected for each Web
application. The nodes that support the Include New function are:
30
•
Farm
•
Windows SharePoint Solutions
•
Microsoft SharePoint Foundation Web Application and the Web Application nodes
below it
•
Shared Service Applications
•
Shared Service Proxies
SMSP 8.1 Platform Backup and Restore User’s Guide
•
InfoPath Form Services
o
Data Connections
o
Form Templates
o
Exempt User Agents
3. In the screenshot below, the following SharePoint objects will be backed up by the Platform
backup plan:
•
Newly created Web applications under the Microsoft SharePoint Foundation Web
Application node (because Include New is selected)
•
Any existing or newly added content databases of the selected/newly created Web
applications under the Microsoft SharePoint Foundation Web Application node
•
The SharePoint - 3000_clone and SharePoint - 40000 Web applications
Figure 13: Selecting SharePoint farm content.
4. After selecting content, you are able to build a backup plan using Platform Backup and Restore.
SMSP 8.1 Platform Backup and Restore User’s Guide
31
Using the Custom Database Feature
Use the Custom Database feature to manually add to the SharePoint component tree any custom
databases that are not listed. Such databases include the database of a solution, the database of third
party software, and so on.
It is required that custom databases be on NetApp LUNs in order for them to properly function with
SnapManager for SharePoint. A custom database can be on a SQL Server that is separate from the one
that the farm uses as long as the servers have SMSP Agents installed on them and the database is on a
LUN.
After a custom database is added to the tree, it can be backed up normally.
1. On the Backup tab, in the Settings group, click Custom Database. The Custom Database
window appears.
Figure 14: Custom Database window.
2. In the Custom Database window, click the Custom Database node on the right panel to expand
the tree. All custom databases on all of the SQL Servers that have SnapManager for SharePoint
Agents installed are listed under the corresponding SQL instance node in the tree.
32
SMSP 8.1 Platform Backup and Restore User’s Guide
3. Select the databases that you want to be displayed on the backup tree by selecting the checkbox
next to the database.
4. When finished, click OK. The selected database is now shown on the backup tree under the
Custom Database node.
Figure 15: Custom Database node.
SMSP 8.1 Platform Backup and Restore User’s Guide
33
SharePoint Components Supported for Backup
SnapManager for SharePoint Platform Backup and Restore supports backup of the following SharePoint
2010 components:
•
All SharePoint databases – The configuration database, Central Administration content
database, content databases, State Service database, Application Registry Service
Database, Shared Service Application Database, and search database are supported.
These databases are backed up by the SQL Member Agent using Platform Backup.
•
Database master key – When backing up the database, only the database master key
encrypted by the service master key will be backed up with the database.
•
SharePoint search index – This includes the Server Search index. The search index files
are backed up on Index Member Agent.
•
SharePoint components and settings – This includes Web applications, InfoPath Forms
Services, State Service, Microsoft SharePoint Foundation Sandboxed Code Service,
Microsoft SharePoint Server Diagnostics Service, Microsoft SharePoint Foundation
Diagnostics Service, Application Registry Service, Shared Service Applications, Shared
Service Proxies, Global Search Settings, and Managed Metadata Service.
•
SharePoint solutions – This includes any SharePoint customizations deployed to
SharePoint in the form of solutions. These solutions and their deployment statuses are
backed up.
•
Nintex databases – This includes Nintex workflow 2010 configuration database, content
database, and solutions.
•
NewsGator – This includes NewsGator Social Platform Services (including corresponding
databases), NewsGator Social Platform Services Proxy, and solutions.
*Note: Social Sites (NewsGator) 1.2 and 2.5 for SharePoint 2010 are supported by
SnapManager for SharePoint.
•
KnowledgeLake – This includes KnowledgeLake Imaging Data, KnowledgeLake Service
Application, KnowledgeLake Proxy, and solutions.
•
SharePoint front-end resources – The front-end Member Agent backs up the IIS settings
(both metadata and files), SharePoint site definitions, SharePoint hive files, Global
Assembly Cache files, custom features, and extra file system folders.
•
FAST Search Server Farms – FAST Search Server Farms backup is supported.
SnapManager for SharePoint Platform Backup and Restore supports backup of the following SharePoint
2013 components:
•
34
All SharePoint databases – The configuration database, Central Administration content
database, content databases, State Service database, Shared Service Application
SMSP 8.1 Platform Backup and Restore User’s Guide
Database, and search database are supported. These databases are backed up by the
SQL Member Agent using Platform Backup.
•
Database master key – When backing up the database, only the database master key
encrypted by the service master key will be backed up with the database.
•
SharePoint search index – This includes the Server Search index. The search index files
are backed up on Index Member Agent.
•
SharePoint components and settings – This includes Web applications, InfoPath Forms
Services, State Service, Microsoft SharePoint Foundation Sandboxed Code Service,
Microsoft SharePoint Server Diagnostics Service, Microsoft SharePoint Foundation
Diagnostics Service, Shared Service Applications, Shared Service Proxies, Global Search
Settings, and Managed Metadata Service.
•
SharePoint solutions – This includes any SharePoint customizations deployed to
SharePoint in the form of solutions. These solutions and their deployment statuses are
backed up.
•
Nintex databases – This includes Nintex workflow 2013 configuration database, content
database, and solutions.
•
NewsGator 4.0 – This includes the Enrich Service, News Stream Service, Social Platform
Service, and Video Steam Service (including corresponding databases), proxies, and
solutions.
*Note: Social Sites (NewsGator) 4.0 for SharePoint 2013 is supported in SnapManager
8.1 for SharePoint and later versions.
•
SharePoint front-end resources – The front-end Member Agent backs up the IIS settings
(both metadata and files), SharePoint site definitions, SharePoint hive files, Global
Assembly Cache files, custom features, and extra file system folders.
*Note: The Office 2013 Web Apps Server is not supported to be backed up and restored
by SnapManager for SharePoint Platform Backup and Restore.
*Note: Some components have multiple related sub-components that must be backed-up together. For
example, the service application must be backed up with its connection type in order to perform a
successful restore of these components.
*Note: SnapManager for SharePoint does not include system backups such as AD backup and System
State backup. Therefore, the SharePoint customizations’ external dependencies are not backed up.
Typically, such customizations are deployed through an installer or configured manually and require the
use of some binaries, registry entries and so on.
SMSP 8.1 Platform Backup and Restore User’s Guide
35
Using Plan Builder to Back Up Data
Use the Plan Builder to schedule a backup job.
*Note: By default, SnapManager for SharePoint backs up databases and index components in parallel.
To modify this behavior, you must manually edit a configuration file. For details, refer to Backing up
Databases First, and then Index Components.
To use Plan Builder:
1. After selecting the content to back up, click Plan Builder from the Backup tab.
2. From the drop-down menu, select Wizard Mode for step-by-step guidance during configuration,
or select Form Mode (recommended for advanced users only) to set up a plan quickly.
See the section below applicable to your choice.
Using Wizard Mode to Create a Backup Plan
Wizard Mode provides you with step-by-step guidance on how to configure a new plan. Follow the
instructions below to configure a plan using Wizard Mode. Note that a red * in the user interface
indicates a mandatory field or step.
1. Enter a Plan Name and optional Description, if desired. Then choose whether to Create a new
plan or Copy saved plan settings from template to start from a previously saved plan template.
Figure 16: Creating a plan in Wizard Mode.
2. Click Next. The Storage Policy page appears.
36
SMSP 8.1 Platform Backup and Restore User’s Guide
3. Select a Storage Policy from the drop-down list, or choose to set up a new storage policy by
clicking the New Storage Policy link. Click the here link to display detailed information of the
Primary Storage, Total Space, Free Space, and The number of physical device(s) attached in the
area below.
*Note: Please make sure the user credentials designated for the Storage System Profile are
correct before performing a Platform Backup job.
Figure 17: Selecting a Storage Policy.
4. Click Next. The Advanced page appears.
Figure 18: Configuring the Advanced page.
a. Enable Offloaded Data Transfer ─ Choose whether or not to enable Offloaded Data
Transfer to speed up copy and move operations. To enable offloaded data transfer,
select Yes; otherwise, select No. For more details on Offloaded Data Transfer, refer to
http://msdn.microsoft.com/en-us/library/windows/hardware/hh833784.aspx.
*Note: Offloaded Data Transfer (ODX) supports Web front-end data and the FAST
Search data (the FAST Search data stored in LUN is not supported), but ODX does not
SMSP 8.1 Platform Backup and Restore User’s Guide
37
support data in a database snapshot. For details on these limitations, refer to
http://msdn.microsoft.com/en-us/library/windows/hardware/dn265282(v=vs.85).aspx.
b. Associated Plan Group ─ Select the plan groups from the drop-down list to add the plan
to the corresponding groups. The added plan will run according to the related plan
group settings. You can also choose to create a new plan group by clicking the New Plan
Group link in the drop-down list. For more information on plan groups, refer to the
SnapManager for SharePoint Control Panel User’s Guide.
c. To inform users of the Platform Backup job, configure the Notification settings. Select a
previously configured notification profile from the Select a profile with address only
drop-down list, or choose to create a new e-mail notification profile by clicking the New
Notification Profile link. Click View to view the detailed configuration of the selected
notification profile.
d. Agent Group – Select an Agent group from the drop-down menu. The selected Agent
group will execute the backup job and load balance, which improves performance. Click
View to view the details of the selected Agent group.
5. Click Next. The Schedule page appears.
6. Define the Schedule type selection:
Figure 19: Configuring a schedule.
38
SMSP 8.1 Platform Backup and Restore User’s Guide
•
No schedule – Select this option to run the plan manually, and the plan will be saved in
Plan Manager.
•
Configure the schedule myself – Select this option to configure a customized schedule,
and run the backup job by schedule. Click Add Schedule to set up a schedule. The Add
Schedule window appears. Configure the settings in the Options, Advanced and Time
tabs according to the detailed information in each section. Refer to Backup Schedule for
more information on adding a schedule.
After configuring the schedule for the Platform Backup, click Calendar View to view the
scheduled jobs by Day, Week, or Month. All of the schedules will be displayed in the
Summary table. Click X to delete a schedule.
7. Click Next. The Maintenance page appears.
8. Configure the Maintenance Options to be performed on the snapshots during the maintenance.
9. Index last … deferred indexing ─ This option generates indexes for backup jobs that have the
Defer Indexing to maintenance jobs option selected. After selecting this option, enter the
number of jobs for which indexes will be generated. For example, setting this option to Index
last 3 deferred indexing will generate the indexes for the most recent three backup jobs that
have a Finished/Finished with Exception status.
a. Clone database on SnapMirror destination ─ Use this option to clone a database based
upon the Snapshot copy on the SnapMirror destination volume.
b. Clone database on SnapVault destination ─ Use this option to use the remote backup to
perform the clone operation. Snapshots saved in SnapVault primary storage are
considered Local Backups and snapshots saved in SnapVault secondary storage are
considered Remote Backups.
c. Granularity index server ─ Choose the verification and index server or server group
used for generating the granular level restore index. To generate the granular level
index, SMSP uses the SQL Server that contains the data to be backed up by default. You
can click the New Index Server link in the drop-down list to create a new indexserver.
For more information, refer to About the Verification and Index Policy.
d. Assign Mount Point ─ If you do not want to use the default mount point directory, use
this option to specify the mount point directory on which a backup set will be mounted
during generating the granular level restore index. For example: C:\mountpoint.
*Note: A volume mount point is a drive or volume in Windows that is mounted to a
folder that uses the NTFS file system. A mounted drive is assigned a drive path instead
of a drive letter. Volume mount points enable you to exceed the 26 drive letter
limitation. By using volume mount points, you can mount a target partition onto a folder
on another physical disk.
e. BLOB Settings ─ Select which options to perform on the device that stores the original
BLOB data after the BLOB backup completes. The SnapMirror destination of the device
that stores the original BLOB data will be updated.
SMSP 8.1 Platform Backup and Restore User’s Guide
39
f.
Storage Policy Settings ─ Select which options to perform on the device configured in
the storage policy after the backup operation completes. The SnapMirror destination of
the device configured in the storage policy will be updated.
10. Verify last … unverified backup(s) ─ Select this option to specify how many unverified backup
jobs to verify. Enter a positive integer in the provided field.
a. Verification Server ─ Select the server or server groups used for verifying the backed-up
database. By default, the default verification server is used. You can click the New
Verification Server link in the drop-down list to create a new verification server. For
more information, refer to About the Verification and Index Policy.
b. Assign Mount Point ─ If you do not want to use the default mount point directory, use
this option to specify the mount point directory on which a backup set will be mounted
during database verification. For example: C:\mountpoint.
*Note: If you are using a clustered instance of SQL, the mount point LUN needs to be a
shared LUN in the SQL cluster.
c. Scripts ─ If you selected the Run command with operation option, the Verify operation
type command profile will be listed in the drop-down list. Select a command profile
from the drop-down list to run the commands according to the command profile you
selected. You can also click the New Command Profile link in the drop-down list to
create a new command profile. For more information, refer to Command with
Operation.
d. BLOB Settings ─ Select which options to perform on the device that stores the original
BLOB data after the BLOB backup completes. The SnapMirror destination of the device
that stores the original BLOB data will be updated.
e. Database Settings ─ Configure the SnapMirror-/SnapVault-related settings for the
backed-up databases.
o
o
SnapMirror ─ Choose the operations to perform on the SnapMirror destination
after completion of the database backup.

Update SnapMirror after operation ─ Use this option if you are using
backups that reside on volumes configured as SnapMirror sources. This
option updates the SnapMirror destination after the backup operation
is complete.

Verify on available SnapMirror destination volumes ─ Use this option
to verify the database on the SnapMirror destination volume.
SnapVault ─ Choose the operations to be performed on the SnapVault storage
system after completion of the database backup.
*Note: Prior to using this option in a backup plan, the SnapVault datasets must
have already been created by SMSQL and in a conformant state. For more
40
SMSP 8.1 Platform Backup and Restore User’s Guide
information on configuring the SnapVault datasets, refer to the SnapManager
for Microsoft SQL Server Installation and Administration Guide.
f.

Verify archive backup on secondary storage ─ Use this option to verify
the database archived on the secondary storage system.

Archive backup to secondary storage ─ Choose whether you want to
retain backups at the archived location on an Hourly, Daily, Weekly,
Monthly, or Unlimited basis.
Storage Policy Settings ─ Select which options to perform on the device configured in
the storage policy after the backup operation completes. The SnapMirror destination of
the device configured in the storage policy will be updated.
*Note: If you select a Maintenance Option, you must configure a schedule for running
the maintenance jobs.
*Note: You can also perform maintenance jobs manually in Job Monitor. For more
information, refer to Manual Maintenance.
11. Maintenance Schedule – Define the Schedule type selection for scheduled maintenance jobs.
Note that you can only perform a maintenance job on Finished and Finished with Exception
backup jobs whose Index Status is not Successful.
•
No schedule – Run the maintenance job manually. Select this option if you want to run
the maintenance job manually in Job Monitor after the corresponding backup job
completes.
•
Configure the schedule myself – Select this option to configure a customized schedule,
and run the maintenance job by schedule. Click Add Schedule to create a schedule. The
Add Schedule window appears. After configuring the schedule for the maintenance job,
click Calendar View to view the scheduled jobs by Day, Week, or Month. All the
schedules will be displayed in the Summary table. Click X to delete a schedule.
12. Maintenance Notification – To inform users of a maintenance job, configure a notification.
Select a previously configured notification profile from the Select a profile with address only
drop-down list, or create a new e-mail notification profile by clicking the New Notification
Profile link. Click View to view the detailed configuration of the selected notification profile.
13. When finished, click Next. The Overview screen appears.
SMSP 8.1 Platform Backup and Restore User’s Guide
41
14. Review and edit the plan selections. To make changes, click Edit in the middle of the row. This
links to the corresponding setting page, allowing you to edit the configuration.
Figure 20: The Overview interface.
15. Select the Save current plan as plan template checkbox to save the current plan as a template.
Enter the template name in the textbox; after this plan template is saved, you can select it when
creating a new plan.
16. On the lower-right section of the screen, click Finish to save the configuration of the plan
without running it or Finish and Run Now to save the configuration and then run the saved plan
immediately. The backup plan is now listed in Plan Manager.
42
SMSP 8.1 Platform Backup and Restore User’s Guide
Backup Schedule
Configure the following settings in each tab to build a new backup schedule.
1. Options tab – Choose backup options for the scheduled backup job.
Figure 21: Configuring backup options.
2. Restore Granularity Level – Select the restore granularity level for the scheduled backup job.
Note that the more detailed restore granularity level you select, the more detailed the granular
restore index will be. Because a detailed granular restore index requires more storage space
than a less detailed one, ensure that there is enough space to store the generated granular
restore index. You can view the size of the data backed up by each platform backup plan and the
available space of each logical device used by the corresponding storage policy when viewing
the detailed information of the plan’s storage policy in Control Panel > Storage Configuration >
Storage Policy. After selecting the Restore Granularity Level, you can expand the tree to the
level you selected when running a restore job.
If you select None, no granular restore index is generated. However, you can still restore the
backup data of this job through a Platform granular restore by using the Browse the index from
backup data option. The granular restore index makes it easier to search for contents to be
restored from a backup.
SMSP 8.1 Platform Backup and Restore User’s Guide
43
•
Defer indexing to maintenance jobs – Selecting this option does not generate a
granular restore index for the backup data in the corresponding logical device. The index
can be generated using a scheduled or manual maintenance job that is run after the
backup job completes.
•
Granularity index server ─ Choose one or more verification servers used for generating
the granular level restore index. By default, the SQL server whose data you want to back
up is used. You can click the New Index Server link in the drop-down list to create a new
verification server. For more information, refer to About the Verification and Index
Policy.
•
Assign Mount Point ─ If you do not want to use the default mount point directory, use
this option to specify the mount point directory on which a backup set will be mounted
during generating the granular level restore index. For example: C:\mountpoint.
3. Verify Backup ─ Configure settings for verifying the backed-up database.
•
Verify Backup ─ Select this option to enable the verification of the backed up database.
Note that not all backups have to be verified, but it is recommended that you perform
at least one verified backup per day. Also, verifications can be performed through
scheduled maintenance jobs after the backup job is completed.
o
Verification server ─ Specify the server used for verifying the backed-up
database. By default, the default verification server is used. You can click the
New Verification Server link in the drop-down list to create a new verification
server. For more information, refer to About the Verification and Index Policy.
o
Assign Mount Point ─ If you do not want to use the default mount point
directory, use this option to specify the mount point directory on which a
backup set will be mounted during database verification. For example:
C:\mountpoint.
4. Check Old Backups to Be Deleted ─ If a retention rule is enabled for the selected storage policy
and the Check Old Backups to Be Deleted function is enabled, SnapManager for SharePoint
looks to see if former snapshots from this plan have been manually deleted by the user
accidentally. For those accidentally deleted snapshots, SnapManager for SharePoint ensures
that deleted snapshot data cannot be selected to restore in the Data Selection interface of the
Restore wizard.. Note that SnapManager for SharePoint does not clean up snapshot metadata.
5. Transaction Log Backup & Truncation ─ If the Run transaction log backup after full database
backup option is selected, this option backs up and truncates the transaction log after a Full
database backup. By default, this option is selected. Note that the transaction log backup is
skipped for databases in simple recovery mode.
6. Back up Stub Database for Selected Scope ─ Choose whether or not to back up the stub
database along with the contents you have selected to back up. This option allows users to
perform granular-level restores of stubs from a backed-up stub database.
7. Back up BLOB for Selected Scope ─ This option backs up BLOB content generated by Storage
Manager and files in the connected path of Connector. Select the corresponding checkboxes if
you wish to back up this BLOB data.
44
SMSP 8.1 Platform Backup and Restore User’s Guide
8. Back up Web Front-End Servers in Parallel – Choose whether or not to back up the Web frontend servers in parallel. Backing up the Web front-end servers in parallel may cause overload of
the Media service. If you select the Back up Web Front-End servers in parallel option, you are
required to specify the maximum number of the Web front-end servers you want to back up in
parallel.
*Note: The following recommendations assume that your network bandwidth is 60 MB/s:
If the content under the Extra File System Folder node exceeds 1 GB, 3 or 4 is a recommended
maximum number.
If the content under the Extra File System Folder node does not exceed 1 GB, the maximum
number can be larger because the average backup rate is less than 1 MB/s.
9. Refresh SharePoint Farm Topology – Choose whether or not to refresh the SharePoint farm
topology before starting to run the backup job and to update the backup scope in the Platform
Backup plan. Leverage this option if you have strict change management policies for SharePoint.
Refreshing the farm topology will use the current state of the farm, as indicated by SharePoint
Central Administration, to define the scope of the selected nodes in this backup plan. The plan
will assume any changes to a farm’s services, server layout, or Web applications and databases
from the previous job are expected and will not log these changes as exceptions in the job
details. After selecting this option, the Verify Storage Layout option appears. Choose whether or
not to select this option to verify the storage layout before backup.
10. Granular Index Method – Choose how to generate the granular index. Sequential will generate
the index one database at a time on each SQL Server, minimizing the resource requirements.
Parallel will generate the index for multiple databases simultaneously on each SQL Server. If you
select Parallel, by default, there will be at most five databases generating index at the same
time on a SQL Server. You can change the maximum number for the parallel index generation.
For details, refer to Configuring the Maximum Number of Database Indices to Generate in
Parallel.
11. Check Agent Account Permissions for Backup –Select Yes to check the Agent account
permissions for backup in the backup job. If you are sure that your Agent Account has the
required permissions for using Platform Backup and Restore, select No to skip this process.
Skipping this process may result in faster job times. If the job fails because of insufficient
permissions for the Agent account, the backup job report will show the details.
12. Advanced tab ─ Configure the advanced settings for the scheduled backup job.
SMSP 8.1 Platform Backup and Restore User’s Guide
45
Figure 22: Configuring advanced backup settings (1).
Figure 23: Configuring advanced backup settings (2).
46
SMSP 8.1 Platform Backup and Restore User’s Guide
13. BLOB Settings ─ Select which options to perform on the device that stores the original BLOB
data after the BLOB backup completes. The SnapMirror destination of the device that stores the
original BLOB data will be updated.
14. Database Settings ─ Configure the SnapMirror-/SnapVault-related settings for the backed-up
databases.
a. SnapMirror ─ Choose the operations to perform on the SnapMirror destination after
completion of the database backup.
o
Update SnapMirror after operation ─ If you are using backups that reside on
volumes configured as SnapMirror sources, this option updates the SnapMirror
destination after the backup operation is complete.
o
Verify on available SnapMirror destination volumes ─ Use this option to verify
the database on the SnapMirror destination volume.
b. SnapVault ─ Choose the operations to be performed on the SnapVault storage system
after completion of the database backup.
*Note: SnapVault is an option of Data ONTAP; if you are using the SMSQL 6.x, ensure
that you have set up the Protection Manager Datasets via SMSQL 6.x.
*Note: Prior to using this option in a backup plan, the SnapVault datasets must have
already been created by SMSQL and in a conformant state. For more information on
configuring the SnapVault datasets, refer to the SnapManager for Microsoft SQL Server
Installation and Administration Guide.
*Note: If you are using Clustered mode Data ONTAP 8.2, you can directly configure
SnapVault on the Clustered filers through SMSQL 7 to make it available for SMSP. If you
are using 7 mode Data ONTAP version 8.2 or below (for example, Data ONTAP 7.x), you
must use DFM to configure SnapVault for availability in SMSP.
o
Archive backup to secondary storage ─ Choose whether you want to retain
backups at the archived location on an Hourly, Daily, Weekly, Monthly, or
Unlimited basis.
o
Verify archive backup on secondary storage ─ Use this option to verify the
database archived at the secondary storage system.
c. Scripts ─ If you select the Run command with operation option, the Backup operation
command profile type will be listed in the drop-down list. Select a command profile
from the drop-down list; the commands will be run according to the command profile
you selected. You can also click the New Command Profile link in the drop-down list to
create a new command profile. For more information, refer to Command with
Operation.
15. Storage Policy Settings ─ Select which options to perform on the device configured in the
storage policy after the backup operation completes. The SnapMirror destination of the device
configured in the storage policy will be updated.
16. Time tab ─ Configure the detailed schedules for the scheduled backup job.
SMSP 8.1 Platform Backup and Restore User’s Guide
47
Figure 24: Configuring schedule backup settings.
a. Type – Select the recurring schedule. You can select By hour, By day, By week, or By
month.
b. Schedule Settings – Set up the frequency for the scheduled backup job. If you select the
type as By hour, By week, or By month, set up the advanced settings for the frequency.
For more scheduling options, select the Advanced checkbox to reveal additional options.
o
48
Advanced settings for By hour:

Specify production time – Select the production time range for the
running jobs from the drop-down lists. The start time will be the time in
the From field. The backup job will run hourly until the time entered in
the to field.

Select time below – Select a start time from the drop-down list. The
backup job will start at the entered time. You can click Add to specify
more than one start time.
o
Advanced settings for By week – Enter an integer greater than zero into the Run
every: _ week(s) text box and then select the days of the week from the on:
_drop-down list.
o
Advanced settings for By month:

On day _ of _ – Runs the backup job on the month and date you select.

Day: _ of every _ month(s) – For example, if you enter Day: 1 of every 2
months, the backup job will run on the first day of this month, and on
the first day of the month after next month, and so until the entered
end time.
SMSP 8.1 Platform Backup and Restore User’s Guide

The: _ _ of every _ month(s) –For example, if you enter The: Second
Monday of every 2 months, the backup job will run on the second
Monday every 2 months.

The: _ _ of _ – For example, if you enter The: Second Monday of
February, March, and April, the backup job will run on the second
Monday of February, second Monday of March, and second Monday of
April.
c. Range of Recurrence – Select the start time and end time for the schedule.
Manual Maintenance
In addition to a scheduled maintenance job (which can be configured in the backup plan), you can
manually perform a maintenance job, which generates a granular level index on Finished/Finished with
Exception jobs whose Index Status is not Successful. The Manual Maintenance options will configure
the SnapMirror/SnapVault settings in Job Monitor.
For detailed information on each option, refer to Maintenance Options.
To inform designated users that a maintenance job is about to be run, configure a Maintenance
Notification. Select a previously configured notification profile from the Select a profile with address
only drop-down list, or create a new e-mail notification profile by clicking the New Notification Profile
link. Click View to view the detailed configuration of the selected notification profile.
Maintenance jobs can be viewed in Job Monitor by selecting Filter group > Module > Platform
Maintenance Manager. For more information, refer to the SnapManager for SharePoint Job Monitor
User’s Guide.
Using Form Mode to Create a Backup Plan
Form Mode is recommended for users who are familiar with building SnapManager for SharePoint
backup plans. To build a backup plan in Form Mode, select the content to be backed up, and then click
Plan Builder > Form Mode. Refer to Using Wizard Mode to Create a Backup Plan for detailed
information regarding each option.
*Note: If this is your first time building a plan, or if you think you would benefit from descriptions of
each plan component, it is recommended you use the Wizard Mode.
Backing up Databases First, and then Index Components
Find the SP2010PlatformConfiguration.xml file in the Agent installation directory
(…\NetApp\SMSP8\Agent\data\SP2010\Platform) on the SQL Server that contains the databases and
index components. Configure the NativeBackupParallelConfig BackupParallel attribute; otherwise, the
customized configuration will not take effect and the default configuration will be used.
SMSP 8.1 Platform Backup and Restore User’s Guide
49
To specify whether or not to back up the databases and index components in parallel that reside on the
same server, configure the following attribute:
<NativeBackupParallelConfig BackupParallel="true"/>
The default value is “true”, which indicates that the databases and index components on this server that
are included in the backup plan will be backed up in parallel. If the value is set to False, the databases on
this server will be backed up at first before backing up the index components.
*Note: The index component here refers to that from Search Service Application or SharePoint 2010
Help Search.
Running a Backup Job Immediately
If setting up a plan using Wizard Mode, you can run the backup job immediately by clicking Finish and
Run Now when saving the plan; the plan is saved and the job is run immediately.
If setting up a plan using Form Mode, click OK and Run Now when saving the plan; the plan is saved and
the job is run immediately.
*Note: A backup job cannot be run at the same time as a restore job. However, you can perform
simultaneous backup and restore actions if the actions are on separate SQL instances.
*Note: SnapManager for SharePoint Platform backup plans do not lock up the SharePoint databases and
index files when backing up, and therefore can be scheduled to run during normal production hours.
50
SMSP 8.1 Platform Backup and Restore User’s Guide
Managing Plans
Use Plan Manager to manage created platform backup plans. After launching the Platform Backup and
Restore interface, click Plan Manager next to the Restore tab. In the Plan Manager interface, all of the
previously created plans are displayed in the main display pane.
To change the number of the plans displayed per page in this interface, select the desired number from
the Show rows drop-down menu in the lower right-hand corner. To sort the plans by heading, click the
column heading such as Plan Name, Description, Plan Group, Farm, Last Modified Time, and Platform
Type.
Figure 25: The Plan Manager interface.
Customize how these plans are displayed in a number of different ways:
•
Search – Filter the displayed plans by the keyword entered in the Input Keyword text
box (the keyword is not case-sensitive). The keyword must be contained in a column
value. You can select Search all pages or Search current page to define the search
scope. Search all pages searches all of the pages by keyword, while Search current
page searches only the current page by keyword.
•
Manage columns ( ) – Manage which columns are displayed in the list so that only the
information you want to see will be shown. Select the manage columns button ( ), and
SMSP 8.1 Platform Backup and Restore User’s Guide
51
then select the checkbox next to the column name to have that column shown in the
list.
•
Hide the column ( ) – Hover over a column heading and then click the hide the column
button ( ) to hide the column.
•
Filter the column ( )– Filter which item in the column is displayed. Unlike Search, you
can filter by any item, rather than search based on a keyword. Hover over a column
heading in a column you want to filter, and then select the filter the column button ( ).
Select the checkbox next to the item name to have that item shown in the list.
Perform the following actions in the Plan Manager interface:
•
View Details – Select a plan and click View Details. The backup scope and the plan
settings are displayed on the View Details interface. When you want to change the
nodes you selected or want to modify the settings, click Edit on the ribbon.
Figure 26: Viewing details of the selected backup plan.
52
•
Edit – Select a plan and click Edit on the ribbon to change the configurations for the
selected plan. You can change the nodes you selected and modify the Platform Backup
plan settings. Besides, you can click Storage Policy, Verification and Index Policy, or
Customized Database to perform the corresponding actions.
•
Delete – Select the plans that you want to delete and click Delete on the ribbon. A
confirmation window will pop up and ask whether you are sure that you want to
proceed with the deletion. Click OK to delete the selected plans, or click Cancel to
return to the Plan Manager interface without deleting the selected plans.
SMSP 8.1 Platform Backup and Restore User’s Guide
•
Test Run – Click Test Run to perform a test run job that simulates the real platform
backup job. By viewing the job report of the test run, you can find whether the source
contents can be backed up successfully, and then adjust the plans or optimize the
settings.
•
Run Now – Click Run Now to go to the Run Now interface. For more information on the
Run Now interface settings, see Configuring the Run Now Interface.
Configuring the Run Now Interface
*Note: In SnapManager 8.1 for SharePoint, the Options and Advanced tabs on the Run Now interface
are identical to the Backup Schedule interface.
1. Options tab – Choose backup options for the scheduled backup job.
2. Restore Granularity Level – Select the restore granularity level for the scheduled backup job.
Note that the more detailed restore granularity level you select, the more detailed the granular
restore index will be. A detailed granular restore index requires more storage space than a less
detailed one, so ensure that your storage has enough free space for the generated granular
restore index. You can view the size of the data backed up by each platform backup plan and the
available space of each logical device used by the corresponding storage policy when viewing
the detailed information of the plan’s storage policy in Control Panel > Storage Configuration >
Storage Policy. After selecting the Restore Granularity Level, you can expand the tree to the
level you selected when running a restore job.
If you select None, no granular restore index is generated. However, you can still restore the
backup data of this job through a Platform granular restore by using the Browse the index from
backup data option. The granular restore index makes it easier to search for contents to be
restored from a backup.
•
Defer indexing to maintenance jobs – Selecting this option does not generate a
granular restore index for the backup data in the corresponding logical device. The index
can be generated using a scheduled or manual maintenance job that is run after the
backup job completes.
•
Granularity index server ─ Select one or more verification servers used for generating
the granular level restore index. By default, the SQL server whose data you want to back
up is used. You can click the New Index Server link in the drop-down list to create a new
verification server or server group. For more information, refer to About the Verification
and Index Policy.
•
Assign Mount Point ─ If you do not want to use the default mount point directory, use
this option to specify the mount point directory on which a backup set will be mounted
during generating the granular level restore index. For example: C:\mountpoint.
3. Verify Backup ─ Configure settings for verifying the backed-up database.
•
Verify Backup ─ Select this option to enable the verification of the backed up database.
Note that not all backups have to be verified, but it is recommended that you perform
SMSP 8.1 Platform Backup and Restore User’s Guide
53
at least one verified backup per day. Also, verifications can be performed through
scheduled maintenance jobs after the backup job is completed.
o
Verification server ─ Select one or more database server used for verifying the
backed-up database. By default, the SQL Server whose data you want to back up
is used. You can click the New Verification Server link in the drop-down list to
create a new verification server or server group. For more information, refer to
About the Verification and Index Policy.
o
Assign Mount Point ─ If you do not want to use the default mount point
directory, use this option to specify the mount point directory on which a
backup set will be mounted during database verification. For example:
C:\mountpoint.
4. Check Old Backups to Be Deleted ─ If a retention rule is enabled for the selected storage policy
and the Check Old Backups to Be Deleted function is enabled, SnapManager for SharePoint
looks to see if former snapshots from this plan have been manually deleted by the user
accidentally. For those accidentally deleted snapshots, SnapManager for SharePoint ensures
that deleted snapshot data cannot be selected to restore in the Data Selection interface of the
Restore wizard..
5. Transaction Log Backup & Truncation ─ If the Run transaction log backup after full database
backup option is selected, this option backs up and truncates the transaction log after a Full
database backup. By default, this option is selected. Note that the transaction log backup is
skipped for databases in simple recovery mode.
6. Back up Stub Database for Selected Scope ─ Choose whether or not to back up the stub
database along with the contents you have selected to back up. This option allows users to
perform granular-level restores of stubs from a backed-up stub database.
7. Back up BLOB for Selected Scope ─ This option backs up BLOB content generated by Storage
Manager and files in the connected path of Connector. Select the corresponding checkboxes if
you wish to back up this BLOB data.
8. Back up Web Front-End Servers in Parallel – Note that backing up Web front-end servers in
parallel may overload the Media service. If you select the Back up Web Front-End servers in
parallel option, you are required to specify the maximum number of Web front-end servers to
back up in parallel.
*Note: The following recommendations assume that your network bandwidth is 60 MB/s):
If the content under the Extra File System Folder node exceeds 1 GB, 3 or 4 is a recommended
maximum number.
If your content under the Extra File System Folder node does not exceed 1 GB, the maximum
number can be larger because the average backup rate is less than 1 MB/s.
9. Refresh SharePoint Farm Topology – This feature refreshes the SharePoint farm topology
before starting a backup job and updates the backup scope in the Platform Backup plan.
Leverage this option if you have strict change management policies for SharePoint. Refreshing
the farm topology causes SnapManager for SharePoint to use the current state of the farm, as
determined by SharePoint Central Administration, to define the scope of the selected nodes in
54
SMSP 8.1 Platform Backup and Restore User’s Guide
this plan. The plan assumes that any changes to a farm’s services, server layout, or Web
applications and databases from the previous job are expected, so these changes are not logged
as exceptions in the job details. After selecting the Refresh SharePoint farm topology before
starting backup job option, the Verify storage layout option appears. Select this option to verify
the storage layout before running a backup plan.
10. Granular Index Method – Choose how to generate the granular index. Sequential generates the
index one database at a time on each SQL Server, thereby minimizing the resource requirements.
Parallel generates the index for multiple databases simultaneously on each SQL Server. If you
select Parallel, SnapManager for SharePoint will by default generate (at most) five database
indices at the same time on a SQL Server. To change the maximum number of indices to
generate simultaneously, refer to Configuring the Maximum Number of Database Indices to
Generate in Parallel.
11. Check Agent Account Permissions for Backup –Select Yes to check the Agent account
permissions for backup in the backup job. If you are sure that your Agent Account is granted the
required permissions for using Platform Backup and Restore, select No to skip this process.
Skipping this process may result in faster job times. If the job fails because of insufficient
permissions of Agent account, the backup job report will show the details.
12. Remember these settings – Select Yes to remember these settings for the future usage when
the current user performs any backup jobs. Otherwise, select No.
13. Advanced tab ─ Configure the advanced settings for the scheduled backup job.
14. BLOB Settings ─ Select which options to perform on the device that stores the original BLOB
data after the BLOB backup completes. The SnapMirror destination of the device that stores the
original BLOB data will be updated.
15. Database Settings ─ Configure the SnapMirror-/SnapVault-related settings for the backed-up
databases.
a. SnapMirror ─ Choose the operations to perform on the SnapMirror destination after
completion of the database backup.
o
Update SnapMirror after operation ─ If you are using backups that reside on
volumes configured as SnapMirror sources, this option updates the SnapMirror
destination after the backup operation is complete.
o
Verify on available SnapMirror destination volumes ─ Use this option to verify
the database on the SnapMirror destination volume.
b. SnapVault ─ Choose the operations to be performed on the SnapVault storage system
after completion of the database backup.
*Note: SnapVault is an option of Data ONTAP; if you are using the SMSQL 6.x, ensure
that you have set up the Protection Manager Datasets via SMSQL 6.x.
*Note: Prior to using this option in a backup plan, the SnapVault datasets must have
already been created by SMSQL and in a conformant state. For more information on
configuring the SnapVault datasets, refer to the SnapManager for Microsoft SQL Server
Installation and Administration Guide.
SMSP 8.1 Platform Backup and Restore User’s Guide
55
*Note: If you are using Clustered mode Data ONTAP 8.2, you can directly configure
SnapVault on the Clustered filers through SMSQL 7 to make it available for SMSP. If you
are using 7 mode Data ONTAP version 8.2 or below (for example, Data ONTAP 7.x), you
must use DFM to configure SnapVault for availability in SMSP.
o
Archive backup to secondary storage ─ Select whether you want to retain
backups at the archived location on an Hourly, Daily, Weekly, Monthly, or
Unlimited basis.
o
Verify archive backup on secondary storage ─ Use this option to verify the
database archived at the secondary storage system.
c. Scripts ─ If you select the Run command with operation option, the Backup operation
command profile type will be listed in the drop-down list. Select a command profile
from the drop-down list; the commands will be run according to the command profile
you selected. You can also click the New Command Profile link in the drop-down list to
create a new command profile. For more information, refer to Command with
Operation.
d. Storage Policy Settings ─ Select which options to perform on the device configured in
the storage policy after the backup operation completes. The SnapMirror destination of
the device configured in the storage policy will be updated.
16. Remember these settings – Select Yes to remember these settings for the future usage when
the current user performs any backup jobs. Otherwise, select No.
56
SMSP 8.1 Platform Backup and Restore User’s Guide
Generating an Index
Use the Generate Index feature to generate for the first time a granular index for a selected database,
or to replace an existing corrupted index. You can mount the temporary database to one or more index
servers during index generation.
*Note: You cannot regenerate a granular index on backup data that is imported from SnapManager 6
for SharePoint.
*Note: The default maximum number of snapshots that can be cloned as a group for index generation is
5. The default maximum number of databases to generate index in parallel is 5. To configure a desired
maximum number for cloning snapshots or generating index, refer to Configuring the Maximum Number
of Snapshots Cloned for Index Generation and Configuring the Maximum Number of Database Indices to
Generate in Parallel.
To generate index, complete the steps below:
1. Select the Restore tab and click Generate Index in the Manage group. The Generate Index tab
appears.
Figure 27: Selecting the Generate Index button on the Restore tab.
2. Configure the options in the Filter By area to limit the scope of backup data. By default, all of
the backup jobs that were run within the last 7 days are displayed.
a. Filter by Plan – Filter the backup data by plan information using the drop-down list.
o
Farm – Select a farm from the drop-down list to display all plans for that
particular farm. Select All Farms to display all plans for all farms.
o
Plan Name – Select the plan that you want to display from the drop-down list.
Select All Plans to display all plans.
o
Restore Granularity Level – Select the restore granularity level from the dropdown list; only the backup jobs that support the selected restore granularity
levels are displayed. Select All Types to list backup jobs for all levels.
b. Filter by Time Range – Filter backup data by completion time range using the dropdown list.
SMSP 8.1 Platform Backup and Restore User’s Guide
57
o
All Jobs – Select this option to display all Finished/Finished with Exception
Platform backup jobs.
o
Backup jobs start within … – Select this option to select a time period. All of the
Finished/Finished with Exception Platform backup jobs whose start time is in the
entered time period are displayed.
3. After selecting the filters, click the Filter button in the Filter By area or on the ribbon. All backup
jobs that meet the selected filter rules are listed in the calendar. If desired, click Clear All Filters
in the Filter By area or click Clear on the ribbon to clear all filters and display all
Finished/Finished with Exception Platform backup jobs.
4. Select the backup job that contains the desired databases. Additional actions that can be
performed:
•
Place the mouse cursor over a backup job to display job information such as the Plan
Name, Job ID, Restore Granularity Level, Index Status, Job Status and Data Import.
Click Day, Week, or Month to change the view to see all the available jobs during that
time period.
•
Click the page turning button
page.
on the top-left corner of the calendar to turn the
5. Click Next. The Data Selection interface appears.
6. Expand the Backup Data tree to select the desired Web application or content database. The
current index level is displayed beside the corresponding database. Select the content databases
to generate granular index.
Figure 28: Selecting the desired nodes to generate index.
58
SMSP 8.1 Platform Backup and Restore User’s Guide
7. Click Next. The Index Settings interface appears.
8. Index Level – Select from the drop-down list the granular index level.
9. Clone Database Option – Choose whether or not to clone the database on a SnapMirror
destination or SnapVault destination after generating the database’s granular index.
•
Clone database on SnapMirror destination ─ Select this option to clone a database
based upon the Snapshot copy on the SnapMirror destination volume.
•
Clone database on SnapVault destination ─ Select this option to use a remote backup
to perform the cloning operation. Snapshots saved in SnapVault primary storage are
considered Local Backups, and snapshots saved in SnapVault secondary storage are
considered Remote Backups.
10. Index Conflict Resolution – Select an index conflict resolution. If generating a more granularlevel index than your current index level, SnapManager for SharePoint will automatically reindex the database. If the selected index level is less granular than the current index level:
•
Skip keeps the current index level.
•
Replace removes the existing index and generates a new granular index for the
database.
11. Granular Index Method – Choose how to generate the granular index. Sequential generates the
index one database at a time on each SQL Server, minimizing the resource requirements for
generating an index. Parallel simultaneously generates the indices for multiple databases on
each SQL Server. If you select Parallel, by default, there will be at most five databases
generating index at the same time on a SQL Server. To change the maximum number of indexes
you can generate simultaneously. refer to Configuring the Maximum Number of Database
Indices to Generate in Parallel.
12. Verification and Index Policy – You can use the SQL Server where the database resides to
mount a temporary database for index generation, or you can use a configured index server or
index server group to mount the temporary database for the index generation. Select New
Verification and Index Policy from the drop-down list to create a new verification and index
server or group to mount temporary database for index generation. For details, refer to About
the Verification and Index Policy.
13. Assign Mount Point (Optional) – If you do not want to use the SQL Server default mount point
or the mount point directory of the selected index server or group, you can manually enter a
desired mount point path here.
14. Click Next. The Notification interface appears.
15. Notification – Configure the e-mail Notification settings. Select a previously configured
notification profile from the Select a profile with address only drop-down list, or create a new
e-mail notification profile by clicking the New Notification Profile link. Click View to view the
detailed configuration of the selected notification profile.
SMSP 8.1 Platform Backup and Restore User’s Guide
59
16. When finished, click Next. The Overview page appears.
Figure 29: The Overview interface.
17. Review and edit the job selections as needed. To make changes, click Edit in the middle of the
row.
18. Click Finish to save the configuration and run the job immediately.
Checking the Generate Index Job Status
The Generate Index job can be found in the Platform Maintenance Manager module with a Job ID that
starts with PM. For details on managing and viewing job information and details, refer to SnapManager
8 for Microsoft SharePoint Job Monitor User Guide.
After generating a granular index using the Generate Index, the Index Status of the applicable backup
job will be Regenerated or Successful.
60
•
Regenerated – If you selected to generate an index for at least one of the successfully
backed-up databases in this backup job, and at least one index was successfully
generated, the Index Status for this backup job will be Regenerated.
•
Successful – In this case, the Generate Index job must have the following requirements.
SMSP 8.1 Platform Backup and Restore User’s Guide
o
All of the databases that were successfully backed up in this backup job are
selected to generate an index whose level is equal to or more granular than the
current index level.
o
All of the selected databases have successfully generated the granular index.
Configuring the Maximum Number of Snapshots Cloned for Index
Generation
Use the SP2010PlatformConfiguration.xml file to configure the maximum number of snapshots cloned
for index generation.
*Note: Both the SharePoint 2010 environment and SharePoint 2013 environment use this same
configuration file.
On the SQL Server that contains the database, find the SP2010PlatformConfiguration.xml file in the
Agent installation directory (…\NetApp\SMSP8\Agent\data\SP2010\Platform). Then, configure the
following attribute:
<MaxCloneCountConfig MaxCloneCount="5"/>
The default value is “5”, which indicates that at most five snapshots will be cloned in sequential order as
a group to generate index. After the index generation completes, the cloned snapshots are deleted. The
next five snapshots will be cloned and will go through the same process for the next index generation.
Configuring the Maximum Number of Database Indices to
Generate in Parallel
Use the SP2010PlatformConfiguration.xml to configure the maximum number of databases to generate
index in parallel.
*Note: Both SharePoint 2010 environments and SharePoint 2013 environments use this same
configuration file.
On the SQL Server that contains the database, find the SP2010PlatformConfiguration.xml file in the
Agent installation directory (…\NetApp\SMSP8\Agent\data\SP2010\Platform). Then, configure the
following attribute:
<GenerateIndexConfig GenerateIndexMaxThreadCount="5"
The default value is “5”, which indicates that at most, five databases will be simultaneously performing
index generation.
SMSP 8.1 Platform Backup and Restore User’s Guide
61
Performing a Restore
A Platform restore can be performed only on snapshots backed up using SnapManager for SharePoint
Platform Backup and Restore. Before building a restore plan, refer to Restore Details for Specific Farm
Components for important information regarding the restore of farm components.
*Note: A restore job cannot be run at the same time as a backup job. However, you can perform
simultaneous backup and restore actions if the actions are on separate SQL instances.
There are two restore levels available:
•
Database Level ─ Under the Backup Data pane, the SharePoint farm structure is
displayed. Multiple farm components, such as Web applications, content databases,
service applications, or even the entire farm and its settings, can be selected for
restoration.
•
Granular Restore Level ─ If granular indexing options were selected during backup,
individual site collections, sites, libraries, lists, folders, items, or file/item versions can be
restored from the content databases after clicking the View Details link on the top-right
corner of the Backup Data pane. You can also search for the content to be restored by
clicking Advanced Search on the ribbon and search using the entered criteria.
The following are the types of restore that can be performed:
1. In place restore (at database level or granular restore level) – Restores the selected backed-up
data to its original location in SharePoint.
2. Out of place restore (at granular restore level) – Restores the selected backed-up data to
another location in the original SharePoint farm or another SharePoint farm (other than the
original location).
*Note: Before performing an out of place restore of granular content to another location in the
same SharePoint farm, make sure the SQL alias points to the same SQL instance in the backup
and restore process. If you are about to perform an out of place restore of granular content to
another SharePoint farm, make sure there is no SQL alias in the destination that has the same
name as the source SQL alias. Ensure that the destination SQL alias points to a different SQL
instance.
If you perform an out of place restore using the Restore from alternate storage location restore
type, use the clone-backup cmdlet in SnapManager for SQL Server to clone the temporary
database to the desired SQL instance, and make sure the destination farm can successfully
connect to the database using the designated SQL alias name.
*Note: For information regarding the SharePoint components supported in Platform Backup and
Restore, refer to Appendix C: Supported SharePoint Components.
62
SMSP 8.1 Platform Backup and Restore User’s Guide
*Note: The account of the Platform Backup and Restore Agent that is installed on the SharePoint Central
Administration server must be the Administrator of a selected site collection in order to restore the
corresponding site administration-level search scope.
SMSP 8.1 Platform Backup and Restore User’s Guide
63
Building a Restore Plan
The procedure for building in place and out of place restore plans is identical for both until the Restore
Type step. Follow the instructions below for all restore types, and then skip to the section appropriate to
your plan type.
1. Select the Restore tab and click Restore in the Manage group. The Time-based Restore tab
appears.
Figure 30: Time-based Restore tab page.
2. Configure the options in the Filter By: area to limit the scope of backup data. By default, all
backup jobs started within the last 7 days are displayed.
a. Filter by Plan – Filter the backup data by plan information using the drop-down list.
64
o
Farm – Select a farm from the drop-down list to display all plans for that
particular farm. Select All Farms to display all plans for all farms.
o
Plan Name – Select the plan that you want to display from the drop-down list.
Select All Plans to display all plans.
SMSP 8.1 Platform Backup and Restore User’s Guide
o
Restore Granularity Level – Select the restore granularity level from the dropdown list; only the backup jobs that support the selected restore granularity
levels are displayed. Select All Types to list backup jobs for all levels.
b. Filter by Time Range – Filter backup data by completion time range using the dropdown list.
o
All Jobs – Select this option to display all Finished/Finished with Exception
Platform backup jobs.
o
Backup jobs start within … – Select this option to select a time period. All of the
Finished/Finished with Exception Platform backup jobs whose start time is in the
selected time period are displayed.
3. After selecting the filters, click the Filter button in the Filter By: area or on the ribbon. All
backup jobs that meet the selected filter rules are listed in the calendar. If desired, click Clear All
Filters in the Filter By: area or click Clear on the ribbon to clear all filters and display all
Finished/Finished with Exception Platform backup jobs.
4. Select the backup job that you want to restore by clicking the job. Additional actions that can be
performed:
•
Place the mouse cursor over a backup job to display job information such as the Plan
Name, Job ID, Restore Granularity Level, Index Status, Job Status and Data Import.
Click Day, Week, or Month to change the view to see all the available jobs during that
time period.
•
Click the page turning button
page.
on the top-left corner of the calendar to turn the
5. Find the desired site collections in the farm using the Find Site Collection feature. Enter the
keywords of the site collection URL or combine the keywords with wildcards.
6. Now that you have selected a backup job containing data you want to restore, click the link
applicable to your type of restore to continue with instructions on building the job:
•
Building a Restore Plan at Database Level
•
Building an In Place Platform Granular Restore Plan
•
Building an Out of Place Platform Granular Restore Plan
•
Restoring from an Alternate Storage Location
•
Cloning SharePoint Components for Restore
•
Options for Restoring Backed-up Web Front-end Files
•
Restoring Backed-up BLOB Data
SMSP 8.1 Platform Backup and Restore User’s Guide
65
Building a Restore Plan at Database Level
To build and run an in place restore job at the database level:
1. Follow the instructions given in Performing a Restore to begin building the plan.
Figure 31: Building a restore plan.
2. Data Selection – From the tree, select the content you want to restore. The content in the tree
will vary depending upon the type of backup selected. In this case, select a content database to
restore. You can use the Find Site Collection feature to search for your desired site collections.
For more details, refer to Appendix A: About Find Site Collection.
3. Restore Type – Choose how the content will be restored.
•
66
Restore Type ─ Select one restore type from the three types below.
o
Restore to original farm ─ Use this option to restore the databases to the
original farm with the specified configurations.
o
Restore from alternate storage location ─ Use this option to restore the
databases from the alternate storage location by manually restoring the
databases in SMSQL. For more information, refer to Restoring from an Alternate
Storage Location.
SMSP 8.1 Platform Backup and Restore User’s Guide
o
•
Clone to another farm Use this option to clone the selected databases with the
associated BLOB data and stub database. Select a destination farm from the
Destination Farm drop-down list. For more information, refer to Cloning
SharePoint Components for Restore.
Agent Group – Select the Agent group that will perform the restore job. Click View to
view the details of the selected Agent group.
4. Snapshot Selection –Click Load Remote Snapshot on the ribbon to load the remote snapshots in
SnapVault. After the remote backups are loaded in the tree, select local or remote snapshots for
the selected content database. Click View Details next to the snapshot to view the content
databases. Make sure that all of the selected content databases have the corresponding local or
remote snapshots selected.
Figure 32: The Snapshot Selection page.
SMSP 8.1 Platform Backup and Restore User’s Guide
67
5. Restore Settings – Choose detailed settings for the restore job.
Figure 33: Restore Settings.
a. Restore Database to Most Recent State – With this option enabled, the database is
restored together with any recent modifications that were made after the latest
database backup. SnapManager for SharePoint first restores the backed-up database,
and then modifies the database to its most recent status by applying all of the backedup transaction logs to the restored database. Select No to restore only the backed up
database.
To use this option, you must select the most recent backup data. If this option is not
used, a point-in-time restore is performed, which creates multiple recovery paths for
the database. A later up-to-the-minute restore using the same backup data will fail. In
that case, the SnapManager for Microsoft SQL Server interface can be used for up-tothe-minute restores. For more information, refer to Restoring a Database to a Point in
Time.
b. Restore Database Only – If Yes is selected, the selected databases are restored with no
attempt to connect them to the SharePoint environment. This is useful when a
SharePoint environment has not yet been set up (for example, during a whole farm
restore). This can also be useful when performing manual steps to bring up or down a
specific environment after the database has been restored. If you select No, the
database is connected to the SharePoint farm normally after the restore.
68
SMSP 8.1 Platform Backup and Restore User’s Guide
*Note: Configuration databases and Central Administration databases can only be
restored when this option is selected.
c. Conflict Resolution – Select whether or not to overwrite the database contents if there
is a conflict between the original database name and that of the backed-up database.
o
Skip – If a selected database in the backup has the same name as a database in
the original farm, then the selected database in the backup is not restored.
o
Overwrite – If a selected database in the backup has the same name as a
database in the original farm, then the original database is deleted first and the
database in the backup is then restored.
d. Verify Backup Data Before Restore ─ Choose whether to verify the backup data before
a restore operation and then configure the corresponding settings.
o
Verify Backup ─ This option enables you to verify backup data before restoring
it to ensure that the restore is successful. Select this option enables the
following settings.

Verification server ─ Select one or more verification servers used for
verifying the backed up database. By default, the SQL Server whose
database you want to restore is used. You can click the New Verification
Server link in the drop-down list to create a new verification server or
server group. For more information, refer to About the Verification and
Index Policy.
e. Run Command With Operation ─ If you select the Run command with operation option,
the command profile of the Restore operation type will be listed in the drop-down list.
Select a command profile from the drop-down list. The commands will be run according
to the command profile you selected. You can also click the New Command Profile link
in the drop-down list to create a new command profile. For more information, refer to
Command with Operation.
f.
Notification ─ Configure the e-mail Notification settings. Select a previously configured
notification profile from the Select a profile with address only drop-down list, or create
a new e-mail notification profile by clicking the New Notification Profile link. Click View
to view the detailed configuration of the selected notification profile.
6. When finished configuring Restore Settings, click Next. The Schedule page appears.
7. Schedule – Choose whether or not to run the restore job based on a schedule.
•
Select Restore immediately after wizard finishes to run the job immediately after
finishing the restore wizard.
•
To configure the schedule yourself, select Configure the schedule myself and input a
start time in Schedule Settings field. If desired, enter an optional Description to
distinguish the restore job from others.
8. When finished, click Next. The Overview page appears.
SMSP 8.1 Platform Backup and Restore User’s Guide
69
9. Review and edit the job selections. To make changes, click Edit in the middle of the row. This
links to the corresponding setting page, allowing you to edit the configuration.
10. Click Finish to save the job’s configuration.
a. If the restore job does not have a schedule, Finish runs the job immediately.
b. If the restore job is set to run on a schedule, Finish saves the restore job’s configuration
without running it.
70
SMSP 8.1 Platform Backup and Restore User’s Guide
Building an In Place Platform Granular Restore Plan
1. Follow the instructions given in Performing a Restore to begin building the plan.
Figure 34: Selecting a backup plan’s data.
2. Data Selection – Configure the following settings:
a. Select the database that includes the granular content you wish to restore.
b. Click the View Granular Contents link next to the selected content database to view
backup details about the selected database. For details on searching granular data using
the Advanced Search feature, refer to Appendix B: About Advanced Search.
3. You can navigate directly to the Backup Data tab to expand the granular data tree; the backup
tree’s stored index will be used to load the backup data tree. Select your desired granular level
nodes to restore. If no stored index is detected, SnapManager for SharePoint will instruct you to
select the Browse the index from backup data option to continue loading the tree.
Alternatively, you can click the Global Setting for Restoring Content, Property and Security link
at the top of the Data Selection interface and configure the Item Level Settings:
SMSP 8.1 Platform Backup and Restore User’s Guide
71
Figure 35: The Global Setting for Restoring Content, Property and Security link.
•
Restore Granular Content – Select this option to restore granular content. If you are
browsing the tree to load content under site collections, the Restore Granular Content
option is automatically selected to enable the restore of the granular contents under
the site collection level. If you deselect the Restore Granular Content option, the tree is
reloaded and you can only browse the tree to the site collection level. For details, refer
to Deselecting the Restore Granular Content Feature.
•
Browse Method ─ Choose whether or not to browse the tree from the index generated
from the backup data. The current granular level of your stored index is displayed in
bold on the left side of the interface.
o
72
Browse the index from backup data – When this option is selected, a
SharePoint content database backup snapshot is first mounted as a temporary
database. Users can then browse and restore specific granular content. This
option will appear slower when the first browser request is processed. Note
that the tree is generated in real time and can be displayed down to the item
version level regardless of the database’s original restore granularity.
SMSP 8.1 Platform Backup and Restore User’s Guide
By default, the mounted temporary database is stored on the default
verification server. To choose another verification server, select a pre-defined
verification and index policy from the drop-down list, or click the New
Verification and Index Policy link in the drop-down list to create a new
verification server. For more information, refer to About the Verification and
Index Policy.
•
Container Selection ─ Select the Global setting for container configuration checkbox to
enable the container’s global settings.
o
Restore container ─ Select this option to restore the containers in the selected
backup data. Select the Security checkbox if you want to restore the container’s
security settings, and/or select the Property checkbox if you want to restore the
container’s property settings. For more information, refer to Appendix A.
o
Only restore security ─ Select this option to restore only the container’s security
settings. You can select the Conflict resolution as Merge or Replace. Merge will
add the security of the container in the backup to the conflict container in the
destination. Replace will delete the security of the conflict container in the
destination first, and then add the security of the container in the backup to the
conflict container in the destination.
*Note: The Only restore security feature takes effect only if the selected nodes
do not inherit security from their parent nodes.
*Note: Once you select the Only restore security option, the Container level
conflict resolution configuration field in the Restore Settings page will only
display Skip and you will not be able to configure the other Container level
conflict resolutions through that page.
•
Content Selection ─ Select the Global setting for content configuration checkbox to
enable the content’s global settings.
o
Restore content ─ Select this option to restore content in the selected backup
data. Select the Security checkbox to restore the content’s security settings as
well. For more information, refer to Appendix A.
o
Only restore security ─ Select this option to restore only the content’s security
settings. You can select the Conflict resolution as Merge or Replace. Merge will
add the security settings of the content in the backup into the conflict content
in the destination. Replace will delete the security settings of the conflict
content in the destination first, and then add the security of the content in the
backup to the conflict content in the destination.
*Note: The Only restore security feature takes effect only if the selected nodes
do not inherit security from their parent nodes.
*Note: Once you select the Only restore security option, the Content level
conflict resolution configuration field in the Restore Settings page will display
SMSP 8.1 Platform Backup and Restore User’s Guide
73
Skip only. You will not be able to configure other Content level conflict
resolutions through that page.
4. Expand the tree and locate the content you want to restore. The detailed information can be
viewed in the popped up Item Browser window. Specify the configuration of the
container/content being restored.
a. Security – Refer to Appendix E: SharePoint Object Security and Property.
b. Property – Refer to Appendix E: SharePoint Object Security and Property.
5. When finished, click Next. The Stub and BLOB Configuration page appears.
*Note: The Stub and BLOB Configuration page is available when the selected backup data for a
granular level restore contains stubs. Configure the Stub Database Settings and BLOB Settings
to choose to restore granular data from the backed-up stub database/BLOB data or from the
original Storage Manager/Connector devices.
6. Stub Database Settings – Choose whether or not to restore the granular data from the backedup stub database in the Use Backed up Stub Database field.
•
Select Yes to restore the granular data from the backed-up stub database. If you select
Yes, you are required to select which backup method you have used.
o
Default Platform Backup – Use the stub database that has been backed up by a
Platform Backup job.
o
Other/Third Party Backup – Select this option if the stub database was backed
up by other/third party tools, and you must manually restore and stage the stub
database onto the destination SQL Server.

•
Database Access Credentials – Enter the SQL instance name where the
stub database resides and the stub database name. Select the database
authentication to use to access the customer backed up stub database.
Select No to restore the stubs from the original Storage Manager/Connector devices.
7. BLOB Settings – Choose whether or not to restore the granular data from the backed up BLOB
data.
•
Select Yes to restore the granular data from the backed up BLOB data. If you select Yes,
you are required to select which backup method you have used.
o
Default Platform Backup – Use the BLOB data that has been backed up by
Platform Backup job to restore.
o
Other/Third Party Backup – Select this option if the BLOB data was backed up
by other/third party tools, and you must manually restore the BLOB data to a
location that must be configured as a logical device.

74
Logical Device – Select the logical device where the BLOB data has been
staged from the Logical device drop-down list.
SMSP 8.1 Platform Backup and Restore User’s Guide
•
Select No to restore the granular data from the original Storage Manager/Connector
devices.
8. Click Next. The Restore Type page appears.
9. Restore Type – Choose how the content will be restored.
a. Restore Type – Select the location where to restore the backup data. In this case, select
In place restore to restore the selected content to its original SharePoint location.
Figure 36: In place restore.
b. Restore From Alternate Storage Location ─ Use this option to restore the data from an
alternate storage location by manually cloning the databases in SMSQL. For more
information, refer to Restoring from an Alternate Storage Location.
c. Agent Group – Select the Agent group that will perform the restore job. Click View to
view the details of the selected Agent group.
SMSP 8.1 Platform Backup and Restore User’s Guide
75
10. Click Next when finished. The Restore Settings page appears.
Figure 37: Configuring restore settings (1).
Figure 38: Configuring restore settings (2).
11. Restore Settings – Configure how the content will be restored.
a. Conflict Resolution – Select the action to dictate how to resolve the container level and
content level conflicts that arise during a Platform granular restore.
76
SMSP 8.1 Platform Backup and Restore User’s Guide
o
Container level conflict resolution – Set the conflict resolution on the site
collection, site, list, and folder levels.

Skip – Ignores the source container that conflicts with the destination
one.

Merge – Combines the configuration of the source and destination
containers. If there is a conflict, the source configuration overwrites the
destination’s configuration.

Replace – Deletes the destination container and then restores the
source container to the destination. If the selected container is a toplevel site, Replace function empties the top-level site instead of deleting
it and restores the source top-level site to the destination. This option
can only be used at folder/list/library/site/site collection level.
*Note: As the Replace conflict resolution deletes the destination
container before performing the restore, make sure the destination
container is no longer needed before performing the restore using this
conflict resolution.
o
Content Level Conflict Resolution – Set the conflict resolution on the item level.

Skip – Ignores the source item/document that has the same item
ID/document name as the destination item/document.

Overwrite – Copies the source item/document to the destination by
overwriting the destination item/document with same item
ID/document name.

Overwrite by Last Modified Time – Keeps the conflict item/document
which has the latest modified time and overwrites the older one.

Append an Item/Document with a Suffix – Keeps both of the conflict
items/documents and adds a suffix (_1, _2, _3…) to the name of the
conflict source item/document.

Append a New Version – Adds the conflict source item/document to
the destination as a new version of the conflict destination
item/document.
b. Apps Conflict Resolution – Define the conflict resolution behavior that occurs if there is
a conflict with Apps in the source and destination. You can choose Skip, Update App
Only, or Replace App and AppData from the drop-down list. To successfully restore
SharePoint Apps, make sure that the Agent account to perform the restore job is not a
Local system account.
o
Skip – Ignores the source App that has the same name as the destination one.
o
Update App Only – If the source App is a more recent version than the
destination one, the destination App is updated, but the original destination
AppData remains.
SMSP 8.1 Platform Backup and Restore User’s Guide
77
o
Replace App and AppData – The source App replaces the destination App and
AppData, even if it is in an older version.
c. Include Recycle Bin Data – Choose whether to compare the data in the backup with the
data in the original SharePoint farm’s recycle bin. If you select Skip at the Container
level or Content level, or you select Append an Item/Document Name with a Suffix or
Append a New Version at the Content level, the Include Recycle Bin Data option is
available. If you select Yes in this field and the selected content in the backup still exists
in the original SharePoint farm’s Recycle Bin, the selected content in the backup is not
restored.
d. Include Detailed Job Report for All Items – Selecting Yes generates a detailed job report
for all of the items. Selecting No still generates a job report, but only in truncated list
form.
e. Verification and Index Policy – Select a verification and index policy from drop-down list.
Here, you will designate one or more database servers for verifying the database backup
data and for generating the granular level index. By default, SnapManager for
SharePoint uses the SQL Server that contains the data you are about to restore.
If you do not want to use the default mount point directory, you can use the Assign
Mount Point option to specify the mount point directory.
f.
Workflow – Decide how the backed-up workflows are restored.
o
Include workflow definition – Only restores the definition of the backed-up
workflows.
o
Include workflow instance – Restore the state, history, and tasks for each item.
*Note: All workflow instances whose status was In Progress when backed up
will be Cancelled when restored to the destination.
g. Item Dependent Columns and Content Types – Choose whether to restore itemdependent columns and content types.
*Note: If you did not select Property beside the selected node in the Data Selection
step and the dependent column or content type does not exist in the destination, the
column or content type will not be restored. If this is the case, use this option to restore
them.
78
o
Restore the item-dependent columns and content types to maintain item
integrity – The item is restored and the dependent column or content type is
created in the corresponding list/library. The item still uses the dependent
column and content type.
o
Do not restore item-dependent columns and content types – The item
dependent columns and dependent content types will not be restored. When
selecting this option, make sure the dependent columns and content types exist
in the destination. Otherwise, the item cannot be restored.
SMSP 8.1 Platform Backup and Restore User’s Guide
h. Exclude User/Group Without Permission ─ If you select Yes, the users/groups that have
no permissions will not be restored. By default, No is selected.
i.
Version Settings – Choose the Version Settings for the content being restored to
SharePoint. To improve performance, limit the versions restored. Restore all versions
restores all versions of the backup data; while Restore the latest version(s) only
restores the latest several Major or Major and Minor versions of the backup data as
designated. The other versions are not restored. Note that the current version will
always be restored together with the entered number of Major or Major and Minor
versions.
j.
Notification – Configure the e-mail Notification settings. Select a previously configured
notification profile from the Select a profile with address only drop-down list, or choose
to create a new e-mail notification profile by clicking the New Notification Profile link.
Click View to view the detailed configuration of the selected notification profile.
12. When finished configuring Restore Settings, click Next. The Schedule page appears.
13. Schedule – Choose whether or not to create the restore job based on a schedule. Select Restore
once finish the wizard to run the job immediately after finishing the restore wizard. If you
decide to configure the schedule yourself, select Configure the schedule myself and input a
start time in Schedule Settings field. If desired, enter an optional Description to distinguish the
restore job from others.
14. When finished, click Next. The Overview page appears.
15. Review and edit the job selections. To make changes, click Edit in the middle of the row. This
links to the corresponding setting page, allowing you to edit the configuration.
16. Click Finish to save the job’s configuration. If the restore job does not have a schedule, Finish
runs the job immediately. If the restore job is set to run on a schedule, Finish saves the restore
job’s configuration without running it.
SMSP 8.1 Platform Backup and Restore User’s Guide
79
Building an Out of Place Platform Granular Restore Plan
To build and run an out of place Platform granular restore plan:
1. Follow the instructions given in Performing a Restore to begin building the plan.
2. Data Selection – Select the database that includes the granular content to restore. Click View
Granular Content link on the top right corner of the Backup Data pane to view the detailed
backup data for the selected database. For details on searching granular data using the
Advanced Search feature, refer to Appendix B: About Advanced Search.
3. You can navigate directly to the Backup Data tab to expand the granular data tree. The backup
tree’s stored index will be used to load the backup data tree. Select your desired granular level
nodes to restore. If no stored index is detected, SMSP will instruct you to select the Browse the
index from backup data option to continue loading the tree.
Alternatively, you can click the Global Setting for Restoring Content, Property and Security link
at the top of the Data Selection interface and configure the Item Level Settings:
•
Restore Granular Content – Select this option to restore granular content. If you are
browsing the tree to load the contents under site collections, the Restore Granular
Content option will be automatically selected to enable the restore of the granular
contents under the site collection level. If you deselect the Restore Granular Content
option, the tree is reloaded and you can only browse the tree to the site collection level.
For details, refer to Deselecting the Restore Granular Content Feature.
•
Browse Method ─ Choose whether or not to browse the tree from the index generated
from the backup data. The current granular level of your stored index in the backup data
be displayed in bold on the left side of the interface.
o
Browse the index from backup data – When this option is selected, a
SharePoint content database backup snapshot is first mounted as a temporary
database. Users can then browse and restore specific granular content. This
option will appear slower when the first browse request is processed. Note that
the tree is generated in real time and can be displayed down to item version
level regardless of the database’s original restore granularity.
By default, the mounted temporary database is stored on the default
verification server. To choose another verification server, select a pre-defined
verification and index policy from the drop-down list, or click the New
Verification and Index Policy link in the drop-down list to create a new
verification server. For more information, refer to About the Verification and
Index Policy.
•
Container Selection ─ Select the Global setting for container configuration checkbox to
enable the container’s global settings. A container refers to site collections, sites,
lists/libraries, or folders in SharePoint.
o
80
Restore container – Select this option to restore the container in the selected
backup data. Select the Security checkbox if you want to restore the container’s
SMSP 8.1 Platform Backup and Restore User’s Guide
security settings, and/or select the Property checkbox if you want to restore the
container’s property settings. For more information, refer to Appendix A.
o
Only restore security ─ Select this option to restore only the container’s security
settings. You can specify the Conflict resolution as Merge or Replace. Merge
will add the security of the container in the backup to the conflict container in
the destination. Replace will delete the security of the conflict container in the
destination first, and then add the security of the container in the backup to the
conflict container in the destination.
*Note: The Only restore security feature takes effect only if the selected nodes
do not inherit security from their parent nodes.
*Note: Once you select Only restore security option, the Container level
conflict resolution configuration field in the Restore Settings page will only
display Skip and you will not be able to configure the other Container level
conflict resolution through that page.
•
Content Selection ─ Select the Global setting for content configuration checkbox to
enable the content’s global settings. Content refers to the documents or files in libraries
or items in lists.
o
Restore content ─ Select this option to restore the contents in the selected
backup data. Select the Security checkbox if you want to restore the content’s
security settings as well. For more information, refer to Appendix A.
o
Only restore security ─ Select this option to restore only the content’s security
settings. You can specify the Conflict resolution as Merge or Replace. Merge
will add the security settings of the content in the backup into the conflict
content in the destination. Replace will delete the security settings of the
conflict content in the destination first, and then add the security of the content
in the backup to the conflict content in the destination.
*Note: The Only restore security feature takes effect only if the selected nodes
do not inherit security from their parent nodes.
*Note: Once you select Only restore security option, the Content level conflict
resolution configuration field in the Restore Settings page will display Skip only.
You will not be able to configure the other Content level conflict resolution
through that page.
4. Expand the tree and locate the content you want to restore. The detailed information can be
viewed in the popped up Item Browser window. Specify the configuration of the
container/content being restored.
a. Security – Refer to Appendix E: SharePoint Object Security and Property.
b. Property – Refer to Appendix E: SharePoint Object Security and Property
SMSP 8.1 Platform Backup and Restore User’s Guide
81
*Note: To out-of-place restore a catalog site collection to a destination Web application or site
collection, you must configure the following settings:
a. Select the catalog site collection from the Backup Data tree. Use the Find Site Collection
feature as a quick method. For details, refer to Appendix A: About Find Site Collection.
b. Click Next. In the Restore Type interface, select the Out of place restore option.
c. In the Destination field, select a destination Web application or site collection.
d. Action – Select how the data will be restored to the destination.
o
Merge – If you selected a site collection as the destination, select Merge. Merge
will add the site collection to the destination site collection.
o
Attach – If you select a Web application as the destination, select Attach. Attach
will restore the site collection as children beneath the selected Web application.
e. In the Restore Settings interface, the Use as App Catalog Site field is available to
configure. Select Yes to restore the current site collection as the app catalog site for the
destination Web application. Otherwise, select No.
f.
For details on other settings, refer to the information in this section.
5. When finished, click Next. The Stub and BLOB Configuration page appears.
*Note: The Stub and BLOB Configuration page is available when the backup data selected for a
granular level restore contains stubs. Configure the Stub Database Settings and BLOB Settings
to choose to restore granular data from the backed-up stub database/BLOB data or from the
original Storage Manager/Connector device.
6. Stub Database Settings – Choose whether or not to restore the granular data from the backedup stub database in the Use Backed up Stub Database field.
•
Select Yes to restore the granular data from the backed up stub database. If you select
Yes, you are required to specify which backup method you have used.
o
Default Platform Backup – Use the stub database that has been backed up by
Platform Backup job to restore.
o
Other/Third Party Backup – Select this option if the stub database was backed
up by other/third party tools (for example, the SQL Server backup method), and
you must manually restore and stage the stub database onto the destination
SQL Server.

•
82
Database Access Credentials – Enter the SQL instance name where the
stub database resides and the stub database name. Specify the
database authentication to use to access the customer backed up stub
database.
Select No to restore the granular data from the original Connector device.
SMSP 8.1 Platform Backup and Restore User’s Guide
7. BLOB Settings – Choose whether or not to restore the granular data from the backed up BLOB
data.
•
Select Yes to restore the granular data from the backed up BLOB data. If you select Yes,
you are required to specify which backup method you have used.
o
Default Platform Backup – Use the BLOB data that has been backed up by
Platform Backup job to restore.
o
Other/Third Party Backup – Select this option if the BLOB data was backed up
by other/third party tools (for example, the SQL Server backup method), and
you must manually restore the BLOB data to a location that must be configured
as a logical device.

•
Logical Device – Select the logical device where the BLOB data has been
staged from the Logical device drop-down list.
Select No to restore the granular data from the original Storage Manager/Connector
storage device.
8. Click Next. The Restore Type page appears.
9. Restore Type – Choose how the content will be restored.
*Note: You cannot restore backed-up SharePoint 2010 data to SharePoint 2013, nor can you
restore backed-up SharePoint 2013 data to SharePoint 2010. Make sure that the source node
and the destination node are the same version of SharePoint. If the site within SharePoint 2013
is a SharePoint 2010 Mode site, the content can only be restored to a SharePoint 2013 site that
is in SharePoint 2010 mode.
SMSP 8.1 Platform Backup and Restore User’s Guide
83
a. Restore Type – Select the location where to restore the backup data. In this case, select
Out of place restore to restore the content to another SharePoint farm or a different
location in the original farm.
Figure 39: Out of place restore.
b. Restore From Alternate Storage Location ─ Use this option to restore data from an
alternate storage location by manually cloning the databases in SMSQL. For more
information, refer to Restoring from an Alternate Storage Location.
c. Destination – Choose the destination for the restore job. You can either select an
existing node on the tree or select a manually created node. To create a node in the
destination SharePoint manually, perform the steps below.
o
Select a node with a blank textbox.
o
Enter the URL of the destination node into the textbox following the format
displayed in the textbox. If you are creating a new site collection, you will be
asked to select one existing managed path from the drop-down list.
o
Click Create Container beside the textbox to create the node in the destination
farm. Alternatively, click Create Container in the Manage group in the Timebased Restore tab to create the corresponding node.
To search your desired granular objects (from site collection level down to item level) in
the destination farm tree, use the Advanced Search feature. You can search your
84
SMSP 8.1 Platform Backup and Restore User’s Guide
desired objects from the selected destination scope (from the farm to folder level). For
more details on the Advanced Search interface, refer to Appendix B: About Advanced
Search.
d. Agent Group – Select the Agent group that will perform the restore job. Click View to
view the details of the selected Agent group.
e. Action – Select how the data will be restored to the destination, and preview the impact
of your selection.
o
Merge –Adds the contents to the destination node.
o
Attach – Restores the contents as children beneath the selected nodes.
To preview what the destination node data tree will look like after the job is executed,
click Preview. Only the unfolded tree structure in the Data Selection step can be
previewed in the destination tree. Click Hide Preview to hide the Preview area.
f.
Mapping Settings (Optional) – Configure whether to specify the mapping settings to
map the user, domain, displayed list or column label to the destination.
o
User Mapping – If desired, configure the user mapping to map the backed up
user to the destination user. For specific instructions on setting up the user
mapping, refer to the SnapManager for SharePoint Control Panel User’s Guide.
o
Domain Mapping – If desired, configure the domain mapping to map the
backed up domain to the destination domain. For specific instructions on setting
up the domain mapping, refer to the SnapManager for SharePoint Control Panel
User’s Guide.
o
Language Mapping – If desired, configure the language mapping to display a
destination node in a different language than the language of the backed-up
data. For specific instructions on setting up the language mapping, refer to the
SnapManager for SharePoint Control Panel User’s Guide.
10. Click Next when finished. The Restore Settings page appears.
11. Restore Settings – Configure how the content will be restored.
a. Conflict Resolution – Specify the action to resolve container level and content level
conflicts that arise during a Platform granular restore.
o
Container Level Conflict Resolution – Set the conflict resolution on the site
collection, site, list, and folder levels.

Skip – Ignores the source container that conflicts with the destination
one.

Merge – Combines the configuration of the source and destination
containers. If there is a conflict, the source configuration overwrites the
destination’s configuration.
SMSP 8.1 Platform Backup and Restore User’s Guide
85

Replace – Deletes the destination container and then restores the
source container to the destination. If the selected container is a toplevel site, Replace function empties the top-level site instead of deleting
it and restores the source top-level site to the destination. This option
can only be used at folder/list/library/site/site collection level.
*Note: As the replace conflict resolution deletes the destination
container before performing the restore, make sure the destination
container is no longer needed before performing the restore using this
conflict resolution.
o
Content Level Conflict Resolution – Set the conflict resolution on the item level.

Skip – Ignores the source item/document that has the same item
ID/document name as the destination item/document.

Overwrite – Copies the source item/document to the destination by
overwriting the destination item/document with same item
ID/document name.

Overwrite by Last Modified Time – Keeps the conflict item/document
that has the latest modified time and overwrites the older one.

Append an Item/Document with a Suffix – Keeps both of the conflict
items/documents and adds a suffix (_1, _2, _3…) to the name of the
conflict source item/document.

Append a New Version – Adds the conflict source item/document to
the destination as a new version of the conflict destination
item/document.
b. Apps Conflict Resolution – Define the conflict resolution behavior that occurs if there is
a conflict with Apps in the source and destination. You can choose “Skip”, “Update App
Only”, or “Replace App and AppData” from the drop-down list. To successfully restore
the SharePoint Apps, make sure the Agent account of the Agent account to perform the
restore job is not a Local system account.
o
Skip – Ignore the source App that has the same name as the destination one.
o
Update App Only – If the source App is in a more recent version than the
destination one, the destination App will be updated, but with the original
destination AppData remained.
o
Replace App and AppData – The source App will replace the destination App
and AppData, even if it is in a lower version.
c. Include Recycle Bin Data – Choose whether to compare the data in the backup with the
data in the destination SharePoint farm’s recycle bin. If you select Skip either at the
Container level or Content level, or you select the Append an Item/Document Name
with a Suffix or Append a New Version at the Content level, the Include Recycle Bin
Data option is available to configure. If you select Yes in this field and the selected
86
SMSP 8.1 Platform Backup and Restore User’s Guide
content in the backup still exists in the recycle bin of the destination SharePoint farm,
the selected content in the backup is not restored.
d. Include Detailed Job Report for All Items – Selecting Yes generates a detailed job report
for all the items. Selecting No still generates a job report, but only in truncated list form.
e. Verification and Index Policy – Select a verification and index policy from the dropdown list. Here you can designate one or more database servers for verifying the
database backup data and generating the granular level index. By default, SnapManager
for SharePoint uses the SQL Server that contains the data you are about to restore.
If you do not want to use the default mount point directory, you can select the Assign
Mount Point option to specify the mount point directory.
f.
Workflow – Decide how the backed-up workflows are restored.
o
Include workflow definition – Only restores the definition of the backed-up
workflows.
o
Include workflow instance – Restores the state, history, and tasks for each
item.
*Note: All workflow instances whose status was In Progress when backed up
will be Cancelled when restored to the destination.
g. Item Dependent Columns and Content Types – Choose whether to restore itemdependent columns and content types.
*Note: If you did not select Property beside the selected node in the Data Selection
step and the dependent column or content type does not exist in the destination, the
column or content type will not be restored. If this is the case, use this option to restore
them.
o
Restore the item-dependent columns and content types to maintain item
integrity – The item is restored and the dependent column or content type is
created in the corresponding list/library. The item still uses the dependent
column and content type.
o
Do not restore item-dependent columns and content types – The itemdependent columns and dependent content types will not be restored. When
selecting this option, make sure the dependent columns and content types exist
in the destination. Otherwise, the item cannot be restored.
h. Exclude User/Group Without Permission ─ If you select Yes, the users/groups that have
no permissions will not be restored. By default, No is selected.
i.
Version Settings – Choose the Version Settings for the content being restored to
SharePoint. To improve performance, limit the versions restored. Restore all versions
restores all the versions of the backup data; while Restore the latest version(s) only
restores the latest several Major or Major and Minor versions of the backup data as
designated. The other versions are not restored. Note that the current version will
SMSP 8.1 Platform Backup and Restore User’s Guide
87
always be restored together with the entered number of Major or Major and Minor
versions.
j.
Notification – Configure the e-mail Notification settings. Select a previously configured
notification profile from the Select a profile with address only drop-down list. You can
also choose to create a new e-mail notification profile by clicking the New Notification
Profile link. Click View to view the detailed configuration of the selected notification
profile.
12. When finished configuring Restore Settings, click Next. The Schedule page appears.
13. Schedule – Choose whether or not to create the restore job based on a schedule. Select Restore
immediately after wizard finishes to run the job immediately after finishing the restore wizard.
To configure the schedule yourself, select Configure the schedule myself and input a start time
in Schedule Settings field. If desired, enter an optional Description to distinguish the restore job
from others.
14. When finished, click Next. The Overview page appears.
15. Review and edit the job selections. To make changes, click Edit in the middle of the row on the
Settings tab to go to the corresponding settings page. This links to the corresponding setting
page, allowing you to edit the configuration. In the Preview tab, you can view the restore action
and the expected farm tree after the restoration, or click Edit to go to the Restore Type
interface to change the restore action.
16. Click Finish to save the job’s configuration. If the restore job does not have a schedule, Finish
runs the job immediately. If the restore job is set to run on a schedule, Finish saves the restore
job’s configuration without running it.
88
SMSP 8.1 Platform Backup and Restore User’s Guide
Restoring a Database to a Point in Time
In a point-in-time restore, databases are restored to a point in time selected from the timeline browser.
A point-in-time restore occurs in two restore scenarios:
•
The database is restored to a given time from a backed up transaction log.
•
The database is restored but only a subset of backed up transaction logs are applied to
it.
*Note: Performing a point-in-time database recovery results in a new recovery path.
The following image illustrates the potential problems when a point-in-time restore is performed.
Figure 40: Recovery Paths.
In this image, Recovery path 1 consists of a Full backup followed by a number of transaction log backups
(a point-in-time backup). New transaction log backups are created after the point-in-time restore takes
place, which results in Recovery path 2. It is not possible to tie the transaction logs created in Recovery
path 2 to the Full backup belonging to Recovery path 1. Therefore, to preserve database integrity, the
only way to restore the database to its most current state after a point-in-time restore is to complete a
new Full backup that has only one recovery path.
*Note: To avoid the problems listed previously, ensure that you always create a Full backup after
restoring a database to a point-in-time.
Restoring from an Alternate Storage Location
This option restores data from an alternate storage location other than your primary storage (for
example, data stored on a SnapMirror copy or as a SnapVault backup). The data will be restored
manually using other tools (like SnapManager for Microsoft SQL Server); you will need to locate the
database backup snapshot using the prompt and restore the data in SnapManager for Microsoft SQL
Server.
For database level restore:
SMSP 8.1 Platform Backup and Restore User’s Guide
89
1. If you have selected Restore from Alternate Storage Location, SnapManager for SharePoint
begins preparing for the restore after you have configured the notification profile and clicked
Next. During this preparation process, the selected databases will be detached from the
SharePoint environment.
2. After the restore preparation successfully completes, detailed information regarding all related
components for manual restore is listed in the Related Component page. Perform a manual
restore of the necessary components. For example, if restoring a content database, you must
perform a database restore to the selected content database.
Figure 41: The Related Component interface.
3. For instructions regarding a restore from an alternate source, see the SnapManager for SQL
Server Administrator’s Guide.
4. After the manual restore completes, click the Verify button to continue the restore process.
SnapManager for SharePoint attempts to verify the manually restored components and
completes the restore. If the verification or the restore fails, a list of errors detected is
displayed.
For item level restore:
1. If you have selected Restore from Alternate Storage Location, the content database where the
selected items reside will be displayed in the Related Component page after you have
configured the restore settings and clicked Next. Perform a clone restore to the content
database where the selected items reside.
90
SMSP 8.1 Platform Backup and Restore User’s Guide
Figure 42: The Related Component interface.
2. For instructions regarding a restore from an alternate source, see the SnapManager for SQL
Server Administrator’s Guide.
3. Once the original content database is restored to a temporary database, click the Verify button
to continue the restore process. SnapManager for SharePoint uses the manually cloned
temporary database to complete the restore process. After the restore is completed, the
detailed information about the restore is displayed.
Cloning SharePoint Components for Restore
This option, which is essentially an out of place restore at the database level, allows users to restore
selected SharePoint components by cloning backup data to the destination farm. The Clone to another
farm feature restores backed-up Web applications and content databases only. If BLOB data or a stub
database is being backed up with the selected Web application or content database, the BLOB data and
the stub database will be cloned to the destination farm as well.Refer to the instructions below for more
information about cloning SharePoint components for restore:
1. After you have selected the backed-up content databases or Web applications from the backup
data tree in the Data Selection step, click Next to go to the Restore Type step.
SMSP 8.1 Platform Backup and Restore User’s Guide
91
2. Restore Type – In the Restore Type field, select the Clone to another farm option. Select a
destination farm from the drop-down list.
Figure 43: Select the Clone to another farm option.
92
SMSP 8.1 Platform Backup and Restore User’s Guide
3. Click Next to go to the SnapShot Selection page. Click Load Remote Snapshot on the ribbon to
load the remote snapshots in the SnapVault. After the remote backups are loaded in the tree,
select local or remote snapshots for the selected content database. Click View Details next to
the snapshot to view the content databases. Make sure that all of the selected content
databases have the corresponding local or remote snapshots selected.
Figure 44: The Snapshot Selection page.
SMSP 8.1 Platform Backup and Restore User’s Guide
93
4. Click Next to go to the Destination Component Options page to configure the cloned
components’ settings in the destination.
Figure 45: Configuring the destination component options.
5. Click Configure under the Destination Configuration column to configure the destination
settings of each clone component, such as Web application, content database, or stub database
(if you have the stub database backed up with the selected content database or Web
application). The configuration options are the same as creating a new Web application, or
configuring the content database settings during new Web application creation. Also, the stub
database configuration is similar to the content database configurations that are made during
new Web application creation.
6. Click Next. The Physical Device Mapping page appears. Note that if no BLOB data is backed up,
this step will be skipped.
7. Physical device mapping clones BLOBs in the source physical device to the designated
destination physical device. Select the physical device from the Clone to Physical Device column.
Note that only physical devices used by Storage Manager display and map to the destination
physical device.
*Note: A source physical device can only be mapped to one destination physical device. In
addition, if you edit the restored items/documents from the SharePoint site collection, the BLOB
94
SMSP 8.1 Platform Backup and Restore User’s Guide
data in the destination physical device will be orphaned and the stub will be converted to real
content. The content will be stored in the content database where the items/documents reside.
*Note: If your backed-up content database contains file stream data, you must install the RBS
provider in the destination SharePoint farm.
You can map all of the selected source physical devices to the same destination physical device
in batch. To do this, complete the steps below:
a. Select one or more checkboxes beside the physical device mapping items, and then click
Destination Physical Device on the ribbon. The BLOB Batch Settings Page appears.
*Note: Source physical devices that are different storage types cannot be selected
together. Only physical devices that are the same storage type as the selected source
physical devices can be displayed and selected as the Clone to Physical Device.
b. Choose a destination physical device from the drop-down list. Click Show to view the
path and usage information of the selected physical device.
c. Click OK to save the batch settings and return to the Physical Device Mapping interface.
*Note: If the source physical devices are included in a BLOB storage logical device, the clone
physical devices function in the destination does not automatically recognize the relationship as
a BLOB storage logical device.
Figure 46: Configuring the physical device mapping.
8. Click Next. The Restore Settings page appears.
9. Restore Settings – Choose detailed settings for the restore job.
•
Conflict Resolution – Select Overwrite or Skip to decide whether to overwrite the
conflicting content in the destination.
SMSP 8.1 Platform Backup and Restore User’s Guide
95
•
Notification – Configure the e-mail notification settings. Select a previously configured
notification profile from the Select a profile with address only drop-down list, or create
a new e-mail notification profile by clicking the New Notification Profile link. Click View
to view the detailed configuration of the selected notification profile.
10. Click Next. The Schedule page appears.
11. Schedule – Choose whether or not to create the restore job based on a schedule. Select Restore
immediately after wizard finishes to run the job immediately after finishing the restore wizard.
To configure the schedule yourself, select Configure the schedule myself and input a start time
in Schedule Settings field. If desired, enter an optional Description to distinguish the restore job
from others.
12. When finished, click Next. The Overview page appears.
13. Review and edit the job selections. To make changes, click Edit in the middle of the row. This
links to the corresponding setting page, allowing you to edit the configuration.
14. Click Finish to save the job’s configuration. If the restore job does not have a schedule, Finish
runs the job immediately. If the restore job is set to run on a schedule, Finish saves the restore
job’s configuration without running it immediately.
96
SMSP 8.1 Platform Backup and Restore User’s Guide
Options for Restoring Backed-up Web Front-end Files
In the Settings group on the Time-based Restore tab, there are two options that can be used to restore
the Web front-end files.
•
Installed Programs ─ This function is used for checking the program installation status
on the specified Web front-end server and the current program installation status when
backing up the Web front-end server components.
•
Download Backup List ─ This function is used for checking data status on the selected
Web front-end server and the current data status when backing up the specified Web
front-end server components. Click the Download Backup List button on the ribbon,
select the corresponding checkboxes, and click OK. A .zip file that contains detailed lists
is downloaded to the specified local path. The list is recorded in the .csv file in the .zip
file.
There are also two special restore settings for restoring the Web front-end files.
•
Restore Front-end File Security ─ This option only applies to the front-end files backed
up, including IIS site files (except the web.config file), SharePoint hive files and extra file
system files. When the option is used, both file contents and security permissions are
restored. Otherwise, only the file content is restored.
•
Restore Front-end File to Alternate Location ─ This option enables you to select a
location to restore the front-end files and templates files.
For more information on restoring backed-up Web front-end files, refer to the Platform Restore Support
Table.
SMSP 8.1 Platform Backup and Restore User’s Guide
97
Restoring Backed-up BLOB Data
If you selected to back up Storage Manger BLOB data or Connector BLOB data, a corresponding Storage
Manager or Connector node is generated in the backup data tree under the corresponding database.
After selecting the Storage Manager or Connector node, click the View Details next to the node to view
detailed BLOB backup data for the selected node. After selecting the data to restore and configuring the
desired settings, the backed-up BLOB data will be restored back to the corresponding Storage Path.
*Note: Only one BLOB node per restore is supported for granular level restores. If you want to perform
a platform restore job at a granular level, only one BLOB node (one Storage Manager or Connector node)
can be configured through the View Details link.
Figure 47: Restoring backed-up Connector and Storage Manager data.
98
SMSP 8.1 Platform Backup and Restore User’s Guide
Restoring Backed-up Stub Database
Select one stub database to restore the backed up stubs. For details on how to separately restore the
stub database, refer to the section below.
*Note: You can only select one stub database to restore at a time. You cannot select multiple stub
databases at the same time or select a content database at the same time for restore.
*Note: To restore the stub database, related BLOB data, and content databases to another SharePoint
farm, it is recommended that you perform a restore using the Clone to another farm restore type. For
details, refer to Cloning SharePoint Components for Restore.
1. Select a stub database node from the backup data tree. Click the View Details link beside the
node to view the detailed information about this stub database, such as the Content Database
Name, SQL Server, and Farm.
Figure 48: Select a stub database to restore.
SMSP 8.1 Platform Backup and Restore User’s Guide
99
Figure 49: View the details of the stub database.
2. Click the Next button at the bottom-right corner to go to the Restore Type page. Select Restore
to original Farm as the restore type and select an Agent group to execute the restore job.
3. Click the Next button at the bottom-right corner to go to the Restore Settings page.
4. In the Restore Settings page, configure the options according to your requirements. For the
detailed explanation of each option, refer to the Building a Restore Plan at Database Level.
In this case, select Overwrite as the Conflict Resolution and click the Next button at the bottomright corner to go to the Schedule page.
5. In the Schedule page, configure the schedule settings according to your requirements. When
you select Configure the schedule myself, the restore job will be started at the designated Start
time that you configure. For the detailed explanation of each option, refer to Building a Restore
Plan at Database Level.
In this case, use the default settings and click the Next button at the bottom right corner to go
to the Overview page.
6. In the Overview page, you can view all the previously configured settings. Once you are satisfied
with all the configurations, click Finish to start the out of place Platform Restore job.
100
SMSP 8.1 Platform Backup and Restore User’s Guide
Restoring Backed-up Database Master Key
If you restore the backed-up database, the backed-up database master key will be restored together.
While if you want to only restore the backed-up database master key, complete the following steps:
1. Navigate to ……\NetApp\SMSP8\Agent\data\SP2010\Platform on the Agent server included in
the Agent group. Open the SP2010PlatformConfiguration.xml file.
2. Find the RestoreMasterKey from the <FarmLevel> attributes. To only restore the database
master key, set the value of RestoreMasterKey to true.
3. Select the database from the backup data tree, whose database master key that you want to
restore.
4. Select Skip as the Restore Option.
5. Run the Platform Restore job to restore the backed-up database master key.
*Note: By default, the password of the database master key will be restored to 1qaz2wsxE.
Change it to your desired password after the restoration. For details, refer to
http://technet.microsoft.com/en-us/library/ms186937.aspx.
SMSP 8.1 Platform Backup and Restore User’s Guide
101
Deselecting the Restore Granular Content Feature
Deselecting the Restore Granular Content checkbox disables granular content selection. This restore
method can only be used for a Platform granular restore that is performed at the site collection level,
either in place or out of place. If the whole site collection needs to be restored, it is recommended to
perform the restore at site collection level and deselect the Restore Granular Content checkbox. In this
case, the restore is similar to STSADM site collection level restore. It is faster and can keep internal
document IDs.
*Note: If you select a SharePoint 2013 site collection to restore with the Restore Granular Content
option deselected, the apps in the site collection will not be restored.
102
SMSP 8.1 Platform Backup and Restore User’s Guide
Restore Details for Specific Farm Components
The following lists some of the details and conditions pertaining to restoring the farm components.
•
Configuration database – This is the core component of the SharePoint farm. It can only
be restored using Restore Database Only. The SharePoint Configuration database can
only be backed up and restored if the backup/restore includes the SharePoint Central
Administration Content database. It is also recommended that you restore the
SharePoint Central Administration Content database together with the SharePoint
Configuration database to avoid breaking the relationship between these two
databases.
•
Web applications – Web applications can be selected from the farm tree and restored;
this includes the settings and associated IIS sites. Content databases under Web
applications are also restored, if selected. However, if there are any changes to the IIS
sites (resulting from manual changes or third-party software), the IIS site backup on the
front-end Member Agent will also need to be restored.
•
Content databases – Content databases include SharePoint data such as site collections,
sites, lists, libraries, files, and all items. When a content database is restored, SMSP
automatically attaches them to the original Web application.
•
SharePoint solutions – When a SharePoint solution is restored, it is deployed to the
related Web applications with the same status that existed during backup. Depending
on the customizations contained in the SharePoint solution, the solution may need to be
re-configured after the deployment.
•
Front-end resources – If only out-of-the-box SharePoint features are used, there is no
need to restore the front-end resources, as everything is covered by the other farm
components. If there are manual customizations applied to the IIS site (including
Web.config), the IIS site should be restored. If customizations are self-contained within
the SharePoint 14/15 hive folder, they can be restored as well. Both IIS site files and
14/15 hive files can be restored out-of-place to another location for further
examination.
*Note: Certificates used by the IIS sites will not be backed up when backing up the
front-end resources. You must manually back them up and restore them.
*Note: Front-end resources cannot be restored together with other farm components.
They need to be restored separately after any other farm components are restored.
SMSP 8.1 Platform Backup and Restore User’s Guide
103
Backup and Restore FAST Search Server for SharePoint
2010 Farms
Microsoft FAST Search Server 2010 for SharePoint is a new search solution that delivers the power of
FAST with the simplicity and TCO of Microsoft. It provides the best general productivity search on the
market and makes it easy and economical to build high-value search applications. FAST Search Server
2010 for SharePoint provides high-end search features and can search huge corpus of data extremely
fast.
FAST Search Server 2010 for SharePoint solution consists of three main parts:
1. FAST Search Server 2010 for SharePoint ─ The server infrastructure that provides processing,
indexing, and query capabilities, and the administration of these features.
2. FAST Query Search Service Application (SSA) ─ The Query SSA provides the query Web frontend capabilities. You install and deploy this SSA on a SharePoint Web server, and it hosts query
Web parts and SDK query integration capabilities for your search solution.
3. FAST Search Connector (Content SSA) ─ The FAST Search Connector is a Search Service
Application (SSA) that retrieves content for indexing from SharePoint farms and other content
repositories. You install and deploy this SSA on a SharePoint application server.
Backing Up the FAST Search Server
Follow the steps below to back up the FAST Search Server:
*Note: If the FAST Search Server is installed on a NetApp LUN, SnapManager for SharePoint will perform
the snapshot backup. If the FAST Search Server is installed on the local disk, SnapManager for
SharePoint will send the backup data to the configured storage policy.
1. Login to SnapManager for SharePoint and navigate to Data Protection > Platform Backup &
Granular Restore > Platform Backup.
2. On the Backup tab, load the SharePoint farm tree in the Scope area to display the FAST Search
Server for SharePoint 2010 Farms node. Then expand the node.
3. Select the FAST Search Server Name (Admin) checkbox; a pop-up window appears, prompting
you to select the FAST Search Connector Service Application along with it. Click OK to select the
SSA or click Cancel to not select the SSA. Note that FAST Search Query Application is not
included in the backup tree.
104
SMSP 8.1 Platform Backup and Restore User’s Guide
4. Click Plan Builder on the ribbon and choose Wizard Mode or Form Mode to create the plan and
run it. You can view the job status in Job Monitor by clicking the corresponding button on the
ribbon.
Figure 50: Plan Builder Form Mode.
*Note: In step 3, selecting the FAST Search Server for SharePoint 2010 Farms node directly displays a
warning message reading The selected FAST Search Server nodes contain a large amount of content.
This indicates that when performing the backup, the FAST Search Admin Database nodes and FAST
Search Server nodes are included; the FAST Content SSA nodes are excluded.
SMSP 8.1 Platform Backup and Restore User’s Guide
105
Restoring the FAST Search Server
Follow the steps below to restore the FAST Search Server:
1. Login to SnapManager for SharePoint and navigate to Data Protection > Platform Backup &
Granular Restore > Platform Restore.
2. Configure the necessary settings and go to the Data Selection page.
3. In this page, select the FAST Search Server Name (Admin) checkbox; a pop-up window appears,
prompting you to select the FAST Search Connector Service Application along with it. Click OK to
select the SSA or click Cancel to not select the SSA.
Figure 51: Restoring the FAST Search Server.
4. Only In Place restore type and Overwrite/Skip restore options are supported.
5. In the Advanced field:
106
SMSP 8.1 Platform Backup and Restore User’s Guide
Figure 52: The Advanced field.
a. If you do not select any checkbox, it will only restore the backed up files on the backedup FAST Search Server.
b. When selecting the Configure FAST Certificate checkbox:
o
If you select the Use the certificate from backup option, enter the correct
certificate password to restore the certificate.
o
If you select the Generate new FAST certificate(self-signed) option, enter a
valid certificate password to create a new certificate.
*Note: If you select the Configure FAST Search Server checkbox, the Configure FAST
Certificate checkbox is selected automatically. Then, enter the correct FAST admin
password to configure the FAST Search Server. Also note that the Configure FAST Search
Server checkbox cannot be used for the updated SMSP 6.1 FAST Search Server backup
data.
6. Configure the other settings and click Finish on the Overview page to start the restore job. You
can view the job status in Job Monitor by clicking the corresponding button on the ribbon.
Supported and Unsupported List
Refer to the information below for the supported and unsupported components for the FAST Search
Server.
Component
FAST Search Center Site
FASTSearchCert
Location
On SharePoint server
On Stand-alone FAST server
On FAST admin server
SMSP 8.1 Platform Backup and Restore User’s Guide
Support Status
Supported
Supported
Supported
Supported
107
Component
FAST Search
Index(data_fixml)
FAST Search Connector
FAST Search Connector
proxy (NO proxy when
created)
FAST Search Query
FAST Search Query
proxy
108
Location
On FAST non-admin server
On Stand-alone FAST server
On FAST primary non-admin server
On FAST secondary non-admin server
Content Source
Crawl rule
Support Status
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Unsupported
Supported
Supported
SMSP 8.1 Platform Backup and Restore User’s Guide
About Platform Backup and Restore for SQL Mirroring
Database
If there are principal databases and mirroring databases in SQL Server, you can use a platform backup to
back up your principal databases.
Note that if you choose SQL authentication as a content database’s database authentication in
SharePoint, make sure that the Agent account has sufficient permissions to log into the destination SQL
Server. Otherwise, the mirroring databases cannot be backed up when being used as failover databases.
*Note: Before performing an In Place Restore at the database level, you must manually terminate the
mirroring relationship because a database cannot be deleted or overwritten when it is mirrored. After
completing the In Place Restore at database level, you can manually re-create the mirroring relationship.
SMSP 8.1 Platform Backup and Restore User’s Guide
109
About Platform Backup and Restore for Failover
Database
Refer to the section below for the information of the SharePoint 2010 failover databases supported for
Platform Backup and Restore.
•
Content Database
•
Admin Content Database
•
State Service Database
•
Business Data Connectivity Service Database
•
PerformancePoint Service Application Database
•
Managed Metadata Service Database
•
Web Analytics Service Databases
•
Word Automation Service Database
•
Secure Store Service Application Database
•
Search Service Application Databases
•
Form Based Authentication (FBA) Database
•
Usage and Health Service Database
•
User Profile Service Databases
•
Help Search Database
•
Subscription Service Database
•
Session State Service Database
•
Application Registry Service Database
Refer to the section below for the information on the SharePoint 2013 failover databases supported for
Platform Backup and Restore.
110
•
Content Database
•
Admin Content Database
•
State Service Database
•
Business Data Connectivity Service Database
•
PerformancePoint Service Application Database
•
Managed Metadata Service Database
SMSP 8.1 Platform Backup and Restore User’s Guide
•
Word Automation Service Database
•
Secure Store Service Application Database
•
Search Service Application Databases
•
Form Based Authentication (FBA) Database
•
Usage and Health Service Database
•
User Profile Service Databases
•
App Management Service Database
•
Subscription Service Database
•
Session State Service Database
•
Application Registry Service Database
•
Machine Translation Service Database
SMSP 8.1 Platform Backup and Restore User’s Guide
111
Checking a Job Status
Platform Backup and Restore contains a Job Monitor button where users can view the status of jobs.
This is useful for monitoring jobs or troubleshooting for errors. For Platform granular restore job, users
can check the Object Details, Configuration Details, and Security Details in Job Monitor for more
detailed information.
For backup jobs or restore jobs that contain BLOB data, the BLOB Details tab appears on the Job Details
page.
For Stopped Platform Backup jobs and Platform Restore jobs, you can also view job settings in Job
Monitor.
Refer to the SnapManager for SharePoint Job Monitor User’s Guide for more information.
112
SMSP 8.1 Platform Backup and Restore User’s Guide
Troubleshooting for Platform Backup and Restore
Refer to the section below for SMSP Platform Backup and Restore troubleshooting.
Cannot See the Farm in Migrate Index Wizard
When using the Migrate Index tool, you may find that the farm you want to select does not appear in
the Farm Selection drop-down list.
Try the following to solve this issue:
•
Go to Control Panel > Agent Monitor to verify that the correct Agent type is selected. If
not, select it.
•
Verify that the Agent is active by going to Control Panel > Agent Monitor. If the Agent is
not active, go to the Agent machine to check whether the Agent service is down, or ping
the server where Control service resides to check the connection.
•
Check whether the SMSP login user has permission to the desired farm by going to
Control Panel > Account Manager > Permission Level.
Cannot Load Remote Backups
In some cases, you may not be able to load remote backups from the Platform Restore wizard.
Try the following to solve this issue:
•
Make sure you have properly configured the SnapVault in your environment.
•
Ensure that the Archive backup to secondary storage option is selected in the Platform
Backup wizard. In the Run Now interface or backup schedule settings, select the Archive
backup to secondary storage option in the SnapVault field of the Advanced tab.
•
Download the backup job report. It may be that SMSQL failed to update SnapVault.
•
Log into the SQL Server where the local snapshot resides, and then use SMSQL to
browse the database and verify that the remote snapshot exists.
•
Log into the SQL Server where the local snapshot resides, and then execute the getbackup cmdlet. Check the output result for LocalBackup and RemoteBackup. True
means the local backup or the remote backup can be loaded.
SMSP 8.1 Platform Backup and Restore User’s Guide
113
Appendix A: About Find Site Collection
The Find Site Collection feature provides you with a quick method of finding a site collection in your
backup data by entering the URL or using wildcards.
*Note: The search scope is all of the content databases that have been backed up by the selected
backup job and that have a site collection-level index or lower.
1. On the Time-based Restore tab within the Data Selection step of the Restore Wizard, find the
Find Site Collection button on the ribbon.
2. Click the Find Site Collection button on the ribbon. The Find Site Collection interface appears.
Figure 53: The Find Site Collection interface.
3. Enter the URL into the text box ahead of the Search button. The search function supports
wildcards “*” and “?”.
4. You can configure the Advanced settings to specify the maximum number of search results.
a. Click the Advanced button to expand the tab.
114
SMSP 8.1 Platform Backup and Restore User’s Guide
b. Enter the maximum number of the search results you want to display. By default, the
maximum number is 1,000. Larger results to display, higher risks to encounter poor
efficiency. You can specify an integer between 1 and 5,000,000.
c. Click Apply to apply your advanced settings.
5. Click Search to search for the desired site collections.
SMSP 8.1 Platform Backup and Restore User’s Guide
115
Appendix B: About Advanced Search
Advanced Search provides a quick method for locating specific objects or data within each granular level
(from site collection level down to item level). You can use Advanced Search in the Time-based Restore
at the granular level to search for granular content to restore and to select a node in the destination
farm for the granular content you are about to restore.
1. On the Time-based Restore tab within the Data Selection step of the Restore Wizard, select the
database that you want to restore the granular data from.
2. Click View Granular Content beside the database, and then select the Restore Granular Content
option on the Restore Granular Level field.
3. Click OK to proceed to restore the granular data, and then specify the search scope by clicking
the object name in the Backup Data tree.
4. In the Search group on the ribbon, click Advanced Search. The Advanced Search page appears.
5. The granular object levels that equals or lower than the ones you select in the backup tree are
listed in the drop-down list before the Add Criteria button. The value supports wildcard (*).
Using Advanced Search, you can search:
Level
Site
Collection
URL
Rule
Modified
Time
116
Condition
Matches
Value
sitecollection
Equals
http://test:20000/sites/sit
ecollectionA
Before
2013-12-27 16:41:00
(UTC+08:00) Beijing,
Chongqing, Hong Kong,
Urumqi)
After
2013-12-27 16:41:00
(UTC+08:00) Beijing,
Chongqing, Hong Kong,
Urumqi)
Between
From 2013-12-12 16:41:00
(UTC+08:00) Beijing,
Chongqing, Hong Kong,
Urumqi) To 2013-12-27
16:41:00 (UTC+08:00)
Beijing, Chongqing, Hong
Result
Searches for the site collection
whose URL matches
sitecollection.
Searches for the site collection
whose URL equals
http://test:20000/sites/sitecoll
ectionA.
Searches for the site collection
whose last modified time is
earlier than 2013-12-27
16:41:00 (UTC+08:00) Beijing,
Chongqing, Hong Kong,
Urumqi)
Searches for the site collection
whose last modified time is
later than 2013-12-27 16:41:00
(UTC+08:00) Beijing,
Chongqing, Hong Kong,
Urumqi)
Searches for the site collection
whose last modified time is
between 2013-12-12 16:41:00
(UTC+08:00) Beijing,
Chongqing, Hong Kong,
Urumqi) and 2013-12-27
SMSP 8.1 Platform Backup and Restore User’s Guide
Level
Site
Rule
URL
Site Title
Modified
Time
List
Name
Modified
Time
Condition
Value
Kong, Urumqi)
Matches
siteA
Equals
http://test:20000/sites/sit
ecollectionA/siteA
Matches
A
Equals
siteA
Before
2013-12-27 16:41:00
(UTC+08:00) Beijing,
Chongqing, Hong Kong,
Urumqi)
After
2013-12-27 16:41:00
(UTC+08:00) Beijing,
Chongqing, Hong Kong,
Urumqi)
Between
From 2013-12-12 16:41:00
(UTC+08:00) Beijing,
Chongqing, Hong Kong,
Urumqi) To 2013-12-27
16:41:00 (UTC+08:00)
Beijing, Chongqing, Hong
Kong, Urumqi)
Matches
A
Equals
listA
Before
2013-12-27 16:41:00
(UTC+08:00) Beijing,
Chongqing, Hong Kong,
Urumqi)
After
2013-12-27 16:41:00
(UTC+08:00) Beijing,
SMSP 8.1 Platform Backup and Restore User’s Guide
Result
16:41:00 (UTC+08:00) Beijing,
Chongqing, Hong Kong,
Urumqi)
Searches for the site whose
URL matches siteA.
Searches for the site whose
URL equals
http://test:20000/sites/
sitecollectionA/siteA.
Searches for the site whose
title matches A.
Searches for the site whose
title equals siteA.
Searches for the site whose
last modified time is earlier
than 2013-12-27 16:41:00
(UTC+08:00) Beijing,
Chongqing, Hong Kong,
Urumqi)
Searches for the site whose
last modified time is later than
2013-12-27 16:41:00
(UTC+08:00) Beijing,
Chongqing, Hong Kong,
Urumqi)
Searches for the site whose
last modified time is between
2013-12-12 16:41:00
(UTC+08:00) Beijing,
Chongqing, Hong Kong,
Urumqi) and 2013-12-27
16:41:00 (UTC+08:00) Beijing,
Chongqing, Hong Kong,
Urumqi)
Searches for the list whose
name matches A.
Searches for the list whose
name equals listA.
Searches for the list whose last
modified time is earlier than
2013-12-27 16:41:00
(UTC+08:00) Beijing,
Chongqing, Hong Kong,
Urumqi)
Searches for the list whose last
modified time is later than
117
Level
App
Folder
Rule
Title
Name
Modified
Time
Item/Docum
ent
118
Title
Condition
Value
Chongqing, Hong Kong,
Urumqi)
Between
From 2013-12-12 16:41:00
(UTC+08:00) Beijing,
Chongqing, Hong Kong,
Urumqi) To 2013-12-27
16:41:00 (UTC+08:00)
Beijing, Chongqing, Hong
Kong, Urumqi)
Matches
A
Equals
AppA
Matches
A
Equals
folderA
Before
2013-12-27 16:41:00
(UTC+08:00) Beijing,
Chongqing, Hong Kong,
Urumqi)
After
2013-12-27 16:41:00
(UTC+08:00) Beijing,
Chongqing, Hong Kong,
Urumqi)
Between
From 2013-12-12 16:41:00
(UTC+08:00) Beijing,
Chongqing, Hong Kong,
Urumqi) To 2013-12-27
16:41:00 (UTC+08:00)
Beijing, Chongqing, Hong
Kong, Urumqi)
Matches
A
Equals
itemA
Result
2013-12-27 16:41:00
(UTC+08:00) Beijing,
Chongqing, Hong Kong,
Urumqi)
Searches for the list whose last
modified time is between
2013-12-12 16:41:00
(UTC+08:00) Beijing,
Chongqing, Hong Kong,
Urumqi) and 2013-12-27
16:41:00 (UTC+08:00) Beijing,
Chongqing, Hong Kong,
Urumqi)
Searches for the App whose
title matches A.
Searches for the App whose
title equals AppA.
Searches for the folder whose
name matches A.
Searches for the folder whose
name equals folderA.
Searches for the folder whose
last modified time is earlier
than 2013-12-27 16:41:00
(UTC+08:00) Beijing,
Chongqing, Hong Kong,
Urumqi)
Searches for the folder whose
last modified time is later than
2013-12-27 16:41:00
(UTC+08:00) Beijing,
Chongqing, Hong Kong,
Urumqi)
Searches for the folder whose
last modified time is between
2013-12-12 16:41:00
(UTC+08:00) Beijing,
Chongqing, Hong Kong,
Urumqi) and 2013-12-27
16:41:00 (UTC+08:00) Beijing,
Chongqing, Hong Kong,
Urumqi)
Searches for the item whose
title matches A.
Searches for the item whose
title equals itemA.
SMSP 8.1 Platform Backup and Restore User’s Guide
Level
Rule
Attribute
Modified
Time
Condition
Matches
Value
A
Equals
userA
Before
2013-12-27 16:41:00
(UTC+08:00) Beijing,
Chongqing, Hong Kong,
Urumqi)
After
2013-12-27 16:41:00
(UTC+08:00) Beijing,
Chongqing, Hong Kong,
Urumqi)
Between
From 2013-12-12 16:41:00
(UTC+08:00) Beijing,
Chongqing, Hong Kong,
Urumqi) To 2013-12-27
16:41:00 (UTC+08:00)
Beijing, Chongqing, Hong
Kong, Urumqi)
Result
Searches for the item whose
attribute matches A.
Searches for userA as one of
the attributes of the item.
Searches for the
item/document whose last
modified time is earlier than
2013-12-27 16:41:00
(UTC+08:00) Beijing,
Chongqing, Hong Kong,
Urumqi)
Searches for the
item/document whose last
modified time is later than
2013-12-27 16:41:00
(UTC+08:00) Beijing,
Chongqing, Hong Kong,
Urumqi)
Searches for the
item/document whose last
modified time is between
2013-12-12 16:41:00
(UTC+08:00) Beijing,
Chongqing, Hong Kong,
Urumqi) and 2013-12-27
16:41:00 (UTC+08:00) Beijing,
Chongqing, Hong Kong,
Urumqi)
6. Click Add Criteria to add a new filter condition. Change the logical relationship between the
filter rules by clicking the logic icon after the rule. There are two logics now: And and Or. The
default logic is And.
•
And – The content that meets all of the rules is searched out.
•
Or – The content that meets one of the rules is searched out.
7. Under the Basic Filter Conditions tab, view the search rules logical relationship.
8. Click Search to execute the search operation. The search results display under the Search Result
tab. View the search results in Tree View or List View by clicking the corresponding buttons
under the Search Result tab.
SMSP 8.1 Platform Backup and Restore User’s Guide
119
Appendix C: Supported SharePoint Components
Refer to the sections below for information on what components in SharePoint 2010 and SharePoint
2013 are supported in SnapManager for SharePoint.
SharePoint 2010 Components Supported in Platform Backup and
Restore
If you are backing up the whole content database and then restoring it using the database level restore,
all of the Web parts are supported in Platform Backup and Restore.
If you are using the Platform granular restore, refer to the table below for the supported and
unsupported Web parts in SnapManager for SharePoint Platform granular restore.
SharePoint 2010 Supported Web Parts
Business Data
Content Rollup
Filters
120
Web Part
Business Data Actions
Business Data Connectivity
Filter
Business Data Item
Business Data List
Business Data Related List
Chart Web Part
Excel Web Access
Indicator Details
Status List
Visio Web Access
Categories
Content Query
Relevant Documents
RSS Viewer
Site Aggregator
Sites in Category
Summary Links
Table Of Contents
Web Analytics Web Part
WSRP Viewer
XML Viewer
Apply Filters Button
Supported
√
Unsupported
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
SMSP 8.1 Platform Backup and Restore User’s Guide
Forms
Media and Content
Outlook Web App
Search
Social Collaboration
Web Part
Choice Filter
Current User Filter
Date Filter
Page Filed Filter
Query String(URL) Filter
SharePoint List Filter
Text Filter
HTML Form Web Part
InfoPath Form Web Part
Content Editor
Image Viewer
Media Web Part
Page Viewer
Picture Library Slideshow
Web Part
My Calendar
My contacts
My Inbox
My Mail Folder
My Tasks
Advanced Search Box
Dual Chinese Search
Federated Results
People Refinement Panel
People Search Box
People Search Core Results
Refinement Panel
Related Queries
Search Action Links
Search Box
Search Core Results
Search Paging
Search Statistics
Search Summary
Top Federated Results
Contact Details
Note Board
Organization Browser
Site Users
Tag Cloud
SMSP 8.1 Platform Backup and Restore User’s Guide
Supported
√
√
√
√
√
√
√
√
Unsupported
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
121
Web Part
User Tasks
Supported
√
Unsupported
SharePoint 2010 Service Applications Supported for Restore
Refer to the table below for the supported and unsupported SharePoint 2010 service applications for
SnapManager for SharePoint Platform Restore.
Supported in Inplace Restore
Service Application
Databases of the Service Application
Access Services
This Service Application does not have a database
√
Application Registry
Service
application registry service database
√
Business Data
Connectivity Service
Bdc_Service_DB(Business Data Connectivity Database)
√
Excel Services
Application
This Service Application does not have a database
√
Managed Metadata
Service
Managed Metadata Service_Database(Service
Application Database)
√
PerformancePoint
Service Application
PerformancePoint Service
Application_Database(Microsoft.PerformancePoint.Scor
ecards.BIMonitoringServiceDatabase)
√
Search Service
Application
Search_Service_Application_DB(Administration
Database)
√
Search_Service_Application_CrawlStoreDB(Crawl
Database)
Search_Service_Application_PropertyStoreDB(Property
Database)
Secure Store Service
Secure_Store_Service_DB(Secure Store Service
Database)
√
Security Token Service
Application
This Service Application does not have a database
√
122
SMSP 8.1 Platform Backup and Restore User’s Guide
Supported in Inplace Restore
Service Application
Databases of the Service Application
State Service
StateService_Database(State Service Database Settings)
√
Session State Service
SessionStateService_Database
√
SQL Server Reporting
Service
Reporting Service Database
√
User Profile Service
Application
Reporting Service Alerting Database
Reporting Service Temp Database
User Profile Service Application_ProfileDB
(Microsoft.Office.Server.Administration.ProfileDatabase)
√
User Profile Service
Application_SyncDB(Microsoft.Office.Server.Administrat
ion.SynchronizationDatabase)
User Profile Service Application_SocialDB
(Microsoft.Office.Server.Administration.SocialDatabase)
Visio Graphics Service
This Service Application does not have a database
√
Web Analytics Service
Application
WebAnalyticsServiceApplication_StagingDB(Web
Analytics Staging Database)
√
WebAnalyticsServiceApplication_ReportingDB(Web
Analytics Warehouse Database)
Word Automation
Services(Word
Conversion Service)
WordAutomationServices_Database(Microsoft.Office.W
ord.Server.Service.QueueDatabase)
√
Lotus Notes Connector
N/A
×
Usage and Health data
collection
WSS_Logging
Word Viewing Service
N/A
√
SMSP 8.1 Platform Backup and Restore User’s Guide
√
123
Supported in Inplace Restore
Service Application
Databases of the Service Application
PowerPoint Service
Application
N/A
√
Project Service
Application
This Service Application does not have a database.
Platform Backup and Restore backs up and restores the
databases of the Project 2010 PWA site:
ProjectServer_Published
ProjectServer_Draft
ProjectServer_Archive
ProjectServer_Reporting
√
SQL Server PowerPivot
Service Application
PowerpivotServiceApplication
√
Subscription Settings
Service Application
Subscription Settings Database
√
SharePoint 2010 Components Supported for Restore
Refer to the table below for the supported and unsupported SharePoint 2010 components for
SnapManager for SharePoint Platform Restore.
Features
Supported in In-place Restore
Configuration Database
√
Central Admin Web Application
√
Admin Content Database
√
Web Application
√
Content Database
√
Global Search Settings
√
SharePoint Help Search
√
InfoPath Form Services
√
124
Notes
Farm-level search settings and
Crawler impact rules are
supported.
InfoPath Forms Services Settings
and InfoPath Forms Services
SMSP 8.1 Platform Backup and Restore User’s Guide
Features
Supported in In-place Restore
Notes
Form templates are supported.
FBA Databases
√
The FBA Database and some
configurations in the Web.config
under WebApp IIS Setting (such
as MemberShipProvider) are
supported.
Windows SharePoint Solutions
√
For in place restore, restoring the
uploaded solution and its status
in the Solution Management is
supported.
FAST Search Server 2010 for
SharePoint
√
SMSP Platform Backup and
Restore backs up FAST
components, configuration files,
index data and so on. You can
also refer to the link below for
the manual full backup and
restore of FAST Search Server:
http://technet.microsoft.com/enus/library/ff460221.aspx
Knowledge Lake Imaging
√
BLOB
√
NewsGator
√
Social Sites (NewsGator) 1.2 and
2.5 are supported from
SnapManager for SharePoint.
Nintex Workflow
√
Nintex workflows can be restored
to their original location where
they were backed up.
Farm Level Backup and Item Level
Restore
√
If you want to do Platform
granular Restore, the Platform
granular Restore index must be
generated.
SMSP 8.1 Platform Backup and Restore User’s Guide
125
Features
Supported in In-place Restore
Notes
Web Front-End Server
√
•
IIS Settings (such as Form
Authentication, SSL
certification and so on) can
be configured individually on
the Web front-end server;
they are not saved in
SharePoint.
•
SharePoint Template
directory is the most
important directory to record
the IIS extensions. Files such
as feature files and site
definition files in the Web
front-end server are saved in
this directory.
•
SnapManager for SharePoint
Platform Backup and Restore
can also backup and restore
the files in the file system of
the Web front-end server.
SharePoint 2013 Components Supported in Platform Backup and
Restore
SharePoint 2013 Service Application Supported for Restore
Refer to the table below for the supported and unsupported SharePoint 2013 service applications for
SnapManager for SharePoint Platform Restore.
Service Application
Databases of the Service Application
Access Services
Access Services 2010
App Management
Service
Business Data
Connectivity Service
Excel Services
Application
Lotus Notes Connector
Machine Translation
This Service Application does not have a database
This Service Application does not have a database
AppMng_Service_DB (App Management Database)
126
Bdc_Service_DB(Business Data Connectivity Database)
Supported in Inplace Restore
√
√
√
√
This Service Application does not have a database
√
N/A
Machine Translation_Database
×
√
SMSP 8.1 Platform Backup and Restore User’s Guide
Service Application
Service
Managed Metadata
Service
PerformancePoint
Service Application
PowerPoint Conversion
Service Application
Project Service
Application
Search Service
Application
Secure Store Service
Security Token Service
Application
Session State Service
State Service
Subscription Settings
Service Application
SQL Server Reporting
Service
SQL Server Powerpivot
Service Application
Usage and Health data
collection
User Profile Service
Application
Visio Graphics Service
Word Automation
Services(Word
Databases of the Service Application
Managed Metadata Service_Database(Service
Application Database)
PerformancePoint Service
Application_Database(Microsoft.PerformancePoint.Scor
ecards.BIMonitoringServiceDatabase)
This Service Application does not have a database
This Service Application does not have a database.
Platform Backup and Restore backs up and restores the
databases of Project 2013 PWA site:
ProjectWebApp
Search_Service_Application_DB(Administration
Database)
Search_Service_Application_AnalyticsReportingStoreDB(
Analytics Reporting Database)
Search_Service_Application_CrawlStoreDB(Crawl
Database)
Search_Service_Application_LinksStoreDB(Link
Database)
Secure_Store_Service_DB(Secure Store Service
Database)
Supported in Inplace Restore
√
√
√
√
√
√
This Service Application does not have a database
√
SessionStateService_Database
StateService_Database(State Service Database Settings)
√
√
Subscription Settings Database
√
Reporting Service Database
Reporting Service Alerting Database
Reporting Service Temp Database
PowerpivotServiceApplication
√
WSS_Logging
User Profile Service Application_ProfileDB
(Microsoft.Office.Server.Administration.ProfileDatabase)
User Profile Service
Application_SyncDB(Microsoft.Office.Server.Administrati
on.SynchronizationDatabase)
User Profile Service Application_SocialDB
(Microsoft.Office.Server.Administration.SocialDatabase)
This Service Application does not have a database
WordAutomationServices_Database(Microsoft.Office.W
ord.Server.Service.QueueDatabase)
SMSP 8.1 Platform Backup and Restore User’s Guide
√
√
√
√
√
127
Service Application
Conversion Service)
Workflow Service
Application
Work Management
Service
128
Databases of the Service Application
Supported in Inplace Restore
N/A
√
This Service Application does not have a database
√
SMSP 8.1 Platform Backup and Restore User’s Guide
SharePoint 2013 Components Supported for Restore
Refer to the table below for the supported and unsupported SharePoint 2013 components for
SnapManager for SharePoint Platform Restore.
Features
Web Application
Content Database
Configuration Database
Central Admin Web
Application
Admin Content Database
Supported in In-place
Notes
Restore
√
√
√( Restore Database
Only must be used)
√
√
Windows SharePoint
Solutions
√
InfoPath Form Services
√
Global Site Template
Custom DB
Web Front-End Server
Item Level Restore
√
√
√
√
FBA Databases
√
BLOB
NewsGator
√
√
Nintex Workflow
√
SMSP 8.1 Platform Backup and Restore User’s Guide
For in place restore, restoring the uploaded
solution and its status in the Solution
Management is supported.
InfoPath Forms Services Settings and InfoPath
Forms Services Form templates are supported.
The FBA Database and some configurations in
the Web.config under WebApp IIS Setting (such
as MemberShipProvider) are supported.
Social Sites (NewsGator) 4.0 for SharePoint
2013 is supported in SMSP 8.1.
Nintex workflows can be restored to their
original location where they were backed up.
129
Platform Restore Support Table
*Note: Before you restore any content at the selected restore granularity, make sure that the related higher-level SharePoint objects are restored at the farm level or database level. For example, if you want to use the customized
feature correctly, you must restore the backed up features in the Custom Features node prior to restoring any SharePoint content that use this feature.
√ means the restore is Supported at this level and a blank area means the restore is Not Supported at this level.
Platform Restore with Specified
Granularity
What to Restore
Restore Level
SharePoint Central Administration and
SharePoint Configuration Database
130
Farm Level
√
Database
Level
Site
Collection
Level
Site Folder Item Item
Level Level Level Version
Level
√
Note
The SharePoint configuration database and the SharePoint
Central Administration content database are related to each
other; they can only be restored using In Place restore (with the
Restore Database Only option enabled).
If you do not select the Restore Database Only option, these
nodes will be skipped in the restore job (even if you have
selected to restore them).
SMSP 8.1 Platform Backup and Restore User’s Guide
What to Select When Restoring
(SharePoint 2010 Screenshots Shown Below)
Platform Restore with Specified
Granularity
What to Restore
Solutions
Restore Level
Database
Farm Level
Level
√
SMSP 8.1 Platform Backup and Restore User’s Guide
Site
Collection
Level
Site Folder Item Item
Level Level Level Version
Level
√
131
Note
What to Select When Restoring
(SharePoint 2010 Screenshots Shown Below)
Platform Restore with Specified
Granularity
What to Restore
Restore Level
Database
Farm Level
Level
Site
Collection
Level
Site Folder Item Item
Level Level Level Version
Level
InfoPath Form Services
√
132
√
SMSP 8.1 Platform Backup and Restore User’s Guide
Note
What to Select When Restoring
(SharePoint 2010 Screenshots Shown Below)
Platform Restore with Specified
Granularity
What to Restore
License to Feature Mappings
Restore Level
Database
Farm Level
Level
Site
Collection
Level
Site Folder Item Item
Level Level Level Version
Level
√
SMSP 8.1 Platform Backup and Restore User’s Guide
Note
This feature is specific to SharePoint 2013.
133
What to Select When Restoring
(SharePoint 2010 Screenshots Shown Below)
Platform Restore with Specified
Granularity
What to Restore
Restore Level
SharePoint Server State Service
134
Database
Farm Level
Level
√
Site
Collection
Level
Site Folder Item Item
Level Level Level Version
Level
√
SMSP 8.1 Platform Backup and Restore User’s Guide
Note
What to Select When Restoring
(SharePoint 2010 Screenshots Shown Below)
Platform Restore with Specified
Granularity
What to Restore
Web Application
Restore Level
Database
Farm Level
Level
√
Site
Collection
Level
Site Folder Item Item
Level Level Level Version
Level
Note
If you choose to overwrite an existing target Web application
using a backed-up Web application with the same name in an In
Place restore, the content database of the target Web
application will be deleted and replaced with the one in the
backup. However, the properties of the target Web application
will not be deleted.
√
For Web applications with extended zones, you can configure
the extended zones after clicking Show Other Zone Information.
SMSP 8.1 Platform Backup and Restore User’s Guide
135
What to Select When Restoring
(SharePoint 2010 Screenshots Shown Below)
Platform Restore with Specified
Granularity
What to Restore
Restore Level
Database
Farm Level
Level
Site
Collection
Level
Site Folder Item Item
Level Level Level Version
Level
Content Database
√
√
√
√
Sites with Content Types
√
√
√
√
136
√
√
SMSP 8.1 Platform Backup and Restore User’s Guide
√
Note
Features can be restored at farm level, database level, site
collection level, and site level. However, when restoring at site
collection and site level, SnapManager only restores the existing
status and using status of this feature; it does not restore the
features’ physical files, which are in …\Common Files\Microsoft
Shared\Web Server Extensions\14\TEMPLATE\FEATURES.
The content types in the site/site collection will be restored
together with the site/site collection.
What to Select When Restoring
(SharePoint 2010 Screenshots Shown Below)
Platform Restore with Specified
Granularity
What to Restore
Lists with Content Types
SharePoint Built-in Workflow
Restore Level
Database
Farm Level
Level
√
√
SMSP 8.1 Platform Backup and Restore User’s Guide
√
√
Site
Collection
Level
√
√
Site Folder Item Item
Level Level Level Version
Level
√
√
Note
√
The content types in the list will be restored together with the
list.
√
If you want to restore the workflow, you must select the
SharePoint object that is associated with the workflow on the
tree, and check the checkbox in front of Include workflow
definition/Include workflow instance. If you are restoring the
whole database, the workflow will be restored together with the
database, so there are no such options.
√
137
√
What to Select When Restoring
(SharePoint 2010 Screenshots Shown Below)
Platform Restore with Specified
Granularity
What to Restore
Restore Level
SharePoint Designer Customizations
Web Part
Database
Farm Level
Level
√
√
√
√
Site
Collection
Level
√
√
Site Folder Item Item
Level Level Level Version
Level
√
√
√
√
√
√
√
√
Note
The SharePoint Designer customizations can be restored
together with the selected content in the content database.
What to Select When Restoring
(SharePoint 2010 Screenshots Shown Below)
N/A
If you want to restore Web parts, make sure the content you
selected on the backup tree contains the Web parts you want to
restore.
N/A
The content you selected on the tree can be navigated down to
page and page version level.
Lists and items with Managed Metadata
Sites with Custom Templates
√
√
√
√
√
√
√
√
√
√
√
If you want to restore an item that uses managed metadata term
sets, make sure the related managed metadata service is
successfully restored at the database level first. Otherwise, the N/A
item cannot be associated with the specified managed metadata
term sets.
If the custom template is generated from the SharePoint built-in
site templates (typically from “Save site as template”), it will be
restored together with the site.
N/A
If the custom template is written by the customer, it may not be
usable after a Platform restore job because of template
138
SMSP 8.1 Platform Backup and Restore User’s Guide
Platform Restore with Specified
Granularity
What to Restore
Restore Level
Database
Farm Level
Level
Site
Collection
Level
Site Folder Item Item
Level Level Level Version
Level
Note
variation.
SPUserCode V4
√
SMSP 8.1 Platform Backup and Restore User’s Guide
Type: Microsoft SharePoint Foundation Sandboxed Code Service
√
Description: Settings for the Sandboxed Code Service.
139
What to Select When Restoring
(SharePoint 2010 Screenshots Shown Below)
Platform Restore with Specified
Granularity
What to Restore
Restore Level
Database
Farm Level
Level
Site
Collection
Level
Site Folder Item Item
Level Level Level Version
Level
Note
Global Search Settings
√
√
Type: Index files and Databases
SharePoint Foundation Help Search
√
√
Description: Search instances for Microsoft SharePoint
Foundation
*Note: The SharePoint Foundation Help Search is specific for
SharePoint 2010.
140
SMSP 8.1 Platform Backup and Restore User’s Guide
What to Select When Restoring
(SharePoint 2010 Screenshots Shown Below)
Platform Restore with Specified
Granularity
What to Restore
Restore Level
Database
Farm Level
Level
SMSP 8.1 Platform Backup and Restore User’s Guide
Site
Collection
Level
Site Folder Item Item
Level Level Level Version
Level
141
Note
What to Select When Restoring
(SharePoint 2010 Screenshots Shown Below)
Platform Restore with Specified
Granularity
What to Restore
Restore Level
Database
Farm Level
Level
Site
Collection
Level
Site Folder Item Item
Level Level Level Version
Level
Note
Search Service Settings: It is a virtual node that does not exist in
SharePoint and it contains the following components:
Search Service Application
√
√
•
Content Source
•
Crawl Rules
•
File Types
•
Crawl Impact Rules
•
Authentication Pages
•
Federated Locations
•
Metadata Properties
•
Scopes
The Search Service Settings node backs up the properties of the
search service application, so this node can only be restored to a
search service application when performing an out of place
restore.
For Restore Exported Federated Location, you can select No to
back up the properties and then restore them; or you can select
Yes to Export the federated location and then Import it.
Index Partition and Query Component: Under the Server dropdown list, all SharePoint servers that can run the Search Service
Instance will be displayed. Regardless of whether the service is
enabled or not, the service can be restored normally. After the
restore, the Search Service will be started on the specified
142
SMSP 8.1 Platform Backup and Restore User’s Guide
What to Select When Restoring
(SharePoint 2010 Screenshots Shown Below)
Platform Restore with Specified
Granularity
What to Restore
Restore Level
Database
Farm Level
Level
Site
Collection
Level
Site Folder Item Item
Level Level Level Version
Level
Note
SharePoint server.
SMSP 8.1 Platform Backup and Restore User’s Guide
143
What to Select When Restoring
(SharePoint 2010 Screenshots Shown Below)
Platform Restore with Specified
Granularity
What to Restore
Restore Level
Database
Farm Level
Level
Site
Collection
Level
Site Folder Item Item
Level Level Level Version
Level
Note
http (IISWebServiceEndPoint) and https
(IISWebServiceEndPoint) are the EndPoint groups of the IIS Web
Service. They are also called Service Application Endpoint Group
in SharePoint.
Service Application
√
√
Service Applications that have no database or proxy: Access
Services Service Application, Excel Services Application, and Visio
Graphics Service Application.
When restoring the service application proxy, a new proxy
having the same name and type will be created in the target
farm, and all of SharePoint will be restored and preserved.
144
SMSP 8.1 Platform Backup and Restore User’s Guide
What to Select When Restoring
(SharePoint 2010 Screenshots Shown Below)
Platform Restore with Specified
Granularity
What to Restore
Restore Level
FAST Search Server for SharePoint 2010
Farms
Database
Farm Level
Level
√
SMSP 8.1 Platform Backup and Restore User’s Guide
Site
Collection
Level
Site Folder Item Item
Level Level Level Version
Level
√
Note
This feature is specific to SharePoint 2010.
145
What to Select When Restoring
(SharePoint 2010 Screenshots Shown Below)
Platform Restore with Specified
Granularity
What to Restore
Restore Level
Database
Farm Level
Level
Site
Collection
Level
Site Folder Item Item
Level Level Level Version
Level
Note
NewsGator 1.2 and 2.5 for SharePoint 2010 and NewsGator 4.0
for SharePoint 2013 are supported in Platform Backup and
Restore.
NewsGator Social Site must be installed in the target farm first.
NewsGator Social Site
√
√
If you have uninstalled the NewsGator Social Site and want to
restore it, make sure all of the nodes are selected.
Only In Place restore type is enabled when restoring NewsGator
Social Site.
If NewsGator Service exists in the farm, select Overwrite to
overwrite the old files; if it has been uninstalled, either
Overwrite or Skip can be used.
146
SMSP 8.1 Platform Backup and Restore User’s Guide
What to Select When Restoring
(SharePoint 2010 Screenshots Shown Below)
Platform Restore with Specified
Granularity
What to Restore
Restore Level
Database
Farm Level
Level
SMSP 8.1 Platform Backup and Restore User’s Guide
Site
Collection
Level
Site Folder Item Item
Level Level Level Version
Level
147
Note
What to Select When Restoring
(SharePoint 2010 Screenshots Shown Below)
Platform Restore with Specified
Granularity
What to Restore
Restore Level
Database
Farm Level
Level
Site
Collection
Level
Site Folder Item Item
Level Level Level Version
Level
Note
Nintex Workflow 2010 or Nintex Workflow 2013 must be
installed in the target farm first.
Nintex Workflow
√
√
Only In Place restore type is enabled when restoring Nintex
Workflow.
If Nintex Workflow exists in the farm, select Overwrite to
overwrite the old one; if it has been removed, either Overwrite
or Skip can be used.
148
SMSP 8.1 Platform Backup and Restore User’s Guide
What to Select When Restoring
(SharePoint 2010 Screenshots Shown Below)
Platform Restore with Specified
Granularity
What to Restore
Restore Level
Database
Farm Level
Level
Site
Collection
Level
Site Folder Item Item
Level Level Level Version
Level
Note
This feature is specific to SharePoint 2010.
KnowledgeLake Imaging 2010
√
KnowledgeLake Imaging 2010 must be installed in the target
farm first. To back up and restore the KnowledgeLake Imaging
components, the KnowledgeLake Imaging service application
solution must be deployed on each server in the SharePoint
farm.
√
Only In Place restore type is enabled when restoring
KnowledgeLake Imaging 2010.
If KnowledgeLake Imaging exists in the farm, select Overwrite to
overwrite the old one; if it has been removed, either Overwrite
or Skip can be used.
SMSP 8.1 Platform Backup and Restore User’s Guide
149
What to Select When Restoring
(SharePoint 2010 Screenshots Shown Below)
Platform Restore with Specified
Granularity
What to Restore
150
Restore Level
Database
Farm Level
Level
Site
Collection
Level
Site Folder Item Item
Level Level Level Version
Level
SMSP 8.1 Platform Backup and Restore User’s Guide
Note
What to Select When Restoring
(SharePoint 2010 Screenshots Shown Below)
Platform Restore with Specified
Granularity
What to Restore
Custom Database
Restore Level
Database
Farm Level
Level
√
SMSP 8.1 Platform Backup and Restore User’s Guide
Site
Collection
Level
Site Folder Item Item
Level Level Level Version
Level
Note
You cannot select detailed content inside the database to
restore. You can only restore the whole database.
√
151
What to Select When Restoring
(SharePoint 2010 Screenshots Shown Below)
Platform Restore with Specified
Granularity
What to Restore
Restore Level
Database
Farm Level
Level
Site
Collection
Level
Site Folder Item Item
Level Level Level Version
Level
Note
If the data you want to restore does not exist in the destination,
the data will be restored to the destination regardless of
whether you choose the Overwrite or Skip option.
IIS Settings
152
√
√
SMSP 8.1 Platform Backup and Restore User’s Guide
If the data you want to restore exists in the destination, the
destination data will be overwritten by the backed up one if you
select Overwrite option; if you select Skip option, the
destination data will not be overwritten.
What to Select When Restoring
(SharePoint 2010 Screenshots Shown Below)
Platform Restore with Specified
Granularity
What to Restore
SharePoint Hive
Restore Level
Database
Farm Level
Level
√
SMSP 8.1 Platform Backup and Restore User’s Guide
Site
Collection
Level
Site Folder Item Item
Level Level Level Version
Level
√
153
Note
What to Select When Restoring
(SharePoint 2010 Screenshots Shown Below)
Platform Restore with Specified
Granularity
What to Restore
Restore Level
Database
Farm Level
Level
Site
Collection
Level
Site Folder Item Item
Level Level Level Version
Level
Note
If the data you want to restore does not exist in the destination,
the data will be restored to the destination regardless of
whether you choose the Overwrite or Skip option.
Global Assembly Cache
154
√
√
SMSP 8.1 Platform Backup and Restore User’s Guide
If the data you want to restore exists in the destination, the
destination data will be overwritten by the backed up one if you
select Overwrite option; if you select Skip option, the
destination data will not be overwritten.
What to Select When Restoring
(SharePoint 2010 Screenshots Shown Below)
Platform Restore with Specified
Granularity
What to Restore
Custom Features
Restore Level
Database
Farm Level
Level
√
SMSP 8.1 Platform Backup and Restore User’s Guide
Site
Collection
Level
Site Folder Item Item
Level Level Level Version
Level
√
155
Note
What to Select When Restoring
(SharePoint 2010 Screenshots Shown Below)
Platform Restore with Specified
Granularity
What to Restore
SharePoint SiteDefinitions
156
Restore Level
Database
Farm Level
Level
√
Site
Collection
Level
Site Folder Item Item
Level Level Level Version
Level
√
SMSP 8.1 Platform Backup and Restore User’s Guide
Note
What to Select When Restoring
(SharePoint 2010 Screenshots Shown Below)
Platform Restore with Specified
Granularity
What to Restore
Extra File System Folders
Restore Level
Database
Farm Level
Level
√
SMSP 8.1 Platform Backup and Restore User’s Guide
Site
Collection
Level
Site Folder Item Item
Level Level Level Version
Level
√
157
Note
What to Select When Restoring
(SharePoint 2010 Screenshots Shown Below)
Platform Customization Table Notes
Below are the detailed notes that are referenced in the Platform Customization Table.
Workflow Definition and Instance
To restore workflow content, you must select the related checkboxes first.
•
Workflow Definition ─ The user-created workflow definition in the site, list, or library.
SharePoint built-in workflows, workflows defined by SharePoint Designer, and
workflows defined by Nintex are supported. Workflows defined by Visio Studio are not
supported.
•
Workflow Instance ─ The item instance created upon the triggering of a workflow
definition. This includes the workflow state, workflow history, and workflow tasks.
*Note: The workflow instance of the SharePoint Designer workflow whose platform
type is SharePoint 2013 Workflow is not supported being restored.
The workflow instance of the checked-out file is not supported being restored.
In order to restore the workflow definition and workflow instance correctly, the following requirements
must be met:
•
The workflow definition must be restored to the destination farm before restoring the
workflow instance.
•
The workflow feature must be enabled before you restore the workflow definition and
workflow instance.
*Note: All workflow instances whose status was In Progress when backed up will be Cancelled when
restored to the destination.
Restoring Workflow Definitions
If there is an existing destination workflow definition that has the same name as one in the backup, then
the backed-up workflow definition is not restored. Otherwise, the backed-up workflow definition is
restored to the destination.
Restoring Workflow Instances
If the content that the workflow instance is based on is skipped during a restore, the workflow instance
will not be restored. If the related content is restored to the destination but there is an existing
destination workflow definition with the same name as one in the source, the backed-up workflow
instance will be restored to the destination.
If there is no workflow definition for this workflow instance, it is skipped and the corresponding
information is recorded in the logs.
158
SMSP 8 Platform Backup and Restore User’s Guide
Appendix D: SharePoint 2013 Social Features Supported
in Platform Backup and Restore
Refer to the table below for the supported and unsupported SharePoint 2013 social features for SMSP
Platform Backup and Restore.
Social Feature
Granular Level
Restore
Supported
Supported
Database Level
Restore
Supported
Supported
Supported
Not Supported
Supported
Supported
Post
Reply
Like
Picture
Link
@
Mentions
Tag
Not Supported
Not Supported
Not Supported
Not Supported
Not Supported
Not Supported
Not Supported
Not Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
People
Site
Document
Tag
Supported
Supported
Supported
Not Supported
Supported
Supported
Supported
Supported
Categories
Discussion
Board
Members
Budge
Reputation
Best Reply
Question
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
My Site
SkyDrive Pro (namely, OneDrive for
Business)
Blog
Tag
Microblog and Feed
Follow
Community Site
SMSP 8 Platform Backup and Restore User’s Guide
Comment
The Tags are stored in
Managed Metadata
Service as System Term.
It must be restored with
Managed Metadata
Service.
The tags must be
restored with Managed
Metadata Service.
The tags must be
restored with Managed
Metadata Service.
159
Social Feature
Community Portal
160
Community
Settings
Granular Level
Restore
Supported
Database Level
Restore
Supported
Supported
Supported
Comment
SMSP 8 Platform Backup and Restore User’s Guide
Appendix E: SharePoint Object Security and Property
Refer to the table below for detailed information on the security and property of each SharePoint object.
This table is applicable to both SharePoint 2010 and SharePoint 2013.
Type
SharePoint
Object
Security
Site Collection
Users and groups of the Site Collection
Site
Mappings of the users and their permissions, Permission Levels, Groups,
Users
List
Mappings of the users and their permissions, Users, Groups
Folder/Item/File
Mappings of the users and their permissions, Users, Groups
Property Site Collection
Attributes of the SharePoint Object which belongs to the specified Type
Basic information used to create the Site Collection, Other information of
the Site Collection, Site Features
Site
Basic information used to create the Site, Other information of the Site, Site
Columns, Site Content Types, Navigation, Site Features, Triggers for the
users’ actions in the Site
List
Basic information used to create the List, Other information of the List, List
Columns, List Content Types, Triggers for the users’ actions in the List, Alert
Folder/Item/File
Properties of the Folder/Item/File, Alert
SMSP 8 Platform Backup and Restore User’s Guide
161
Appendix F: Using Hot Key Mode in Platform Backup
and Restore
SnapManager for SharePoint supports Hot Key mode, which allows you to perform actions quickly by
using only the keyboard.
To access Hot Key mode, press Ctrl+Alt+ Z simultaneously on the keyboard while in the Platform Backup
and Restore interface.
The following is a list of hot keys for the Home page of the Platform Backup and Restore interface. To go
back to the Home page of the Platform Backup and Restore interface, press Ctrl+Alt+Z on the keyboard.
For example, continue pressing B to go back to the Backup tab of Platform Backup and Restore.
Operation Interface
Hot Key
Backup
B
Restore
R
Plan Manager
P
SnapManager for SharePoint Platform Page
1
NetApp Official website
2
Control Panel
3
Job Monitor
4
Plan Group
5
Health Analyzer
6
Logon Account
9
Help and About information
0
Backup Tab
The following is a list of hot keys for the Backup tab functions.
Plan Builder
162
P
Wizard
Mode
Functionality Name and Hot Key
W
Storage Policy
Back
Next
Finish
S
B
N
F
Finish
Finish and Run
Now
F
R
SMSP 8 Platform Backup and Restore User’s Guide
Form
Mode
Functionality Name and Hot Key
Cancel
F
Storage Policy
OK
Cancel
Storage
Policy
Verification
and Index
Policy
Custom
Database
Command
With
Operation
C
S
O
C
OK
OK and Run Now
O
R
S
A
C
CO
Create
MD
Migrate
Index
MI
Job Monitor
J
Verification and
Index Server
Verification and
Index Server
Group
OK
Cancel
S
OK
Cancel
OK
Cancel
G
Edit
E
Delete
Close
OK
Cancel
Create
D
C
O
C
N
Configure
C
E
OK
Cancel
Configure
O
B
C
OK
Cancel
O
B
Edit
Migrate
Database
N
Delete
Close
Back
Next
Start
Cancel
Back
Next
Start
Cancel
D
C
B
N
F
C
B
N
F
C
O
C
O
C
O
C
OK
Cancel
OK
Cancel
O
B
O
B
Restore Tab
The following is a list of hot keys for the Restore tab functions.
SMSP 8 Platform Backup and Restore User’s Guide
163
Restore
Farm Rebuild
R
FB
Farm Repair
FP
Generate Index
GI
Verification and Index
Policy
Command With
Operation
Job Monitor
Functionality Name and Hot Key
Disconnect
Restore
Verify
Connect
Back
Next
Finish
Cancel
Repair
Close
A
D
R
V
CO
B
N
F
C
FP
C
Verfication and Index
Policy
Back
Next
Finish
Cancel
A
B
N
F
C
ZO
J
Time-based Restore
Time-based Restore
164
T
Functionality Name and Hot Key
Create Container
T
Destination Physical
Device
Load Remote Backups
Advanced Search
DP
Find Site Collection
Verification and index
Policy
Installed Programs
Download Backup List
Q
ZC
Back
Next
Finish
Cancel
B
N
F
C
L
AS
I
DB
OK
Cancel
O
C
Search
Cancel
S
C
Close
OK
Cancel
X
O
C
SMSP 8 Platform Backup and Restore User’s Guide
Plan Manager Tab
The following is a list of hot keys for the Plan Manager tab functions.
View Details
Edit
V
E
Delete
Test Run
D
T
Run Now
R
Edit
Functionality Name and Hot Key
E Storage Policy
ZP
Plan Group
Close
Storage Policy
Verification and
Index Policy
Custom Database
Command With
Operation
Save
P
C
ZP
ZC
Save As
Cancel
A
C
OK
Cancel
O
C
Verification and
Index Policy
ZC
Custom Database
ZD
Command With
Operation
Save
ZO
Save As
Cancel
A
C
Save and Run Now
Save
SR
S
S
Save and Run Now
Save
SR
S
ZD
ZO
S
SMSP 8 Platform Backup and Restore User’s Guide
165
Copyright Information
Copyright © 1994–2014 NetApp, Inc. All rights reserved. Printed in the U.S.
No part of this document covered by copyright may be reproduced in any form or by any means—
graphic, electronic, or mechanical, including photocopying, recording, taping, or storage in an electronic
retrieval system—without prior written permission of the copyright owner.
Software derived from copyrighted NetApp material is subject to the following license and disclaimer:
THIS SOFTWARE IS PROVIDED BY NETAPP "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED
WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE, WHICH ARE HEREBY DISCLAIMED. IN NO EVENT SHALL NETAPP BE
LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
NetApp reserves the right to change any products described herein at any time, and without notice.
NetApp assumes no responsibility or liability arising from the use of products described herein, except
as expressly agreed to in writing by NetApp. The use or purchase of this product does not convey a
license under any patent rights, trademark rights, or any other intellectual property rights of NetApp.
The product described in this manual may be protected by one or more U.S. patents, foreign patents, or
pending applications.
RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the government is subject to restrictions
as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at
DFARS 252.277-7103 (October 1988) and FAR 52-227-19 (June 1987).
166
SMSP 8 Platform Backup and Restore User’s Guide
Trademark Information
NetApp, the NetApp logo, Network Appliance, the Network Appliance logo, Akorri, ApplianceWatch,
ASUP, AutoSupport, BalancePoint, BalancePoint Predictor, Bycast, Campaign Express, ComplianceClock,
Customer Fitness, Cryptainer, CryptoShred, CyberSnap, Data Center Fitness, Data ONTAP, DataFabric,
DataFort, Decru, Decru DataFort, DenseStak, Engenio, Engenio logo, E-Stack, ExpressPod, FAServer,
FastStak, FilerView, Fitness, Flash Accel, Flash Cache, Flash Pool, FlashRay, FlexCache, FlexClone,
FlexPod, FlexScale, FlexShare, FlexSuite, FlexVol, FPolicy, GetSuccessful, gFiler, Go further, faster,
Imagine Virtually Anything, Lifetime Key Management, LockVault, Manage ONTAP, Mars, MetroCluster,
MultiStore, NearStore, NetCache, NOW (NetApp on the Web), Onaro, OnCommand, ONTAPI, OpenKey,
PerformanceStak, RAID-DP, ReplicatorX, SANscreen, SANshare, SANtricity, SecureAdmin, SecureShare,
Select, Service Builder, Shadow Tape, Simplicity, Simulate ONTAP, SnapCopy, Snap Creator,
SnapDirector, SnapDrive, SnapFilter, SnapIntegrator, SnapLock, SnapManager, SnapMigrator,
SnapMirror, SnapMover, SnapProtect, SnapRestore, Snapshot, SnapSuite, SnapValidator, SnapVault,
StorageGRID, StoreVault, the StoreVault logo, SyncMirror, Tech OnTap, The evolution of storage, Topio,
VelocityStak, vFiler, VFM, Virtual File Manager, VPolicy, WAFL, Web Filer, and XBB are trademarks or
registered trademarks of NetApp, Inc. in the United States, other countries, or both.
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business
Machines Corporation in the United States, other countries, or both. A complete and current list of
other IBM trademarks is available on the web at www.ibm.com/legal/copytrade.shtml.
Apple is a registered trademark and QuickTime is a trademark of Apple, Inc. in the United States and/or
other countries. Microsoft is a registered trademark and Windows Media is a trademark of Microsoft
Corporation in the United States and/or other countries. RealAudio, RealNetworks, RealPlayer,
RealSystem, RealText, and RealVideo are registered trademarks and RealMedia, RealProxy, and
SureStream are trademarks of RealNetworks, Inc. in the Unites states and/or other countries.
All other brands or products are trademarks or registered trademarks of their respective holders and
should be treated as such.
NetApp, Inc. is a licensee of the CompactFlash and CF Logo trademarks. NetApp, Inc. NetCache is
certified RealSystem compatible.
SMSP 8 Platform Backup and Restore User’s Guide
167
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement