Restore Troubleshooting - SharePoint Server iDataAgent

Backup Restore  

SP0005: Host header associated with a web application is not restored correctly for SharePoint 2007

Problem

Web Application that uses Host Headers (with SSL bindings) is restored without the Host header bindings during a Web Application restore.

Solution

To resolve this issue follow the steps given below:

  1. Create the Web Application that has the Host Header bindings.
  2. Log on to CommCell Console and  use the Databases backup set to restore the content databases for the Web Application that uses Host Headers (with SSL bindings).

SP0006: Error Message: "The IIS web site you have selected is in use by SharePoint. You must select another port or hostname."

Problem

Restores may fail for SharePoint 2007 Host Header Web Applications if the Web Application with Host Header uses the same port number as that of other Web Application.

Solution

To resolve this issue follow the steps given below:

  1. Create the Web Application that has the Host Header bindings.
  2. Log on to CommCell Console and  use the Databases Backup set to restore the content databases for the Web Application that uses Host Headers (with SSL bindings).

SP0007: Restore of SharePoint web application completed with one or more error

Problem

Restore of SharePoint Web Application completes with one or more errors and items failing with the following error message:

"SPUpdatedConcurrencyException: An update conflict has occurred, and you must re-try this action. The object SPWebApplication Name=[WebApp_name] is being updated by [user_account], in the OWSTIMER process, on machine [machine_name]. View the tracing log for more information about the conflict."

Solution

Out-of-Place Restore

  1. Stop SharePoint Timer Service
  2. For out-of-place restore, delete partially restored Web Application.
  3. Resubmit Web Application restore job.
  4. Restart the SharePoint Timer Service.

In-Place Restore

  1. Stop SharePoint Timer Service
  2. Resubmit Web Application restore job.
  3. Restart the SharePoint Timer Service.

SP0009: Failure in importing ghost pages during an In-Place restore

Problem

While restoring sub-sites using the SharePoint Document agent, an error appears due to failure in importing the ghost pages (files and views that reside on the front-end web server) in the import.log file:

FatalError: Object reference not set to an instance of an object.

Solution

To resolve this issue, set the values of dImportRetainObjectIdentity as zero and bImportSkipGhostPages as one.

  1. To run an in-place restore, set the value of dImportRetainObjectIdentity as zero.
    1. From the CommCell Browser, navigate to Client Computers.
    2. Right-click the <Client> and then click Properties.
    3. On the Client Computer Properties dialog box, click Advanced.
    4. Click the Additional Settings tab.
    5. Click Add.
    6. In the Name box, type dImportRetainObjectIdentity.
    7. The Category and Type details will be automatically populated.
    8. Alternatively, you can click Lookup and search for the additional setting using the Find box.
    9. In the Value field, enter 0.
    10. Click OK.
  2. To skip restoring ghost pages, set the value of bImportSkipGhostPages as one.
    1. From the CommCell Browser, navigate to Client Computers.
    2. Right-click the <Client> and then click Properties.
    3. On the Client Computer Properties dialog box, click Advanced.
    4. Click the Additional Settings tab.
    5. Click Add.
    6. In the Name box, type bImportSkipGhostPages.
    7. The Category and Type details will be automatically populated.
    8. Alternatively, you can click Lookup and search for the additional setting using the Find box.
    9. In the Value field, enter 1.
    10. Click OK.

SP0011: SharePoint restore operation may fail if a virus scanner is running on the server

Symptom

Restore operation fails if a virus scanner is running on the SharePoint server. You might see the following error in the CVSPRestore.log file:

The specified network name is no longer available.

Cause

During a restore operation, a virus scanner running on the Sharepoint server may delete staging files or network share.

Resolution

On the SharePoint server, either disable the virus scanner or exclude SnapProtect processes from the virus scanner configuration.

SP0012: SharePoint In-Place restore operation of host name site collection may fail

Symptom

Sometimes during an In-Place restore of host name site collection, the restore operation fails with the following error in the CVSPRestore.log file:

Collection failed with Exception [System.IO.DirectoryNotFoundException: <nativehr>0x80070003</nativehr><nativestack></nativestack>

Resolution

Perform the following steps as a work around for this issue:

  1. From the SharePoint Central Administration, remove the content database associated with the WebApp.
  2. Add the content database again to the WebApp.
  3. Perform the In-Place restore operation.

Recovering data associated with deleted clients and storage policies

Symptom

In a disaster recovery scenario, use the following procedure to recover data associated with the following entities:

  • Deleted storage policy
  • Deleted client, agent, backup set or instance

Before You Begin

This procedure can be performed when the following are available:

  • You have a Disaster Recovery Backup that contains information on the entity that you are trying to restore. For example, if you wish to recover a storage policy (and the data associated with the storage policy) that was accidentally deleted, you must have a copy of the disaster recovery backup that was performed before deleting the storage policy.
  • Media containing the data you wish to recover is available and not overwritten.
  • If a CommCell Migration license was available in the CommServe when the disaster recovery backup was performed, no additional licenses are required. If not, obtain the following licenses:
    • IP Address Change license
    • CommCell Migration license

    See License Administration for more details.

  • A standby computer, which is used temporarily to build a CommServe.
Recovering Deleted Data
  1. Locate the latest Disaster Recovery Backup that contains the information on the entity (storage policy, client, agent, backup set or instance) you are trying to restore.
    • Check the Phase 1 destination for the DR Set or use Restore by Jobs for CommServe DR Data to restore the data.
    • If the job was pruned and you know the media containing the Disaster Recovery Backup, you can move the media in the Overwrite Protect Media Pool. See Accessing Aged Data for more information. You can then restore the appropriate DR Set associated with the job as described in Restore by Jobs for CommServe DR Data.
    • If the job is pruned and you do not know the media containing the Disaster Recovery Backup, you can do one of the following:
      • If you regularly run and have copies of the Data on Media and Aging Forecast report, you can check them to see if the appropriate media is available.
      • If you do not have an appropriate report, and know the media that contains the DR Backup, catalog the media using Media Explorer. Once the cataloging process is completed, details of the data available in the media are displayed.
  2. On a standby computer, install the CommServe software. For more information on installing the CommServe, see Install the CommServe.
  3. Restore the CommServe database using the CommServe Disaster Recovery Tool from the Disaster Recovery Backup described in Step 1. (See CommServe Disaster Recovery Tool for step-by-step instructions.)
  4. Verify and ensure that the NetApp Client Event Manager NetApp Communications Service (EvMgrS) is running.
  5. If you did not have a CommCell Migration license available in the CommServe when the disaster recovery backup was performed, apply the IP Address Change license and the CommCell Migration license on the standby CommServe. See Activate Licenses for step-by-step instructions.
  6. Export the data associated with the affected clients from the standby CommServe as described in Export Data from the Source CommCell.

    When you start the Command Line Interface to capture data, use the name of the standby CommServe in the -commcell argument.

  7. Import the exported data to the main CommServe as described in Import Data on the Destination CommCell.

    This brings back the entity in the CommServe database and the entity is visible in the CommCell Browser. (Press F5 to refresh the CommCell Browser if the entity is not displayed after a successful merge.)

  8. You can now browse and restore the data from the appropriate entity.

    As a precaution, mark media (tape media) associated with the source CommCell as READ ONLY before performing a data recovery operation in the destination CommCell.