Restore Data - SharePoint Server iDataAgents - Full System Restore

Topics | How To | Full System Restore | Troubleshoot | Related Topics

Overview

Perform a Full System Restore for SharePoint

Overview

The difference between a normal restore and a full system restore is the severity of the problem. Normally, if data is lost or removed, it is recovered from the archives using the normal restore procedures. However, when a normal restore operation cannot correct a software and/or hardware corruption problem, some additional changes may be required.

When the client system (software, hardware, hard drives, etc.) is damaged or destroyed, a full server restore may be required. If a System State or File System restoration is necessary on the system where the SharePoint Server resides, refer to the appropriate File System's Disaster Recovery procedures. The SharePoint Server iDataAgent should be installed and full backup scheduling enforced prior to any SharePoint Server iDataAgent restore.

For the SharePoint Archiver agent, the database file that tracks the stubs is not backed up with the SharePoint Server  iDataAgent. Therefore, you should back up this file with the Windows File System iDataAgent to ensure that stubs can be recovered. See Migration Archiving Considerations for details. 

Perform a Full System Restore for SharePoint

The general procedure for a full system rebuild is described below. Refer to the documentation on each of the components when rebuilding the system. For example, be sure to perform the appropriate File System's Disaster Recovery procedures prior to restoring the data using the SharePoint Server iDataAgent.

To perform these operations, valid backups of the Windows File System with VSS option, SQL Server, and SharePoint Database must exist.

Web Server or All-In-One Server

  1. Follow the procedure for Restore Data - Windows File Systems - Full System Restore - How To. Full system restore will bring back IIS and SharePoint.
  2. After completing Restore Data - Windows File Systems - Full System Restore, the SharePoint Services will be running but trying to access the Configuration Database.
  3. In an All-In-One Configuration, check if SQL Server services are up and running and if SharePoint SQL databases are accessible via SQL Server Management Tools (Enterprise Manager or Management Studio). In case SQL Server is not running, it will be necessary to perform Restore Data - Microsoft SQL Server - Full System Restore.

    SharePoint 2010:

    1. Run the SharePoint Product and Technologies Configuration wizard.
    2. Ensure that all SharePoint services are running prior to performing the restore.
    3. Using the SharePoint Server iDataAgent, follow the appropriate procedure:

      Set the sOwnerLogin and sOwnerEmail registry keys to preserve the original Web application name, and then restore a SharePoint Server WSS Web Application Content Database with the Extend URL option selected.

      Restore a SharePoint Server Shared Service Provider

      Restore a SharePoint Server WSS Search

    SharePoint 2007:

    1. Run the SharePoint Product and Technologies Configuration wizard.
    2. Ensure that all SharePoint services are running prior to performing the restore.
    3. Using the SharePoint Server iDataAgent, follow the appropriate procedure:

      Set the sOwnerLogin and sOwnerEmail registry keys to preserve the original Web application name, and then restore a SharePoint Server WSS Web Application Content Database with the Extend URL option selected.

      Restore a SharePoint Server Shared Service Provider

      Restore a SharePoint Server WSS Search

    4. Run iisreset from the command line.

    SharePoint 2003:

    1. From SharePoint Central Configuration, disconnect from the Configuration Database.
    2. Create a new Configuration Database.
    3. Connect all previous servers to the new Configuration Database (for farm) and configure the same component assignments for the server on the Configure Server Topology page.

      On the Virtual Server list page, the IIS Virtual Servers for the Web Server may appear extended. From the Virtual Server Settings page for each extended virtual server, click Remove Windows SharePoint Services from virtual server. It might return an error that the virtual server is not in the Configuration Database but this will ensure the Virtual Server is available to be extended.

    4. Using the SharePoint Server iDataAgent, follow the appropriate procedure:

      Restore a SharePoint Server Portal Site

      Restore a SharePoint Server Site Content Database

      Restore a SharePoint Server Site Index

      Restore a SharePoint Server Teamsite Database

      Restore a SharePoint Server Webstorage System Database

    5. Run iisreset from the command line.

    Small Server Farm

    Database Server

    Follow procedure for Restore Data - Microsoft SQL Server - Full System Restore.

    When restoring the SQL Databases for SharePoint, do not restore the Configuration Database and the Central Administration Web Application Content Database.

    Web Server

    Follow the Web Server or All-in-One Server procedure.

    Medium or Large Server Farm

    Database Server

    Follow procedure for Restore Data - Microsoft SQL Server - Full System Restore.

    When restoring the SQL Databases for SharePoint, do not restore the Configuration Database and the Central Administration Web Application Content Database.

    Web Server

    Follow the Web Server or All-in-One Server procedure.

    Indexing Server

    1. Follow the procedure for Restore Data - Windows File Systems - Full System Restore - How To.
    2. From the Web Server using the SharePoint Server iDataAgent, follow the appropriate procedure to restore:
    3. Force Propagate the Index(es) to the Query Server(s) for SharePoint 2003.

    Query Server

    1. Follow the procedure for Restore Data - Windows File Systems - Full System Restore - How To.
    2. Force Propagate the Index(es) to the Query Server(s) for SharePoint 2003.