Troubleshooting backup and recovery (Windows SharePoint Services 3.0)

  • Article

Applies To: Windows SharePoint Services 3.0

 

Topic Last Modified: 2009-07-13

Troubleshooting

Use the information in the following tables to troubleshoot problems that you encounter during backup or recovery.

Before you back up a Windows SharePoint Services environment for the first time, you must verify that the SQL Server Volume Shadow Copy Service (VSS) is set to start automatically by using the following procedure. You must be a member of the Administrators group on the local computer to perform this action.

  1. Click Start, click Administrative Tools, and then point to Services.

  2. In the list of services, locate SQL Server VSS Writer.

  3. Verify that Status is set to Started and Startup Type is set to Automatic.

  4. If either of these properties is not set to the required value, right-click SQL Server VSS Writer, and then click Properties.

  5. If needed, on the General tab, select Startup type: Automatic.

  6. If needed, in the Service status area, click Start, and then click OK.

Problems during backup

Problem Description

Unfinished backup package is formed.

Symptom: The backup starts but does not finish.

Cause: This could occur if the Windows SharePoint Services Timer service is restarted during the backup process.

Solution: Make sure that the Windows SharePoint Services Timer service is started, and then perform the backup operation again.

Backup operation is stalled.

Symptom: Status displays In Progress for a long time.

Cause: There are several possible causes.

Solution: Look in the Failure Message column on the Central Administration Web site to determine what action is required.

Backup fails.

Symptoms: The backup failed with the error "System.UnauthorizedAccessException".

Cause: The account performing the backup was not granted write permissions to the remote backup folder.

Solution: Grant write access to the account that runs the Stsadm command-line tool and that you use for the application pool identity.

Problems during recovery

Problem Description

Unable to perform a recovery because the farm account credentials have changed.

Symptom: You cannot perform a recovery, and the error message says "Cannot start service Windows SharePoint Services Timer V3 on computer."

Cause: The farm account credentials have changed since the backup was performed.

Solution: Create a new account that has a password that is identical to the old password for the farm account, and then run the recovery again. On a stand-alone installation, you can use a local account. On a farm installation, you must set up a domain account.

Unable to perform a recovery because the administration content database is corrupted or missing.

Symptoms: You cannot perform a recovery.

Cause: Account credentials are stored in the administration content database. That content database is corrupted or missing.

Solution: Add the account that you want to use to perform the recovery to the Administrators group or the WSS_ADMIN_WPG group on the local computer. After the account is added, you can use it to perform the recovery by using the Stsadm command-line tool.

Unable to perform the recovery because the first attempt failed and you cannot try again.

Symptom: The first cannot at backup or recovery failed, and now you are prevented from trying the operation again.

Cause: The previous timer job became corrupted.

Solution: Delete the previous failed timer job, and then try the operation again.

A host header associated with a Web application is not restored correctly.

Symptom: The Web application is restored without its host header binding.

Cause: This is a known bug.

Solution: First, create the Web application that has the host header binding.  Then restore the content database only.  Finally, attach the content database to the Web application by using the Stsadm addcontentdb operation. For more information, see Addcontentdb: Stsadm operation (Windows SharePoint Services).

Recovery is stalled.

Symptom: Status displays In Progress for a long time.

Cause: There are several possible causes.

Solution: Look in the Failure Message column in Central Administration to determine the action needed.

Recovery fails.

Symptoms: The recovery status page displays the error "Failed in the OnRestore event."

Cause: An attempt to delete a content database by using the Central Administration Web site or the Stsadm command-line tool was not successful. The database still exists. Therefore, the recovery operation could not overwrite the existing database in SQL Server 2005.

Solution: Use a different database name or delete the previous content database by using SQL Server Management Studio, and then try the operation again.

Recovery with new configuration does not overwrite the previous configuration.

Symptoms: The recovery did not overwrite the previous configuration.

Cause: The databases are still attached to the old configuration.

Solution: To restore the backup to a new configuration, you must first remove the databases from the previous Web application. You can do this on the Manage Content Database Settings page on the Central Administration Web site.

Recovery fails in a topology that has multiple front-end Web servers.

Symptoms: Recovery fails with an "OnPostRestore" error in a topology that has multiple front-end Web servers.

Cause: The failure could be caused by any combination of the following:

  • You used the Central Administration Web site.

  • The farm account is not a member of the Administrators group on the local server computer.

  • You are restoring a Web application.

Solution: Do one of the following, and then try the recovery again:

  • Use the Stsadm command-line tool to perform the recovery.

  • Create a new Web application on the server that you are restoring to, and then restore the content databases to the newly created Web application.

  • Add the farm account to the Administrators group on the local server computer.

See Also

Concepts

Protecting and restoring the farm (Windows SharePoint Services 3.0)
Protect and restore content by using Recycle Bins and versioning (Windows SharePoint Services 3.0)
Back up and restore the farm (Windows SharePoint Services 3.0)
Use alternative methods to back up and restore content (Windows SharePoint Server 3.0)