Topics | How To | Full System Restore | Troubleshoot | Related Topics
Restore Considerations for This Agent
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:
Application | Specific Restore Procedures | Common Restore Procedures |
Microsoft SharePoint Foundation 2010 SharePoint Server 2010 (Standard and Enterprise) Microsoft Office Project Server 2010 Fast Search Server 2010 for SharePoint Microsoft Search Server 2010 Microsoft Search Server 2010 Express |
Restore a Service
Application
Restore a Service Application Proxy
|
Restore a Site Collection |
Microsoft Search Server 2008 | Restore a Search Server Shared Service Provider | Restore a Site Collection |
Windows SharePoint Services (WSS) version 3 | Restore a Site Collection | |
Microsoft Office SharePoint Server (MOSS) 2007 | Restore a Search Server Shared Service Provider | |
Microsoft Office Project Server 2007 | Restore a Site Collection | |
Microsoft Office Forms Server 2007 | Restore a Shared Service Provider | |
Windows SharePoint Services (WSS) version 2 | Restore a Site Collection | |
Microsoft SharePoint Portal Server 2003 |
Restore a Portal Site Restore a Site Content Database |
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.
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.
NOTES
Documents restored to Version Disabled libraries will be restored with Skip regardless of the option selected.
Before performing any restore procedures for this agent, review the following information:
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:
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 Galaxy Service Account User Information for Windows 2003 and Window Server 2003 clients available from the Maintenance Advantage web site.
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.
The four databases namely Archive, Draft, Published and Reporting cannot be distributed over multiple subclient. They need to be backed up and restored together as they belong to the same PWA (Project Web Access) Site.
For WSS Web Application Content Database restores with Extend URL option selected, these registry keys are applicable:
The sOwnerLogin registry key is used during an in-place restore of a web application with the original name using the specified owner login.
The sOwnerEmail registry key is used during an in-place restore of a web application with the original name using the specified owner email address.
The bDoNotUseNTLM registry key is used to change the default authentication type of a restored Web application from NTLM to Negotiate (Kerberos).
For SharePoint 2010 stand-alone deployments, ensure that the SQL Server instance service account and SharePoint 2010 Timer service account are switched to Local System. Once the restore is finished, you can switch back to using the previous accounts (e.g., Network Service).
For SharePoint Server 2010, these registry keys are applicable for site collection restore operations:
Site collections that are overwritten can be gradually deleted over time by a timer job instead of all at once by enabling the dwGradualDelete registry key. This key can reduce impact on SharePoint and SQL Server performance and is recommended for large site collections.
The sDatabaseName registry key can be used to specify the SQL Server content database as to where the site collection data should be restored. If the content database is not specified, the site collection data will be restored to the location where there is a high unused capacity of the site location and also its database status is ready.
The sDatabaseServer registry key can be used to specify the SQL Server containing the content database specified by the sDatabaseName registry key. Both registry keys need to be configured.
The sHostHeaderWebApplication registry key can be used to restore a site collection with the host name.
When both SharePoint 2003 and SharePoint 2007 servers co-exist on the same client with the SharePoint Agent, the subclient content needs to be properly configured.
See Subclient Content when SharePoint 2003 and 2007 Servers Co-exist for more information.
For successful backup and restore of site collections or personal sites, the SharePoint Administrator Account should also be added as user with Full control for all sites. It can be done using Policy for Web Application (Application Management - Application Security - Policy for Web Application).
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.
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.
After restoring an XML form to a Forms Library, do the following to relink it to the Forms Library:
When the Browse data from SQL browse option is selected in the Browse Options dialog box, virtual server names are displayed instead of virtual server URLs while browsing content of an offline SharePoint 2003 database.
When the Browse data from SQL browse option is selected in the Browse Options dialog box, items from Libraries located in Portal Areas are not available for restore while browsing content of an offline SharePoint 2003 database.
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.
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:
|