Article ID: 967568 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
If users update content on the site while you are backing up a SharePoint site collection, the backup file may become corrupted. Then, when you try to restore the site to another location, the restore operation fails.
Note To back up a SharePoint site collection, you can use the following command:
stsadm -o backup -url http://server_name/sites/site_name -filename site_name.bak
To work around this issue, follow these steps:
To resolve this issue, install the hotfix package that is described in Microsoft Knowledge Base article 968857. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/968857/ )Description of the Windows SharePoint Services 3.0 hotfix package (Sts.msp): April 28, 2009
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
After you apply this hotfix, the site collection backup behavior changes.
During the site collection backup operation, the Stsadm.exe utility will automatically set the site collection lock to be "readonly" if it was "none" or "noadditions." Then it will perform the site collection backup and then return the site collection lock back to its initial state. The Stsadm.exe utility will record the site collection’s initial lock state in the backup file so that a site collection restore will preserve the initial site collection lock state instead of the "readonly" state that it automatically set during the backup.
If you want to use the previous site collection backup behavior where the Stsadm.exe utility does not modify the site collection lock during a site collection backup, you can add the new "-nositelock" parameter to the command. The following is an example:
stsadm -o backup -url http://server_name/sites/site_name -filename site_name.bak -nositelock