User manual | SMSP Platform Backup and Restore

SnapManager® 7.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-07522_A0
Feburary 2013
Table of Contents
Chapter 1:
Overview ............................................................................................................................... 4
Chapter 2:
Using Platform Backup and Restore ..................................................................................... 6
Before You Begin....................................................................................................................................... 8
Getting Started.......................................................................................................................................... 9
Notes for Customers Upgrading to SharePoint 2013 ............................................................................. 11
Configuring Devices and Setting up Storage Policies .............................................................................. 12
About the Staging Policy ......................................................................................................................... 13
Command with Operation ...................................................................................................................... 15
Migrator Tools......................................................................................................................................... 21
Selecting Content to Back Up ................................................................................................................. 24
SharePoint Components Supported for Backup ..................................................................................... 29
Using Plan Builder to Back Up Data ........................................................................................................ 31
Performing a Restore .............................................................................................................................. 42
Backup and Restore FAST Search Server for SharePoint 2010 Farms .................................................... 67
About Platform Backup and Restore for SQL Mirroring Database ......................................................... 72
Checking a Job Status .............................................................................................................................. 73
Chapter 3:
Performing Disaster Recovery............................................................................................. 74
Full Farm Recovery in Primary Site ......................................................................................................... 74
Full Farm Recovery in NetApp SnapMirror Destination ......................................................................... 78
Appendix A: Supported SharePoint Components ....................................................................................... 80
SharePoint 2010 Components Supported in Platform Backup and Restore .......................................... 80
SharePoint 2013 Components Supported in Platform Backup and Restore .......................................... 87
Platform Restore Support Table ............................................................................................................. 90
Appendix B: SharePoint Object Security and Property ............................................................................. 116
Appendix C: Using Hot Key Mode in Platform Backup and Restore ......................................................... 117
Backup Tab ............................................................................................................................................ 117
Restore Tab ........................................................................................................................................... 118
Plan Manager Tab ................................................................................................................................. 119
Copyright Information .............................................................................................................................. 121
2
SMSP 7.1 Platform Backup and Restore User’s Guide
Trademark Information............................................................................................................................. 122
SMSP 7.1 Platform Backup and Restore User’s Guide
3
Chapter 1: 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.
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:
4
•
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-fromanywhere 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 backup 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, CIFS devices) leveraging RBS
•
Archiving and 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
SMSP 7.1 Platform Backup and Restore User’s Guide
•
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 7.1 Platform Backup and Restore User’s Guide
5
Chapter 2: Using 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.
6
SMSP 7.1 Platform Backup and Restore User’s Guide
Figure 1: Platform Backup and Restore data flow diagram
SMSP 7.1 Platform Backup and Restore User’s Guide
7
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.
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.
8
SMSP 7.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 7.1 Platform Backup and Restore User’s Guide
9
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 farm(s). 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.
10
SMSP 7.1 Platform Backup and Restore User’s Guide
Notes for Customers Upgrading to SharePoint 2013
If you are running SMSP Platform Backup and Restore with SharePoint 2010 and plan on upgrading to
SharePoint 2013, take the following information into consideration when planning your upgrade:
•
Customers leveraging Platform Backup and Restore will need to install new 2013 SMSP Agents
and create new data protection plans for the upgraded 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 7.1 Platform Backup and Restore User’s Guide
11
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 device(s) 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 Data ONTAP device.
For instructions on defining devices and setting up storage policies, refer to the SnapManager for
SharePoint Control Panel User’s Guide.
12
SMSP 7.1 Platform Backup and Restore User’s Guide
About the Staging Policy
If you do not want to use the default verification server, you can set up a staging policy to specify a new
verification server used for verifying the backed up database and generating the granular level restore
index.
Configuring a Staging Policy
To configure a staging policy:
1. Click Staging Policy in the Settings group on the Backup or Restore tab. The Staging Policy
Configuration window appears.
Figure 4: Selecting Staging Policy
2. Click Create from the Manage group. The Staging Policy Configuration page appears. Configure
the following settings:
Figure 5: Selecting Staging Policy
a. Staging Policy Name – Enter a Name and optional Description for the staging policy.
b. Platform Type – Describe which platform is going to use this staging policy.
SMSP 7.1 Platform Backup and Restore User’s Guide
13
c. Server Name – Input a SQL Server to be used as the verification server in the Server
Name field. The format is Server or Server\Instance.
*Note: SnapManager for SQL Server must be installed on the verification server.
d. Database Access Credentials – Select the authentication method used to create the
database.
•
Windows authentication (recommended) (the default option) – Use this
method to confirm the user identity using Windows.
•
SQL authentication – SQL Server confirms the user identity according to the
entered account and password. The specified account must be added to the
sysadmin role in SQL Server.
•
Click Validation Test to verify the access to the SQL Server.
e. Allow all Farms to Use this Server – By default, all farms are allowed to use the
specified verification server in the created staging policy. To choose the farms where
you want to use this verification server, click the Farm drop-down list and select the
specified farm(s).
14
SMSP 7.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 specify 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 SMSQL 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 specifying 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 7.1 Platform Backup and Restore User’s Guide
15
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 6: 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. Specify 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 ─ Check 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.
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.
16
SMSP 7.1 Platform Backup and Restore User’s Guide
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 ─ Check 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 7.1 Platform Backup and Restore User’s Guide
17
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
18
Expands to the name of the SnapInfo subdirectory. This
argument is used in backup and verification operations.
SMSP 7.1 Platform Backup and Restore User’s Guide
Variable
Description
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
$ServerInstance
Specifies the name of the SQL Server instance that is
actually processed.
Example:
ACMESERVER1\SQLINSTANCE1
SMSP 7.1 Platform Backup and Restore User’s Guide
19
Variable
Description
$OperationStatus
Provides the status of the SMSQL operation.
Example:
5234
$PreCommandStatus
Provides the pre-command status to the post- command 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:
20
•
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 7.1 Platform Backup and Restore User’s Guide
Migrator Tools
SharePoint databases/indexes must be located on storage systems running Data ONTAP (LUNs) 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. You can also separate the database files and log files onto
separate LUNs by using SMSQL’s database migration.
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.
Migrating Database
Before you perform the database migration in SMSQL, make sure that the appropriate services are
stopped in the Services interface on each Web front-end server. After you have performed the database
migration in SMSQL, also make sure you start these same services in the Services interface on each Web
front-end server.
On any Web front-end server, navigate to Start > Administrative Tools > Services to find the Services
interface.
For detailed steps on performing a database migration in SMSQL, refer to SnapManager for Microsoft
SQL Server Installation and Administration Guide.
•
Migrate SharePoint content databases.
SharePoint 2010 Administration > SharePoint 2010 User Code Host >
SharePoint 2010 Tracing > SharePoint 2010 Timer > World Wide Web Publishing Service
•
Migrate databases of the Search Service Application.
SharePoint 2010 Administration > SharePoint 2010 User Code Host >
SharePoint 2010 Tracing > SharePoint 2010 Timer > SharePoint Server Search 14
•
Migrate databases of SharePoint Foundation Help Search.
SharePoint 2010 Administration > SharePoint 2010 User Code Host >
SharePoint 2010 Tracing > SharePoint 2010 Timer > SharePoint Foundation Search V4
SMSP 7.1 Platform Backup and Restore User’s Guide
21
•
Migrate databases of the Web Analytics Service Application.
SharePoint 2010 Administration > SharePoint 2010 User Code Host >
SharePoint 2010 Tracing > SharePoint 2010 Timer > Web Analytics Service
•
Migrate databases(Profile Database, Synchronization Database, and Social Tagging Database) of
the User Profile Service Application.
SharePoint 2010 Administration > SharePoint 2010 User Code Host >
SharePoint 2010 Tracing > SharePoint 2010 Timer > Forefront Identity Manager Service >
Forefront Identity Manager Synchronization Service
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 Migrate Tools group on the Backup tab. The Migrate Index page
appears.
Figure 7: 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.
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.
22
SMSP 7.1 Platform Backup and Restore User’s Guide
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.
*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 the following Microsoft article.
SMSP 7.1 Platform Backup and Restore User’s Guide
23
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 8: SharePoint 2010 tree and SharePoint 2013 tree
Figure 9: SharePoint 2010 tree and SharePoint 2013 tree
24
SMSP 7.1 Platform Backup and Restore User’s Guide
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,
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 with SnapMirror and
SnapVault enabled
In LUN with SnapMirror enabled
In LUN with SnapVault enabled
Database
Index
In LUN
Invalid, no database or index in
LUN
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
*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:
•
Farm
•
Windows SharePoint Solutions
•
Microsoft SharePoint Foundation Web Application and the Web Application nodes
below it
•
Shared Service Applications
SMSP 7.1 Platform Backup and Restore User’s Guide
25
•
Shared Service Proxies
•
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 application(s) under the Microsoft SharePoint Foundation Web
Application node (because Include New is selected)
•
Any existing or newly-added content database(s) of the selected/newly-created Web
application(s) under the Microsoft SharePoint Foundation Web Application node
•
The Finance Web and HR Web Web applications
Figure 10: Selecting SharePoint farm content
4. After selecting content, you are able to build a backup plan using Platform Backup and Restore.
26
SMSP 7.1 Platform Backup and Restore User’s Guide
Using the Customize Database Feature
Use the Customize Database feature to manually add to the SharePoint component tree any customized
databases that are not listed. Such databases include the database of a solution, the database of third
party software, databases of the Project Service Application, 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 customized database is added to the tree, it can be backed up normally.
1. On the Backup tab, in the Settings group, click Customize Database. The Customize Database
window appears.
Figure 11: Customize Database window
2. In the Customize Database window, click the Custom Database node on the right panel to
expand the tree. All customized 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.
SMSP 7.1 Platform Backup and Restore User’s Guide
27
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
Customize Database node.
Figure 12: Customize Database node
28
SMSP 7.1 Platform Backup and Restore User’s Guide
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.
•
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 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 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:
•
All SharePoint databases – The configuration database, Central Administration content
database, content databases, State Service database, Shared Service Application Database, and
search database are supported. These databases are backed up by the SQL Member Agent using
Platform Backup.
•
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
SMSP 7.1 Platform Backup and Restore User’s Guide
29
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.
•
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 following SharePoint 2013 objects are not supported to be backed up and restored by
SnapManager for SharePoint Platform Backup and Restore: SharePoint 2013 APP service and APP
catalog, Windows Azure workflows, and Office 2013 Web Apps Server.
*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.
30
SMSP 7.1 Platform Backup and Restore User’s Guide
Using Plan Builder to Back Up Data
Use the Plan Builder to schedule a backup.
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 13: Creating a plan in Wizard Mode
2. Click Next. The Storage Policy page appears.
SMSP 7.1 Platform Backup and Restore User’s Guide
31
3. Specify 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.
Figure 14: Selecting a Storage Policy
4. Click Next. The Advanced page appears.
Figure 15: Configuring the Advanced page
a. Associated Plan Group ─ Select the plan group(s) from the drop-down list to add the
plan to the corresponding group(s). 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.
b. To inform specified 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.
c. 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.
32
SMSP 7.1 Platform Backup and Restore User’s Guide
6. Define the Schedule type selection:
Figure 16: Configuring a schedule
•
No schedule – Select this option to run the plan immediately and save the plan 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.
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.
SMSP 7.1 Platform Backup and Restore User’s Guide
33
c. Granularity index server ─ Specify the verification server used for generating the
granular level restore index. By default, the default verification server 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 Staging 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-driveletter
limitation. By using volume mount points, you can mount a target partition onto a folder
on another physical disk.
e. BLOB Settings ─ Select which option(s) 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.
f.
Storage Policy Settings ─ Select which option(s) 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.
g. 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.
•
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 Staging 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 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.
34
•
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 command(s) 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.
•
BLOB Settings ─ Select which option(s) 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.
•
Database Settings ─ Configure the SnapMirror-/SnapVault-related settings for
the backed-up databases.
SMSP 7.1 Platform Backup and Restore User’s Guide
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 information on configuring the SnapVault
datasets, refer to the SnapManager for Microsoft SQL Server Installation
and Administration Guide.
•

