Export (0) Print
Expand All

Configuration backup and restore (FAST Search Server 2010 for SharePoint)

FAST Search Server 2010

Published: May 12, 2010

The configuration backup makes a snapshot of the FAST Search Server 2010 for SharePoint configuration setup and the FAST Search Server 2010 for SharePoint administration database. You must restore the backup to an existing FAST Search Server 2010 for SharePoint deployment, either to the same deployment as the backup was made from, or to another deployment with other servers or with a different deployment.xml file.

Before you run a configuration backup or restore, see Backup and restore prerequisites (FAST Search Server 2010 for SharePoint).

In this article:

Make a configuration backup

  1. Open a Microsoft FAST Search Server 2010 for SharePoint shell as administrator.

  2. At the command prompt, browse to <FASTSearchFolder>\bin.

    Where <FASTSearchFolder> is the path of the folder where you have installed FAST Search Server 2010 for SharePoint, for example C:\FASTSearch.

  3. Run the following command:

    .\backup.ps1 –action config –backuppath <UNC path of backup store>
    

The script will prompt you for a password to authenticate itself to remote resources. To run the script without having to enter a password, use the -passwordfile option to specify a file that contains a saved password. See Run scripts with a saved password for more information.

Before the backup starts, the script checks if the backup store already exists, or not. If you want to overwrite an existing backup set, use the –force option when you run the backup script.

Copy the backup of the administration database to the backup store

The administration database backup file is generated locally on the SQL Server, and is not stored in the FAST Search Server 2010 for SharePoint backup store. To maintain a complete backup file set, you should copy the database backup to the backup store after you run the backup script.

There can be several SQL Server backup files in the SQL Server folder. You can find the exact name of your SQL Server backup file in the dbbackup.txt file in the FAST Search Server 2010 for SharePoint backup store. You can also find more information about the SQL Server backup process in the SQLServerMetaData.txt file in the backup store. The lines that contain BackupDirectory and NetName display the path and host name for the SQL Server.

  1. Locate the administration database backup file in the SQL Server folder.

  2. Copy the file to the backup store.

Restore a configuration backup to the same deployment

To restore a configuration backup to the same system as it was backed up from, with the same server name and the same deployment file:

  1. Make sure that the FAST Search Server 2010 for SharePoint administration database backup file is present on the SQL Server.

  2. Open a Microsoft FAST Search Server 2010 for SharePoint shell as administrator.

  3. At the command prompt, browse to <FASTSearchFolder>\bin.

    Where <FASTSearchFolder> is the path of the folder where you have installed FAST Search Server 2010 for SharePoint, for example C:\FASTSearch.

  4. Run the following command:

    .\restore.ps1 –action config –backuppath <UNC path of backup store>
    

    The script will prompt you for a password to authenticate itself to remote resources. To run the script without having to enter a password, use the -passwordfile option to specify a file that contains a saved password. See Run scripts with a saved password for more information.

  5. When the configuration restore script is complete, restart the FAST Search Server 2010 for SharePoint service on all servers:

    Stop-Service FASTSearchService
    Start-Service FASTSearchService
    

Restore a configuration backup to a different deployment

To restore the configuration backup to different servers or to a system with a different deployment file:

  1. Make sure that the FAST Search Server 2010 for SharePoint administration database backup file is present on the SQL Server.

  2. Open a Microsoft FAST Search Server 2010 for SharePoint shell as administrator.

  3. At the command prompt, browse to <FASTSearchFolder>\bin.

    Where <FASTSearchFolder> is the path of the folder where you have installed FAST Search Server 2010 for SharePoint, for example C:\FASTSearch.

  4. Run the following command:

    .\restore.ps1 –action configmigrate –backuppath <UNC path of backup store>
    

    The script will prompt you for a password to authenticate itself to remote resources. To run the script without having to enter a password, use the -passwordfile option to specify a file that contains a saved password. See Run scripts with a saved password for more information.

  5. When the configuration restore script is complete, restart the FAST Search Server 2010 for SharePoint service on all servers:

    Stop-Service FASTSearchService
    Start-Service FASTSearchService
    

Troubleshooting configuration backup and restore

Issue: The content is not searchable after a configuration restore

Symptom: The content is not searchable after you have restored a configuration backup.

Cause: The backed up system and the restored system have different sets of managed properties.

The managed properties are part of the index schema, which specifies which content parts are indexed. If the managed properties have been changed after the configuration backup was taken, the restored configuration includes a set of managed properties that does not match the indexed content.

Resolution: Re-feed all content.

To prevent this problem, make sure that you make a configuration backup when you change the set of managed properties changes, and that you only restore the latest configuration backup.

Issue: The SPREL configuration restore fails

Symptom: A typical indication of this problem is this error message: "Can't change FDM config when FDM is running".

Cause: Relevancy processing is active.

In rare cases, restoring the SharePoint Relevancy (SPREL) configuration can fail because the relevancy processing is running at the same time as the restore process.

Resolution: Try running the restore script later.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft