Restore Data - SharePoint Server
Topics |
How To |
Full System Restore | Troubleshoot |
Related Topics
Overview
Restore Considerations
for This Agent
Restore Destinations
The following page describes the agent-specific restore options. Additional restore options are accessible from the Related Topics menu.
The SharePoint Database backup sets allow
you to restore SharePoint Database Components and Site Collections.
You can perform the following types of restores:
When you restore the SharePoint data, you are
over-writing your existing data. Data from after the date of that
backup will be lost. The restore operation only provides data from the
point in time when it was backed up.
If the SQL databases for the SharePoint Server were not backed
up by the SharePoint Server iDataAgent, then
they must first be restored on the SQL Server using the
Microsoft SQL
iDataAgent before performing the
SharePoint Server Database Restore Procedure.
For SharePoint Portal Server 2003, if you configure Shared Services, the Portal Site that provides the Shared
Services must be restored/exist before restoring any other Portal Sites.
SharePoint Document
The SharePoint Document backup sets
restore the Top Level sites, sub-sites, Areas, Libraries, and Lists.
The system offers the following options for restoring selected Library items when the
object already exists in Non-Versioned Libraries, which are available in the Restore Options dialog
box.
- Unconditional Overwrite - If an item that is
selected for restore already exists, then that item will be overwritten by the
restored item.
- Skip - If an item is selected for restore and
that item already exists, it will not be restored.
- Restore All Versions - Specifies that all versions of a multi-versioned document
will be restored to a Version Enabled
Library.
NOTES
Before performing any restore procedures for this agent, review the following
information:
SharePoint Server - General
If you have not already done so for the Client to which you are restoring
data, ensure the Client is configured as follows:
The
Base Services of the client
will run under the user account that is specified.
Use an account that meets this criteria:
- member of the local Administrator Group
- member of the SharePoint Administrator Group
- System Administrator role on the SQL Server Instance
In addition, this account must have "Log on as Service" permissions to
ensure the Communication (CVD) Services will
start. For more information on Base and Communication (CVD) Services,
see Services.
Refer to the Knowledge Base article, ID #10573, Galaxy Service Account User Information for Windows
2003 and Window Server 2003 clients available from the
Maintenance Advantage web
site.
SharePoint
Server Database
-
When restoring a Site Collection, temp space is required under the Job
Results folder for staging Site Collections, Portal Indexes, and SharePoint
metadata.
-
After restore, a Site Collection will have a new SiteID and
will show up as new content during a discover/backup operation. You should
manually find the restored site collection and reassign it to the previously
assigned subclient.
Otherwise, the backup of an empty subclient may fail, which displays an "ArchiveIndexfailed
on MediaAgent - index files are missing, possibly due to a failover"
error message and generates an "Failed to record
actual create time in index files" event.
SharePoint Server Document
Site Collections, Top Level Sites, Subsites
Areas
- Portal Site bucket Areas will be restored into the first available
bucket.
Discussion Boards
- Some columns may be duplicated when restoring a Discussion Board from
SharePoint Portal Server 2003 to SharePoint Server 2007. If so, delete any
duplicate columns that are not needed.
- During entire Discussion Board restore:
- On SharePoint 2003, restored Threaded Views are restored as Flat Views.
- On SharePoint 2007, it is recommended to delete restored Flat and
Threaded Views and use those that are automatically created (Flat.aspx
and Threaded.aspx).
Library and Library Items
-
While .aspx files for basic Web Part and
Dashboard Pages from a
Library can be backed up and restored,
restoring the file will not restore the Web Part to the page. Modifications made
to the page using the Content Editor Web Part will not be restored and cannot be
made to the file after it has been restored.
-
To prevent "Error setting '2' WebPart(s) in file
*.aspx", deselect WebMetaDataFiles if restoring with option
"Unconditional overwrite" over a site that already contains the Web Parts
being restored.
- Document versions are
always restored as new versions for Version Enabled Libraries. A restored
document will not be available with the same version number it had when it
was backed up.
- If a document from a Version Enabled Library is
restored to a Version Disabled library, only the latest document version
will be restored.
- If all document versions from a Library that tracks Major and Minor
versions are restored to the same Library or a different Library with the
same settings, then all versions will be restored as Minor versions.
- If all document versions from a Library that tracks Major and Minor
versions are restored to a Library that tracks only Major versions, then all
versions will be restored as Major versions.
-
During a
library restore, the library's document template is set to default value. If the library used a different template file, or none at
all, you must change the document template properties to the desired value
using the "Specify a Custom Template" procedure under "Set up a template for
a library" in
http://office.microsoft.com to work around this issue.
- For a restored Library, the value of the "Modified By"
column will be the name of the account running
Services, and the
value of the "Modified Time" column will be the current date and time.
- Restoring Explorer Views may overwrite or corrupt existing Explorer
Views and may not work properly. If an Explorer View is overwritten or
corrupted, to recreate a Explorer View for SharePoint 2007 libraries:
- Go to "Create View" menu.
- Click on "Explorer View" under the "Start from a view template".
- Type in "Explorer View" as the View Name.
To recreate Explorer Views for SharePoint 2003, the entire Library must be
restored and the Explorer View that is created will automatically work.
- While browsing documents in CommCell Console, the size of documents may
not match the size that appears in the SharePoint Server User Interface.
This is due to metadata being backed up with the document, which
artificially could increase its size.
-
After restoring an XML form to a Forms Library, do the following to relink it
to the Forms Library:
- Open the Forms Library in Internet Explorer.
- Go to Form Library settings.
- Click Relink forms to this form library.
- Select the restored form.
- Click Relink Forms.
List and List Items
- The unconditional
overwrite and skip options are ignored during restore.
- List items can only be
restored to Lists of the same type.
- Since list items are
always restored as new items without the same list ID, multiple lists and
multiple list items with the same name are allowed. Therefore, you may see
duplicates of lists and their items.
- Threaded discussion boards are restored and displayed as Flat views.
After restoring, a Threaded view can be simulated if you select the Group By
"Subject" View setting.
- Any deleted Lists linked to by
Outlook, Excel, Access, etc. must be relinked after the restore.
- Delete any unwanted List Views after
the restore (they will appear numerous times).
- Out-of-place restore of a List
may fail if restored to a site that does not have that list type. For
example, some Meeting Workspaces have lists that are specific to the Meeting
Workspace, so these cannot be restored to a Document Workspace or a Team Site.
- For Survey Lists, the "Allow Multiple Responses" option must be selected
in SharePoint List Settings, or the restore will complete with errors.
- For a restored List or List item, the value of the "Modified By"
column will be the name of the account running
Services, and the
value of the "Modified Time" column will be the current date and time.
- Restoring multi-versioned list items (individual items or the entire
list) with a renamed "Title" column causes each version of the item to be
restored as a separate item.
SharePoint Server Document
By default, the SharePoint Server iDataAgent restores data to the client computer
and path from which it originated; this is referred to as an in-place restore.
- To restore a Site Collection, you should restore a Top-Level Site first
and then the subsites.
- To restore a deleted Sub-site, browse
and select the site and leave all restore options by default.
The following section enumerates the types of restore destinations that are
supported by the SharePoint Server iDataAgent. See Restore/Recover/Retrieve Destinations - Support for a list of Agents
supporting each restore destination type.
You can
also restore the data to another Client
computer in the CommCell. Keep in mind the following considerations when
performing such restores:
- The destination client must reside in the same CommCell as the client
whose data was backed up.
- The restore destination must be on another SharePoint Server with
the SharePoint Server iDataAgent
installed and operational.
- The destination server must either be in the same domain as the original
server, or be in a domain having the proper trust relationship established
both with the original domain, as well as all of the domains with which the
original server’s domain had trust relationships.
- The restore data will
assume the rights (i.e., permissions) of the parent directory.
- To restore a site created by a user-defined Site
Template to a server in a different farm, the Site Template must exist with
the same ID in the destination computer. To change the configuration ID for
user defined templates, open the
CustomTemplates
table in the Configuration database and modify the ID column for the row for
the custom template used.
- To restore a Top Level Site to a
different path, browse and select the Site Collection level for the restore
destination path.
|
- For SharePoint Server Document backup sets, select only one site
at a time for an out-of-place restore of an entire site.
- For SharePoint Server Database backup sets, restore operations across clients with different Windows SharePoint
Services (WSS) Service Pack levels are not supported.
- For SharePoint Portal Server 2003 and SharePoint Server 2007, an
out-of-place restore of Lookup column types for lists and libraries is
not supported because the dependent list or library (which the Lookup
column refers to) will not be present on the target machine.
|
SharePoint Server Database
- Cross-application
restores of databases between different versions of SharePoint Servers are
not supported.
SharePoint Server Document
- Cross-application
restores for library and list items to the same or higher SharePoint Server
version are supported.