Verify archive backup on secondary storage ─ Use this option to
verify the database archived on the secondary storage system.

Archive backup to secondary storage ─ Specify whether you want
to retain backups at the archived location on an Hourly, Daily,
Weekly, Monthly, or Unlimited basis.
Storage Policy Settings ─ Select which option(s) 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.
h. 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.
SMSP 7.1 Platform Backup and Restore User’s Guide
35
i.
Maintenance Notification – To inform specified 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.
10. When finished, click Next. The Overview screen appears.
11. 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.
12. Check 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.
13. 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.
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 17: 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
36
SMSP 7.1 Platform Backup and Restore User’s Guide
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 specified 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.
a. 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.
b. Granularity index server ─ Specify the verification server used for generating the
granular level restore index. By default, the default verification server 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 Staging Policy.
c. 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.
a. 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.
•
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 Staging 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 database verification. For example:
C:\mountpoint.
b. 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 is not restored.
c. Transaction Log Backup ─ 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.
SMSP 7.1 Platform Backup and Restore User’s Guide
37
d. Backup BLOB for Selected Scope ─ This option backs up BLOB content generated by
Storage Manager and files in the connected path of Connector. Check the corresponding
checkbox(es) if you wish to back up this BLOB data.
4. Advanced tab ─ Configure the advanced settings for the scheduled backup job.
Figure 18: Configuring advanced backup settings (1)
Figure 19: Configuring advanced backup settings (2)
38
SMSP 7.1 Platform Backup and Restore User’s Guide
5. BLOB Settings ─ Select which option(s) 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.
6. 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.
•
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.
•
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 version 7 or 7 mode in 8.x version of Data
ONTAP; ensure that you set up the Protection Manager Datasets via SMSQL.
*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.
•
Archive backup to secondary storage ─ Specify whether you want to retain
backups at the archived location on an Hourly, Daily, Weekly, Monthly, or
Unlimited basis.
•
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 command(s) 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.
7. Storage Policy Settings ─ Select which option(s) 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.
SMSP 7.1 Platform Backup and Restore User’s Guide
39
8. Time tab ─ Specify the detailed schedules for the scheduled backup job.
Figure 20: Configuring schedule backup settings
a. Type – Select the interval at which the backup occurs.
b. Schedule Settings – Set up the frequency for the scheduled backup job. If you select the
type as Hourly, Weekly, or Monthly, set up the advanced settings for the frequency. For
more scheduling options, click the Advanced checkbox to reveal additional options.
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 specified 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.
40
SMSP 7.1 Platform Backup and Restore 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.
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.
SMSP 7.1 Platform Backup and Restore User’s Guide
41
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: For information regarding the SharePoint components supported in Platform Backup and
Restore, refer to Appendix A: 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, or SharePoint 2013
Components Supported in Platform Backup and Restore.
*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.
42
SMSP 7.1 Platform Backup and Restore User’s Guide
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 21: 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. Plan Filter – Filter the backup data by plan information using the drop-down list.
•
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.
•
Plan Name – Select the plan that you want to display from the drop-down list.
Select All Plans to display all plans.
•
Restore Granularity Level – Select the restore granularity level from the dropdown list; only the backup jobs that support the selected restore granularity
level(s) are displayed. Select All Types to list backup jobs for all levels.
b. Time Range – Filter backup data by completion time range using the drop-down list.
SMSP 7.1 Platform Backup and Restore User’s Guide
43
•
All Jobs – Select this option to display all Finished/Finished with Exception
Platform backup jobs.
•
Backup jobs start within … – Select this option to specify a time period. All of
the Finished/Finished with Exception Platform backup jobs whose start time is in
the specified time period are displayed.
3. After selecting the filter(s), 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:
a. Place the mouse cursor over a backup job to display job information such as the Plan
Name, Job ID, Restore Granularity Level, Backup Method, Create Persistent Snapshot,
Index Status, Copy Data, Job Status and Data Import. Click Day, Week, or Month to
change the view to see all the available jobs during that time period.
b. Click the page turning button
page.
on the top-left corner of the calendar to turn the
5. 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:
44
•
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
•
Options for Restoring Backed-up Web Front-end Files
•
Restoring Backed-up BLOB Data
SMSP 7.1 Platform Backup and Restore User’s Guide
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 22: Building a restore plan
2. Data Selection – Select the content you want to restore using the tree. The content in the tree
will vary depending upon the type of backup selected. In this case, select a content database to
restore.
3. Restore Type – Choose how the content will be restored.
a. Restore Type ─ Select one restore type from the two types below.
•
Normal restore ─ Use this option to restore the database(s) normally by
configuring the corresponding configurations. In this case, select this option.
•
Restore from Alternate Storage Location ─ Use this option to restore the
database(s) from the alternate storage location by manually restoring the
database(s) in SMSQL. For more information, refer to Restoring from an
Alternate Storage Location.
b. Agent Group – Select the Agent group that will perform the restore job. Click View to
view the details of the specified Agent group.
4. Restore Settings – Choose detailed settings for the restore job.
SMSP 7.1 Platform Backup and Restore User’s Guide
45
Figure 23: 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.
46
SMSP 7.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. Restore Option – Specify 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.
•
Not Overwrite – 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.
•
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.
•
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.
o
Verification server ─ Specify the verification 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 Staging
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 dropdown list. Select a command profile from the drop-down list. The command(s) 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.
5. When finished configuring Restore Settings, click Next. The Schedule page appears.
6. Schedule – Choose whether or not to run the restore job based on a schedule.
a. Select Restore once finish the wizard to run the job immediately after finishing the
restore wizard.
b. 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.
7. When finished, click Next. The Overview page appears.
8. 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.
SMSP 7.1 Platform Backup and Restore User’s Guide
47
9. 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.
Building an In Place Platform Granular Restore Plan
1. Follow the instructions given in Performing a Restore to begin building the plan.
Figure 24: Selecting a backup plan’s data
2. Data Selection – Select the database that includes the granular content you wish to restore.
3. Click the View Details link on the top-right corner of the Backup Data pane to view detailed
information about the selected database.
4. Click the Global Setting for Restoring Content, Property and Security link and configure the
Item Level Settings:
48
SMSP 7.1 Platform Backup and Restore User’s Guide
Figure 25: The Global Setting for Restoring Content, Property and Security link
a. Restore Granular Content – Select this option to restore granular content. If you do not
select this option, the tree in the Backup Data pane can only be expanded down to the
site collection level; the granular content cannot be selected. Refer to Deselecting the
Restore Granular Content Feature for detailed information.
•
Container Selection ─ This is a global setting for restoring the security/property
of the containers. If you have configured the settings to be used when restoring
the security/property of the containers here, the Security/Property checkboxes
next to the containers on the backup data tree will be disabled. For more
information, refer to Appendix A: 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 and
SharePoint 2013 Components Supported in Platform Backup and Restore.
•
Content Selection ─ This is a global setting for restoring the security of the
content. If you have configured the setting to be used when restoring the
security of the content here, the Security checkbox next to the content in the
SMSP 7.1 Platform Backup and Restore User’s Guide
49
Item Browser pop-up window will be disabled. For more information, refer to
Appendix A: 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 and
SharePoint 2013 Components Supported in Platform Backup and Restore.
•
Browse the stored index – Select this option to browse the index that was
generated according to the restore granularity specified when setting up the
backup job or maintenance job.
b. 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 specify another verification server, select a pre-defined staging policy from the
Specify a staging policy for loading tree drop-down list, or click the New Staging Policy
link in the drop-down list to create a new verification server. For more information,
refer to About the Staging Policy.
*Note: If a granular restore index is generated for the specified Platform backup job,
Browse the stored index will be selected by default; if the granular restore index is not
generated for the specified Platform backup job, the Browse the index from backup
data option must be used when restoring backup data using Platform granular restore.
5. 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 A: Supported SharePoint Components
b. Refer to the sections below for information on what components in SharePoint 2010
and SharePoint 2013 are supported in SnapManager for SharePoint.
c. SharePoint 2010 Components Supported in Platform Backup and Restore and
SharePoint 2013 Components Supported in Platform Backup and Restore.
d. Property – Refer to Appendix A: Supported SharePoint Components
e. Refer to the sections below for information on what components in SharePoint 2010
and SharePoint 2013 are supported in SnapManager for SharePoint.
f.
SharePoint 2010 Components Supported in Platform Backup and Restore and
SharePoint 2013 Components Supported in Platform Backup and Restore.
6. When finished, click Next. The Restore Type page appears.
7. Restore Type – Choose how the content will be restored.
50
SMSP 7.1 Platform Backup and Restore User’s Guide
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 26: 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 database(s) 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 specified Agent group.
SMSP 7.1 Platform Backup and Restore User’s Guide
51
8. Click Next when finished. The Restore Settings page appears.
Figure 27: Configuring restore settings
9. Restore Settings – Configure how the content will be restored.
a. Conflict Resolution – Specify the action to dictate how to resolve the container level
and content level conflicts that arise during a Platform granular restore.
•
Container Level Conflict Resolution – Set the conflict resolution on the site
collection, site, list, and folder levels.
o
Skip – Ignores the source container that conflicts with the destination
one.
o
Merge – Combines the configuration of the source and destination
containers. If there is a conflict, the source configuration overwrites the
destination’s configuration.
o
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
52
SMSP 7.1 Platform Backup and Restore User’s Guide
container is no longer needed before performing the restore using this
conflict resolution.
•
Content Level Conflict Resolution – Set the conflict resolution on the item level.
o
Skip – Ignores the source item/document that has the same item
ID/document name as the destination item/document.
o
Overwrite – Copies the source item/document to the destination by
overwriting the destination item/document with same item
ID/document name.
o
Overwrite by Last Modified Time – Keeps the conflict item/document
which has the latest modified time and overwrites the older one.
o
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.
o
Append a New Version – Adds the conflict source item/document to
the destination as a new version of the conflict destination
item/document.
b. Include Recycle Bin Data – Choose whether to compare the data in the backup with the
data in the original SharePoint farm’s recycle bin. The Include Recycle Bin Data field will
only be displayed when you have selected Skip either at the Container level or Content
level. If you select Yes in this field and the selected content in the backup still exists in
the recycle bin of the original SharePoint farm, the selected content in the backup is not
restored.
c. 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.
d. Workflow – Decide how the backed-up workflows are restored.
•
Include workflow definition – Only restores the definition of the backed-up
workflows.
•
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.
e. 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.
f.
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
specified. 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.
SMSP 7.1 Platform Backup and Restore User’s Guide
53
g. 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.
10. When finished configuring Restore Settings, click Next. The Schedule page appears.
11. 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.
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.
54
SMSP 7.1 Platform Backup and Restore User’s Guide
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
Details link on the top right corner of the Backup Data pane to view the detailed backup data
for the selected database.
3. Click the Global Setting for Restoring Content, Property and Security link and configure the
Item Level Settings:
a. Restore Granular Content – Select this option to restore granular content. If you do not
select this option, the tree in the Backup Data pane can only be expanded down to the
site collection level and you cannot select granular content. Refer to Deselecting the
Restore Granular Content Feature for detailed information.
•
Container Selection ─ This is a global setting for restoring the security/property
of the containers. If you have configured the settings to be used when restoring
the security/property of the containers here, the Security/Property checkboxes
next to the containers on the backup data tree will be disabled. For more
information, refer to Appendix A: 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 and
SharePoint 2013 Components Supported in Platform Backup and Restore.
•
Content Selection ─ This is a global setting for restoring the security of the
content. If you have configured the setting to be used when restoring the
security of the content here, the Security checkbox next to the content in the
Item Browser pop-up window will be disabled. For more information, refer to
Appendix A: 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 and
SharePoint 2013 Components Supported in Platform Backup and Restore.
•
Browse the stored index – Browse from the index that was generated according
to the specified restore granularity when backing up this database or
performing the maintenance job.
b. Browse the index from backup data – When this option is selected, a SharePoint
content database backup snapshot is mounted as a temporary database first. 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.
SMSP 7.1 Platform Backup and Restore User’s Guide
55
By default, the mounted temporary database is stored on the default verification server.
To specify another verification server, select a pre-defined staging policy from the
Specify a staging policy for loading tree drop-down list, or click the New Staging Policy
link in the drop-down list to create a new verification server. For more information,
refer to About the Staging Policy.
*Note: If a granular restore index is generated for the specified Platform backup job,
Browse the stored index will be selected by default; if the granular restore index is not
generated for the specified Platform backup job, the Browse the index from backup
data option must be used when restoring the backup using Platform granular restore.
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 A: Supported SharePoint Components
b. Refer to the sections below for information on what components in SharePoint 2010
and SharePoint 2013 are supported in SnapManager for SharePoint.
c. SharePoint 2010 Components Supported in Platform Backup and Restore and
SharePoint 2013 Components Supported in Platform Backup and Restore.
d. Property – Refer to Appendix A: Supported SharePoint Components
e. Refer to the sections below for information on what components in SharePoint 2010
and SharePoint 2013 are supported in SnapManager for SharePoint.
f.
SharePoint 2010 Components Supported in Platform Backup and Restore and
SharePoint 2013 Components Supported in Platform Backup and Restore..
5. When finished, click Next. The Restore Type page appears.
6. 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.
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.
56
SMSP 7.1 Platform Backup and Restore User’s Guide
Figure 28: 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 database(s) 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.
i.
Select a node with a blank textbox.
ii.
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.
iii.
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.
d. Agent Group – Select the Agent group that will perform the restore job. Click View to
view the details of the specified Agent group.
e. Mapping Settings (Optional) – Configure whether to specify the mapping settings to
map the user, domain, displayed list or column label to the destination.
•
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.
SMSP 7.1 Platform Backup and Restore User’s Guide
57
•
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.
•
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.
7. Click Next when finished. The Restore Settings page appears.
8. 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.
•
Container Level Conflict Resolution – Set the conflict resolution on the site
collection, site, list, and folder levels.
o
Skip – Ignores the source container that conflicts with the destination
one.
o
Merge – Combines the configuration of the source and destination
containers. If there is a conflict, the source configuration overwrites the
destination’s configuration.
o
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.
•
58
Content Level Conflict Resolution – Set the conflict resolution on the item level.
o
Skip – Ignores the source item/document that has the same item
ID/document name as the destination item/document.
o
Overwrite – Copies the source item/document to the destination by
overwriting the destination item/document with same item
ID/document name.
o
Overwrite by Last Modified Time – Keeps the conflict item/document
that has the latest modified time and overwrites the older one.
o
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.
SMSP 7.1 Platform Backup and Restore User’s Guide
o
Append a New Version – Adds the conflict source item/document to
the destination as a new version of the conflict destination
item/document.
b. Include Recycle Bin Data – Choose whether to compare the data in the backup with the
data in the destination SharePoint farm’s recycle bin. The Include Recycle Bin Data field
will only be displayed when you have selected Skip either at the Container level or
Content level. If you select Yes in this field and the selected content in the backup still
exists in the recycle bin of the destination SharePoint farm, the selected content in the
backup is not restored.
c. 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.
d. Workflow – Decide how the backed-up workflows are restored.
•
Include workflow definition – Only restores the definition of the backed-up
workflows.
•
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.
e. 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.
f.
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
specified. 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.
g. 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.
9. When finished configuring Restore Settings, click Next. The Schedule page appears.
10. 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. 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.
11. When finished, click Next. The Overview page appears.
12. 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.
SMSP 7.1 Platform Backup and Restore User’s Guide
59
13. 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.
60
SMSP 7.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 29: 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 7.1 Platform Backup and Restore User’s Guide
61
1. If you’ve selected Restore from Alternate Storage Location, SnapManager for SharePoint begins
preparing for the restore after you’ve configured the notification profile and clicked Next.
During this preparation process, the selected database(s) 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 specified content database.
Figure 30: Related Component
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’ve selected Restore from Alternate Storage Location, the content database where the
selected item(s) reside will be displayed in the Related Component page after you’ve configured
the restore settings and clicked Next. Perform a clone restore to the content database where
the selected item(s) reside.
62
SMSP 7.1 Platform Backup and Restore User’s Guide
Figure 31: Related Component
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.
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 checkbox(es), and click OK. A .zip file that contains detailed list(s) 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.
SMSP 7.1 Platform Backup and Restore User’s Guide
63
•
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.
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 link on the top-right
corner of the Backup Data pane 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.
Figure 32: Restoring backed-up Connector and Storage Manager data
64
SMSP 7.1 Platform Backup and Restore User’s Guide
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 uncheck 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 do not select Restore Granular Content, the tree in the Backup Data pane can only be
expanded down to the site collection level. This means that granular content cannot be selected.
For an in place/out of place Platform granular restore performed at the site collection level, deselecting
the Restore Granular Content feature can be executed only when the following conditions are met:
•
Required for out of place Platform granular restore ─ Only one site collection is selected on the
backup data tree when selecting the scope of the restore job.
•
Required only for in place Platform granular restore ─ No site collection in the original location
has the same URL or ID as the site collection selected in the backup data.
•
Required only for out of place Platform granular restore ─ No site collection in the destination
has the same URL or ID as the site collection selected in the backup data.
SMSP 7.1 Platform Backup and Restore User’s Guide
65
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 hive folder, they can be
restored as well. Both IIS site files and 14 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.
66
SMSP 7.1 Platform Backup and Restore User’s Guide
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. Check 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.
SMSP 7.1 Platform Backup and Restore User’s Guide
67
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 33: 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 many contents. This indicates
that when performing the backup, the FAST Search Admin Database node(s) and FAST Search Server
node(s) are included; the FAST Content SSA node(s) are excluded.
68
SMSP 7.1 Platform Backup and Restore User’s Guide
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, click 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 34: Restoring the FAST Search Server
4. Only In Place restore type and Overwrite/Not Overwrite restore options are supported.
5. In the Advanced field:
SMSP 7.1 Platform Backup and Restore User’s Guide
69
Figure 35: 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 checking the Configure FAST Certificate checkbox:
•
If you select the Use the certificate from backup option, enter the correct
certificate password to restore the certificate.
•
If you select the Generate new FAST certificate(self-signed) option, enter a
valid certificate password to create a new certificate.
*Note: If you check 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 upgraded 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
FAST Search
70
Location
On SharePoint server
On Stand-alone FAST server
On FAST admin server
On FAST non-admin server
On Stand-alone FAST server
Support Status
Supported
Supported
Supported
Supported
Supported
Supported
SMSP 7.1 Platform Backup and Restore User’s Guide
Component
Index(data_fixml)
FAST Search Connector
Location
On FAST primary non-admin server
On FAST secondary non-admin server
Content Source
Crawl rule
FAST Search Connector
proxy (NO proxy when
created)
FAST Search Query
FAST Search Query proxy
SMSP 7.1 Platform Backup and Restore User’s Guide
Support Status
Supported
Supported
Supported
Supported
Supported
Unsupported
Supported
Supported
71
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.
72
SMSP 7.1 Platform Backup and Restore User’s Guide
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.
Refer to the SnapManager for SharePoint Job Monitor User’s Guide for more information.
SMSP 7.1 Platform Backup and Restore User’s Guide
73
Chapter 3: Performing Disaster Recovery
The following sections contain information on two types of disaster recovery: full farm recovery in a
primary site, and full farm recovery in a secondary site (NetApp SnapMirror Destination).
Full Farm Recovery in Primary Site
After you have backed up the entire farm using Platform Backup, you can use the Farm Rebuild function
to perform a rebuilding of your farm should the need arise.
*Note: Backed-up Web-Front-End Servers nodes are not restored during the farm rebuild. If necessary,
restore the desired Web-Front-End Servers nodes after the farm rebuild.
Prerequisites
To perform the farm rebuild, the following requirements must be met:
74
•
A SnapManager for SharePoint backup of the data for the entire farm (including the SharePoint
configuration database and the Central Administration database) must be available.
•
The SharePoint farm server topology should be identical to the topology at the time of backup.
The system architecture must also match the platform at the time of backup. For example, an
x64-bit architecture should be used if x64 architecture was used at the time of the backup.
•
All related software installed on the rebuilt destination should be the identical version and the
patch level as before. Examples of related software are: SharePoint, SQL Server, SnapManager
for Microsoft SQL Server, SnapManager for SharePoint, as well as the .NET Framework.
•
User permissions on both the local server and SQL Server should be set to the same as before.
•
Configure the same LUN storage layout as before.
SMSP 7.1 Platform Backup and Restore User’s Guide
Rebuilding the Farm
Detailed full farm rebuild steps are as follows:
1. Select the Restore tab and click Farm Rebuild in the Manage group.
2. From the Farm Rebuild tab, configure the options in the Filter By area, which limits the scope of
backup data to be restored by filtering out specified Full farm backup jobs.
Figure 36: Performing a farm rebuild
a. Plan Filter – Filter the full farm backup data by plan information using this drop-down
list.
•
Farm – Select a farm from the drop-down list to display the plans for that
particular farm. Select All Farms to display all plans for all farms.
•
Plan Name – Select the plan that you want to display from the drop-down list.
Select All Plans to display the jobs of all the plans.
•
Restore granularity level – Select the restore granularity level from the dropdown list; only backup jobs of the specified restore granularity level(s) are
displayed. Select All Types to list the backup jobs of all levels.
b. Time Range – Filter the Full farm backup data by completion time range using this dropdown list.
•
All Jobs – Select this option to display all Finished/Finished with Exception
Platform backup jobs.
•
Backup jobs start within … – Select this option to specify a time period. All of
the Finished/Finished with Exception Platform backup jobs whose start time is
in the specified time period are displayed.
SMSP 7.1 Platform Backup and Restore User’s Guide
75
3. After configuring the three filters above, click the Filter button in the Filter By area or on the
ribbon to filter the backup jobs. All of the Full farm backup jobs that meet all of the filter rules
are listed in the calendar. You can click Clear All Filters in the Filter By area or click Clear on the
ribbon to clear all the filters and display all the Finished/Finished with Exception Platform
backup jobs.
4. Place the mouse cursor over the Full farm backup job to display job information such as the Plan
Name, Job ID, Backup Option, Restore Granularity Level, Backup Method, Create Persistent
Snapshot, Index Status, Copy Data, Job Status and Data Import. Click on Day, Week, or Month to
change the view to see all the available full farm backup jobs during that time period. Click the
page turning button
at the top-left corner to turn the page.
5. Select the Full farm backup job that you want to restore.
6. View ─ View all of the backed-up SharePoint components in the Full farm backup job.
7. Restore Type ─ Choose how the content will be restored.
•
Normal restore ─ Use this option to restore the database(s) normally by configuring the
corresponding configurations.
•
Restore from Alternate Storage Location ─ Use this option to restore the database(s)
from an alternate storage location (SnapVault) by manually restoring the database(s) in
SMSQL. For more information, refer to Restoring from an Alternate Storage Location.
8. 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.
9. Disconnect Connection ─ Disconnect all of the SharePoint servers in this farm. All SharePoint
servers that are connected to the current farm will be displayed here. Hovering the mouse over
one column displays a . Click to hide this column from the current view. You can also select
which column to be displayed in the current view by clicking , checking the checkbox(es) of the
column(s) you want to be displayed in the current view, and clicking OK.
10. Click Disconnect to disconnect all of the displayed SharePoint servers from this farm. If all the
displayed SharePoint servers have already been disconnected from this farm, go to the next step
directly.
11. Restore Database ─ Restore all of the backed up databases in the Full farm backup job. The
databases are all restored with no attempt to connect them to the SharePoint environment
according to the selected restore option.
12. Restore Setting ─ Specify whether or not to overwrite the original contents if there is a conflict
between the original database name and that of the backed-up database.
76
•
Not Overwrite – 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.
•
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.
SMSP 7.1 Platform Backup and Restore User’s Guide
Figure 37: Performing a farm rebuild
13. Click Restore to begin the restore process. After the restore of the databases is finished, the
restore status will be updated in the Status column and the checkboxes before all the databases
will become clickable. If the restore of an individual database fails, only select this database,
specify the restore setting, and perform the restore job again.
14. SharePoint Configuration ─ Configure the settings required for reconfiguring the restored
SharePoint farm. You must enter the passphrase for this farm before reconnecting all of the
servers. Select the Specify Port Number checkbox, and you are able to change the port used by
the SharePoint 2010 Central Administration. For now, only NTLM is supported as the security
authentication type.
*Note: If you plan to restore the backed up IIS settings of the SharePoint 2010 Central
Administration after the farm rebuild, make sure you use the original port number for the
SharePoint 2010 Central Administration in this step. Thus the SharePoint 2010 Central
Administration can be accessed normally after restoring the backed up IIS settings.
15. Click Validation Test to verify the settings you have input.
16. Connect ─ Connect all of the SharePoint servers back to this farm. All SharePoint servers that
have been disconnected from the current farm earlier in this procedure will be displayed here.
Hovering the mouse over one column displays a . Click to hide this column from the current
view. You can also select which column to be displayed in the current view by clicking ,
checking the checkbox(es) of the column(s) you want to be displayed in the current view, and
clicking OK.
17. Click Connect to connect all of the displayed SharePoint servers back to this farm.
18. Overview ─ View the current farm settings you have configured.
19. Click Finish to finish the farm rebuild.
SMSP 7.1 Platform Backup and Restore User’s Guide
77
Full Farm Recovery in NetApp SnapMirror
Destination
This section describes how to perform a disaster recovery (DR) using SnapMirror backup data
(SnapMirror license required on both source and destination NetApp storage systems) from the
perspective of SharePoint and SnapManager for SharePoint. It does not cover how to recover Active
Directory (AD) or any other components not covered by SnapManager for SharePoint.
Prerequisites
Prior to performing this restore, the following requirements must be met:
•
SnapManager for SharePoint backups of the SnapManager for SharePoint Control Database,
SharePoint databases, indexes, Connector BLOB data, and Storage Manager BLOB data must be
available. Typically these are automatically replicated through SnapMirror.
*Note: To ensure that Storage Manager and Connector can be used after disaster recovery, you
must add their stub databases as customized databases and include those stub databases in the
full farm backup. In addition, you must use the same SnapManager for SharePoint Control
Database when re-installing the new SnapManager for SharePoint Manager; also, make sure all
BLOB data is ready at the DR side and the storage system profiles/physical devices/logical
devices are configured using the correct configurations/paths before performing the disaster
recovery.
•
The registry backup of SnapManager for SQL Server must be available, which is
HKEY_LOCAL_MACHINE > SOFTWARE > Network Appliance > SnapManager for SQL Server.
•
At the DR site, SharePoint farm server topology should be identical to the production site, which
includes both the SharePoint farm topology and SnapManager for SharePoint topology. The
system architecture must also match the platform at the time of backup. For example, an x64bit architecture should be used if x64 architecture was used at the time of the backup.
•
All related software installed on the DR side should be the identical version and the patch level
as before. Examples of related software are: SharePoint, SQL Server, SnapManager for Microsoft
SQL Server, SnapManager for SharePoint, as well as the .NET Framework.
•
The hostname of the source and the destination should be the same.
For example, if you use IP in the configuration and use IP to configure SharePoint or
SnapManager for SharePoint Media service, the IP should be the same. For SQL, except port, the
instance name and alias of the source and the destination should be the same. If you install
SnapManager for SharePoint in other places, you should use identical hostname or IP for
SnapManager for SharePoint Manager. The port can be different.
There are several ways to achieve this. For example, a separate AD domain for the DR site can
be used to keep the same server topology, or if the DR site does not need to coexist with the
78
SMSP 7.1 Platform Backup and Restore User’s Guide
production site, disk imaging or virtualization technology can be used to ensure the same
topology is used.
•
User permissions on both the local server and SQL Server should be set to the same as before.
•
If a separate AD domain is used at DR site, that domain should have a trusted relationship with
the primary site’s AD so that users can still access SharePoint content. This can also be run if the
DR site is in the same AD domain as the original location.
Full Farm Rebuild in Secondary Location
After all servers are rebuilt and the preceding prerequisites are met, complete the following steps for
disaster recovery:
1. Install all required software components, including SnapDrive, SQL Server, and SnapManager for
Microsoft SQL Server. For more information about these installations, refer to SnapDrive for
Windows Installation and Administration Guide and SnapManager for Microsoft SQL Server
Installation and Administration Guide. Only connect SQL Server using SnapManager for
Microsoft SQL Server after you have already imported the registry backup of SnapManager for
Microsoft SQL Server.
2. Install SharePoint. If you are only restoring farm components such Web applications, you can
create a new farm in the destination that has the same name and farm topology as the source
farm. Otherwise, SharePoint can be left un-configured when performing an entire farm restore.
3. Install SnapManager for SharePoint Manager according to the steps listed in the SnapManager
for SharePoint Installation Guide.
4. Connect the SnapMirror LUN containing the backup job data, or manually copy this data to a
location that the DR site logical device can access.
5. Install SnapManager for SharePoint Agents according to the steps listed in the SnapManager for
SharePoint Installation Guide.
6. Perform the full farm restore as described in Restoring from an Alternate Storage Location.
SMSP 7.1 Platform Backup and Restore User’s Guide
79
Appendix A: 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
80
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
Supported
√
Unsupported
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
SMSP 7.1 Platform Backup and Restore User’s Guide
Filters
Forms
Media and Content
Outlook Web App
Search
Social Collaboration
Web Part
XML Viewer
Apply Filters Button
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
SMSP 7.1 Platform Backup and Restore User’s Guide
Supported
√
Unsupported
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
√
81
Web Part
Tag Cloud
User Tasks
82
Supported
√
√
Unsupported
SMSP 7.1 Platform Backup and Restore User’s Guide
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
Database(s) 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
√
SMSP 7.1 Platform Backup and Restore User’s Guide
83
State Service
StateService_Database(State Service Database Settings)
√
User Profile Service
Application
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
×
PowerPoint Service
Application
N/A
×
Project Service
Application
N/A
×
SQL Server PowerPivot
Service Application
N/A
×
84
√
SMSP 7.1 Platform Backup and Restore User’s Guide
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
√
InfoPath Forms Services Settings
and InfoPath Forms Services
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
√
SMSP Platform Backup and
Restore backs up FAST
SMSP 7.1 Platform Backup and Restore User’s Guide
Notes
Farm-level search settings and
Crawler impact rules are
supported.
85
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
SharePoint
Knowledge Lake Imaging
√
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.
Front-end Web Server
√
•
IIS Settings (such as Form
Authentication, SSL
certification and so on) can
be configured individually on
the front-end Web 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 frontend Web 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
86
SMSP 7.1 Platform Backup and Restore User’s Guide
the front-end Web 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
Database(s) of the Service Application
Access Services
Access Services 2010
App Management
Service
Business Data
Connectivity Service
Excel Services
Application
Lotus Notes Connector
Machine Translation
Service
Managed Metadata
Service
This Service Application does not have a database
This Service Application does not have a database
AppMng_Service_DB (App Management Database)
PerformancePoint
Service Application
PowerPoint Conversion
Service Application
Project Service
Application
Search Service
Application
Secure Store Service
Security Token Service
Application
Bdc_Service_DB(Business Data Connectivity Database)
Supported in Inplace Restore
√
√
√
√
This Service Application does not have a database
√
N/A
×
Machine Translation_Database
√
Managed Metadata Service_Database(Service
Application Database)
PerformancePoint Service
Application_Database(Microsoft.PerformancePoint.Scor
ecards.BIMonitoringServiceDatabase)
√
√
This Service Application does not have a database
√
Project Database
√
Search_Service_Application_DB(Administration
Database)
Search_Service_Application_CrawlStoreDB(Crawl
Database)
Search_Service_Application_PropertyStoreDB(Property
Database)
Secure_Store_Service_DB(Secure Store Service
Database)
This Service Application does not have a database
SMSP 7.1 Platform Backup and Restore User’s Guide
√
√
√
87
Service Application
Database(s) of the Service Application
Session State Service
State Service
Subscription Settings
Service Application
Usage and Health data
collection
SessionStateService_Database
StateService_Database(State Service Database Settings)
User Profile Service
Application
Visio Graphics Service
Word Automation
Services(Word
Conversion Service)
Workflow Service
Application
Work Management
Service
88
Subscription Settings Database
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
Supported in Inplace Restore
√
√
√
√
√
√
WordAutomationServices_Database(Microsoft.Office.W
ord.Server.Service.QueueDatabase)
√
N/A
x
This Service Application does not have a database
√
SMSP 7.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
Configuration Database
Windows SharePoint
Solutions
InfoPath Form Services
Global Site Template
Custom DB
Web-Front-End Server
Item Level Restore
FBA Databases
Blob
Supported in In-place
Notes
Restore
√
√( Restore Database
Only must be used)
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.
√
SMSP 7.1 Platform Backup and Restore User’s Guide
89
Platform Restore Support Table
*Note: Before you restore any content at the specified 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
90
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 7.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
Windows SharePoint Solutions
Database
Farm Level
Level
√
√
√
√
Site
Collection
Level
Site Folder Item Item
Level Level Level Version
Level
InfoPath Form Services
SMSP 7.1 Platform Backup and Restore User’s Guide
91
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
License to Feature Mappings
√
SharePoint Server State Service
√
92
Site
Collection
Level
Site Folder Item Item
Level Level Level Version
Level
Note
This feature is specific to SharePoint 2013.
√
SMSP 7.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
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 7.1 Platform Backup and Restore User’s Guide
93
What to Select When Restoring
(SharePoint 2010 Screenshots Shown Below)
Platform Restore with Specified
Granularity
What to Restore
Content Database
94
Restore Level
Database
Farm Level
Level
√
√
Site
Collection
Level
√
Site Folder Item Item
Level Level Level Version
Level
√
√
√
SMSP 7.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.
What to Select When Restoring
(SharePoint 2010 Screenshots Shown Below)
Platform Restore with Specified
Granularity
What to Restore
Sites with Content types
Restore Level
Database
Farm Level
Level
√
SMSP 7.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 site/site collection will be restored
together with the site/site collection.
√
95
What to Select When Restoring
(SharePoint 2010 Screenshots Shown Below)
Platform Restore with Specified
Granularity
What to Restore
Lists with Content Types
96
Restore Level
Database
Farm Level
Level
√
√
Site
Collection
Level
√
Site Folder Item Item
Level Level Level Version
Level
√
√
SMSP 7.1 Platform Backup and Restore User’s Guide
Note
The content types in the list will be restored together with the
list.
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
SharePoint Built-in Workflow
√
√
√
√
√
√
√
SharePoint Designer Customizations
√
√
√
√
√
√
√
Web Part
√
√
√
√
√
√
√
Note
What to Select When Restoring
(SharePoint 2010 Screenshots Shown Below)
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 not such options.
The SharePoint Designer customizations can be restored
together with the selected content in the content database.
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
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
√
SMSP 7.1 Platform Backup and Restore User’s Guide
√
√
√
√
√
97
√
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
item cannot be associated with the specified managed metadata
term sets.
N/A
Platform Restore with Specified
Granularity
What to Restore
Restore Level
Database
Farm Level
Level
Sites with Custom Templates
√
√
SPUserCode V4
√
√
98
Site
Collection
Level
√
Site Folder Item Item
Level Level Level Version
Level
√
SMSP 7.1 Platform Backup and Restore User’s Guide
Note
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.
If the custom template is written by the customer, it may not be
usable after a Platform restore job because of template
variation.
Type: Microsoft SharePoint Foundation Sandboxed Code Service
Description: Settings for the Sandboxed Code Service.
What to Select When Restoring
(SharePoint 2010 Screenshots Shown Below)
N/A
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
√
SMSP 7.1 Platform Backup and Restore User’s Guide
√
Description: Search instances for Microsoft SharePoint
Foundation
99
What to Select When Restoring
(SharePoint 2010 Screenshots Shown Below)
Platform Restore with Specified
Granularity
What to Restore
100
Restore Level
Database
Farm Level
Level
Site
Collection
Level
Site Folder Item Item
Level Level Level Version
Level
SMSP 7.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
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
SharePoint server.
SMSP 7.1 Platform Backup and Restore User’s Guide
101
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.
102
SMSP 7.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 7.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.
103
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.
NewsGator Social Site 2010 must be installed in the target farm
first.
If you have uninstalled the Newsgator Social Site and want to
restore it, make sure all of the nodes are selected.
NewsGator Social Site 2010
√
√
Only In Place restore type is enabled when restoring NewsGator
Social Site 2010.
If NewsGator Service exists in the farm, select Overwrite to
overwrite the old files; if it has been uninstalled, either
Overwrite or Not Overwrite can be used.
104
SMSP 7.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 7.1 Platform Backup and Restore User’s Guide
Site
Collection
Level
Site Folder Item Item
Level Level Level Version
Level
105
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
This feature is specific to SharePoint 2010.
Nintex Workflow 2010 must be installed in the target farm first.
Nintex Workflow 2010
√
√
Only In Place restore type is enabled when restoring Nintex
Workflow 2010.
If Nintex Workflow exists in the farm, select Overwrite to
overwrite the old one; if it has been removed, either Overwrite
or Not Overwrite can be used.
106
SMSP 7.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 must be installed in the target
farm first.
KnowledgeLake Imaging 2010
√
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 Not Overwrite can be used.
SMSP 7.1 Platform Backup and Restore User’s Guide
107
What to Select When Restoring
(SharePoint 2010 Screenshots Shown Below)
Platform Restore with Specified
Granularity
What to Restore
Customized Database
108
Restore Level
Database
Farm Level
Level
√
Site
Collection
Level
Site Folder Item Item
Level Level Level Version
Level
√
SMSP 7.1 Platform Backup and Restore User’s Guide
Note
You cannot select detailed content inside the database to
restore. You can only restore the whole database.
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 no matter you
choose Overwrite or Not Overwrite option.
IIS Settings
√
SMSP 7.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 Not Overwrite option, the
destination data will not be overwritten.
109
What to Select When Restoring
(SharePoint 2010 Screenshots Shown Below)
Platform Restore with Specified
Granularity
What to Restore
SharePoint Hive
110
Restore Level
Database
Farm Level
Level
√
Site
Collection
Level
Site Folder Item Item
Level Level Level Version
Level
√
SMSP 7.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
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 no matter you
choose Overwrite or Not Overwrite option.
Global Assembly Cache
√
SMSP 7.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 Not Overwrite option, the
destination data will not be overwritten.
111
What to Select When Restoring
(SharePoint 2010 Screenshots Shown Below)
Platform Restore with Specified
Granularity
What to Restore
Custom Features
112
Restore Level
Database
Farm Level
Level
√
Site
Collection
Level
Site Folder Item Item
Level Level Level Version
Level
√
SMSP 7.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
SharePoint Site Definitions
Restore Level
Database
Farm Level
Level
√
SMSP 7.1 Platform Backup and Restore User’s Guide
Site
Collection
Level
Site Folder Item Item
Level Level Level Version
Level
√
113
Note
What to Select When Restoring
(SharePoint 2010 Screenshots Shown Below)
Platform Restore with Specified
Granularity
What to Restore
Extra File System Folders
114
Restore Level
Database
Farm Level
Level
√
Site
Collection
Level
Site Folder Item Item
Level Level Level Version
Level
√
SMSP 7.1 Platform Backup and Restore User’s Guide
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. For
SharePoint 2010, SharePoint built-in workflows, workflows defined by SharePoint Designer, and
workflows defined by Nintex are supported. Workflows defined by Visio Studio are not
supported.
For SharePoint 2013, only the SharePoint built-in workflows are supported.
•
Workflow Instance ─ The item instance created upon the triggering of a workflow definition.
This includes the workflow state, workflow history, and workflow tasks.
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 there is an existing destination workflow definition that has the same name as the one in the source,
then the destination workflow instances are deleted, and the source workflow instances are 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.
SMSP 7.1 Platform Backup and Restore User’s Guide
115
Appendix B: 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
116
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 7.1 Platform Backup and Restore User’s Guide
Appendix C: 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
Backup Tab
The following is a list of hot keys for the Backup tab functions.
Plan Builder
P
Functionality Name and Hot Key
Wizard Mode
W
Storage Policy
Back
Next
Finish
Form Mode
Storage
S
F
S
B
N
F
Cancel
Storage Policy
OK
C
S
O
Cancel
C
SMSP 7.1 Platform Backup and Restore User’s Guide
Finish
Finish and Run Now
F
FR
OK
OK and Run Now
O
OR
117
Policy
Staging Policy
Customize
Database
Command
With
Operation
Functionality Name and Hot Key
A
C
CO
Create
N
Edit
E
Delete
Close
OK
Cancel
Create
Edit
Migrate
Index
MI
Job Monitor
J
Delete
Close
Migrate Index
Page
OK
Cancel
OK
Cancel
O
C
O
C
D
C
O
C
N
Configure
C
E
OK
Cancel
Configure
O
B
C
OK
Cancel
O
B
Back
Next
Start
Cancel
B
N
F
C
D
C
M
OK
Cancel
OK
Cancel
O
B
O
B
Restore Tab
The following is a list of hot keys for the Restore tab functions.
Restore
Farm Rebuild
R
F
Staging Policy
Job Monitor
A
J
118
Functionality Name and Hot Key
Filter
Clear
Disconnect
Restore
Verify
Connect
Back
Next
Finish
Cancel
FI
CL
D
R
V
CO
B
N
F
C
SMSP 7.1 Platform Backup and Restore User’s Guide
Time-based Restore
Time-based Restore
T
Functionality Name and Hot Key
Create Container
T
Advanced Search
AS
Filter
Clear
Staging Policy
Installed Programs
Download Backup List
PE
RE
ZC
I
D
Back
Next
Finish
Cancel
B
N
F
C
OK
Cancel
Search
Cancel
Close
OK
Cancel
O
C
S
C
X
O
C
Plan Manager Tab
The following is a list of hot keys for the Plan Manager tab functions.
View Details
Edit
V
E
Edit
Functionality Name and Hot Key
E Storage Policy
ZP
Plan Group
Close
Storage Policy
P
C
ZP
Staging Policy
ZC
Staging Policy
ZC
Customize Database
ZD
Command With
Operation
Save
CO
Save As
Cancel
A
C
SMSP 7.1 Platform Backup and Restore User’s Guide
S
Save and Run Now
Save
SR
S
119
Functionality Name and Hot Key
Delete
Test Run
D
T
Run Now
R
120
Customize Database
ZD
Command With
Operation
Save
CO
Save As
Cancel
A
C
OK
Cancel
O
C
S
Save and Run Now
Save
SR
S
SMSP 7.1 Platform Backup and Restore User’s Guide
Copyright Information
Copyright © 1994–2013 NetApp, Inc. All rights reserved. Printed in the U.S.A.
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.A. 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).
SMSP 7.1 Platform Backup and Restore User’s Guide
121
Trademark Information
NetApp, the NetApp logo, Network Appliance, the Network Appliance logo, Akorri, ApplianceWatch,
ASUP, AutoSupport, BalancePoint, BalancePoint Predictor, Bycast, Campaign Express, ComplianceClock,
Cryptainer, CryptoShred, Data ONTAP, DataFabric, DataFort, Decru, Decru DataFort, DenseStak, Engenio,
Engenio logo, E-Stack, FAServer, FastStak, FilerView, FlexCache, FlexClone, FlexPod, FlexScale, FlexShare,
FlexSuite, FlexVol, FPolicy, GetSuccessful, gFiler, Go further, faster, Imagine Virtually Anything, Lifetime
Key Management, LockVault, Manage ONTAP, 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, SnapDirector, SnapDrive, SnapFilter, SnapLock, SnapManager,
SnapMigrator, SnapMirror, SnapMover, SnapProtect, SnapRestore, Snapshot, SnapSuite, SnapValidator,
SnapVault, StorageGRID, StoreVault, the StoreVault logo, SyncMirror, Tech OnTap, The evolution of
storage, Topio, 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 U.S.A. and/or other
countries. Microsoft is a registered trademark and Windows Media is a trademark of Microsoft
Corporation in the U.S.A. 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 U.S.A. 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.
122
SMSP 7.1 Platform Backup and Restore User’s Guide

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