Configuration backup and restore (FAST Search Server 2010 for SharePoint)(informazioni in lingua inglese)
Aggiornato: 10 giugno 2010
The configuration backup takes a snapshot of the FAST Search Server 2010 for SharePoint configuration setup. The configuration backup will only back up configuration files that are not generated by the FAST Search Server 2010 for SharePoint installer. Because the backup set is incomplete, it must be installed over an existing FAST Search Server 2010 for SharePoint deployment.
The configuration backup includes general configuration files and the FAST Search Server 2010 for SharePoint administration database. The configuration backup is not deployment-aware, and can be restored to any system if you use the –action configmigrate parameter during restore.
Nota
You can make a configuration backup while FAST Search Server 2010 for SharePoint is operating without interrupting services. The backup is non-intrusive.
Nota
You should perform a restore on a running system. After the restore finishes, you will need a minimum amount of downtime to restart some services.
In this article:
Configuration backup
Configuration restore to the same deployment
Configuration restore to a different deployment
Potential problems with configuration restore
Configuration backup
The configuration backup will store the system configuration data. This includes schema data, relevance configuration, and other configuration files. Indexed documents are not included in this kind of backup. As a result, the configuration backup is faster and requires less storage space than a full backup. You do not have to shut down any services when you run a configuration backup.
To run a configuration backup, use the Windows PowerShell script backup.ps1, located in the bin directory of the FAST Search Server 2010 for SharePoint deployment:
.\backup.ps1 –action config –backuppath <UNC path of backup store>
Backup files are written to the folder that is specified by the -backuppath parameter.
Nota
The backed up FAST Search Server 2010 for SharePoint administration database is not written to this folder. The backup file for the FAST Search Server 2010 for SharePoint administration database will be in the installation folder for the SQL Server. The name of the SQL Server backup file depends on where the SQL Server is installed. The location of the file is written to the console during the backup operation so that it is easy to find the file. You should manually copy this file into the backup folder to maintain a complete file set for the configuration backup.
The script will verify that the destination folder does not exist before the backup starts. If you have already created a backup store, or if you want to overwrite an existing backup set, you must specify the option –force when you run the backup script.
Optional parameters that can be added to the backup.ps1 script:
force: Use this parameter to overwrite the backup directory.
Importante: If the backup procedure fails with the -force switch parameter set, the resulting backup cannot be restored. To avoid ending up with an unusable backup, either keep another copy of the backup before starting the backup procedure, or restart the failed backup procedure. passwordfile: Use this parameter to run a backup without entering the password at runtime. See Run scripts with a saved password for more information about this operation.
Configuration restore to the same deployment
This section describes how to do a configuration restore of the same system that uses the same server name and the same deployment file. If you migrate the configuration to a different system using a new server name or with a modified deployment file, follow the steps in Configuration restore to a different deployment.
Make sure that the FAST Search Server 2010 for SharePoint administration database backup file is present on the SQL Server. This file is not part of the configuration backup set. You must copy it manually (see Configuration backup). If the SQL Server installation that was used in the backed up system has not been reinstalled, the backup file should be in the SQL Server installation directory. More information about the SQL Server backup process is written to the file, SQLServerMetaData.txt. This file is stored in the specified backup store. The lines that contain BackupDirectory
and NetName
display the path and host name for the SQL Server. There can be several SQL Server backup files in the SQL Server directory. Check the exact name of your SQL Server backup file in dbbackup.txt, inside the configuration backup directory. If you get any errors from the SQL Server during the restore, verify that the installed version of the database matches the VersionString
that is stored in the SQLServerMetaData.txt file. The SQL Server versions must be identical for the SQL restore to succeed.
Nota
The restore process must be performed on a running system. You do not have to stop any services in the FAST Search Server 2010 for SharePoint deployment.
Use the script restore.ps1 to run the configuration restore. The script is located in the bin directory of your FAST Search Server 2010 for SharePoint deployment.
Run a configuration restore to the same deployment
Open a Windows PowerShell shell.
Run the following command:
.\restore.ps1 –action config –backuppath <UNC path of backup store>
The action parameter indicates that this is a configuration restore.
The backuppath should point to the directory where the backup is stored. Use UNC encoded paths, even if the backup is located on the same server that you are restoring to.
When the configuration restore script is complete, you must restart the FAST Search Server 2010 for SharePoint service on all servers. Run the following commands on all servers:
Stop-Service FASTSearchService
Start-Service FASTSearchService
Configuration restore to a different deployment
If you want to migrate the configuration data to a system that differs from the one that you made the backup of, you must make sure that the configuration linked to the server name is not overwritten in your deployment during the restore process. Use the action parameter configmigrate if you are restoring a configuration to a system on different servers, or where the deployment file is different, than the servers that were backed up. The content of the directory <FASTSearchFolder>\etc\config_data\deployment on the restored system will not be modified. The server-specific configuration from installation is not overwritten during the restore process when you use the configmigrate parameter.
Run a configuration restore to a different deployment
Open a Windows PowerShell shell.
Run the following command:
.\restore.ps1 –action configmigrate –backuppath <UNC path of backup store>
The configmigrate action parameter indicates that this is a migration of the configuration, and not a standard configuration restore.
The backuppath should point to the directory where the backup is stored. Use UNC encoded paths.
When the migration script is complete, you must restart the FAST Search Server 2010 for SharePoint service on all servers. Run the following commands on all servers:
Stop-Service FASTSearchService
Start-Service FASTSearchService
Potential problems with configuration restore
If the backed up system and the restored system have different sets of managed properties, the content will not be searchable after a restore. If you encounter this problem, you must re-feed all data. To avoid this problem, make sure that you run a new configuration backup when the set of managed properties changes, and only restore the latest configuration backup.
Since you always restore to a running system, you may experience the rare situation where the SharePoint Relevancy (SPREL) configuration fails due to a running relevancy processing. If you receive the following error message: "Can't change FDM config when FDM is running
", re-try running the restore script later.
Vedere anche
Concetti
Full backup and restore (FAST Search Server 2010 for SharePoint)(informazioni in lingua inglese)
Altre risorse
Eseguire il backup dei componenti di ricerca (SharePoint Server 2010)
Cronologia delle modifiche
Data | Descrizione | Motivo |
---|---|---|
10 giugno 2010 |
2010/06/07 |
Aggiornamento contenuto |
12 maggio 2010 |
Pubblicazione iniziale |