Restoring SharePoint Portal 2003 and Windows SharePoint Services Data
The following topics describe how to restore each SharePoint component. When properly configured, Microsoft SQL Server 2000 environments support point-in-time restores of SharePoint data.
Related Topics:
Note. You can restore the entire SharePoint Portal 2003 or Windows SharePoint Services infrastructure in a single Restore job. If you choose to do this, you must be sure to select the appropriate restore destinations for each source component. Also be aware that if you restore all components of a SharePoint infrastructure, you will restore all of the services to the point-in-time when the backup was taken. If there have been any changes to anything in the topology of the infrastructure (for example, new or changed server names) or if other applications depend on IIS, a full restore may not be appropriate.
The SharePoint administrator is responsible for identifying which files and databases need to be restored for a given SharePoint Portal Server or Windows SharePoint Services.
Note. You may not need to restore all three components of the SharePoint for a successful recovery. You may not even need to restore multiple SharePoint content databases. If you elect not to restore all three components, be sure that the components being restored are in sync with the components not being restored. For example:
If you are restoring the SharePoint content database(s), make sure the IIS configuration and the SharePoint configuration database have not been modified since backing up the SharePoint content database(s).
If the SharePoint infrastructure has changed, the backed up configuration database may no longer be in sync with the rest of the SharePoint system. In that case, you can restore only the SharePoint content databases, and the SharePoint administrator can create a new configuration database or modify the existing configuration database separately using SharePoint tools.
Last updated