| |||||
| |||||
With Microsoft Windows SharePoint Services, you can back up and restore site collections hosted on your server or server farm. You can use this backup and restore method to replace a site collection that has become corrupted, or that contains changes that need to be rolled back (for example, if you need to recover a list or a list item that was deleted accidentally). This backup and restore method is not dependent on the type of database server that you are using. You can perform this backup and restore even if you are running Microsoft SQL Server Desktop Engine (Windows) 2000 (WMSDE) instead of Microsoft SQL Server 2000.
If you need to back up a specific site, rather than a whole installation of Windows SharePoint Services, you can do so by using the backup and restore operations with the Stsadm.exe command line tool. You do not need SQL Server 2000 to perform a site-by-site backup. If you are using WMSDE, this is the only backup and restore option that is available.
When you back up a site collection, you back up the content database for the site collection, including all pages in the site, files in document libraries or lists, security and permission settings, and feature settings. The backup process creates a single file that contains all of this data. You can then restore your site collection to either the same location, or to a new location. The backup file for a site includes any subsites of the site collection.
You must be a member of the server computer's Administrators group to back up or restore a site.
Site backup and restore is intended to help you reconnect sites that have become corrupted or that need to be restored to a previous state. This process is not intended for moving a site to a new server. If you want to move a site, use the Microsoft SharePoint Migration Tool (smigrate.exe) instead. For more information, see About migrating Web sites.
When using site backup and restore, keep the following items in mind:
You can use the object model to include the backup operation in a scripted procedure. For more information, see the Microsoft Windows SharePoint Services Software Development Kit.
The process of backing up and restoring sites takes up both memory and processing power on your server. If you choose to schedule automatic backups in a batch file or script, be sure to run the backup process when server usage is light.
This could be a problem in the following situation: If you have two virtual servers, with separate content databases for each virtual server that are listed only by relative paths in the configuration database, the site names may conflict. For example, if the configuration database lists the site names without the http://server_name prefix, you could have several sites that use the same path. For example, http://server_1/sites/site1 and http://server_2/sites/site1 could both be listed in the configuration database as /sites/site1, even though they are on separate virtual servers. In this case, the sites will not be restored correctly, and you will see an error in the restore log file.
If a site that you are restoring to a new server used a specific language pack, you must add the language pack to the new server before restoring the site. You can also update the new server with the language pack after you restore. If you do not add the language pack, users who browse to the site or any subsites will see a "file not found" error.
When restoring a site that was running in Active Directory account creation mode, the destination site must also be running in Active Directory account creation mode. Further, you cannot restore a site that was not running in Active Directory account creation mode to a server that is running in Active Directory account creation mode.
Important
stsadm –o deletesites –deleteusers false