Full backup and restore (FAST Search Server 2010 for SharePoint)(informazioni in lingua inglese)

Aggiornato: 5 agosto 2010

A full backup makes a complete backup of the FAST Search Server 2010 for SharePoint installation directory and generates a backup of the FAST Search Server 2010 for SharePoint administration database. For each server, it stores a copy of the file system except for the executable binaries and DLLs. A full backup is associated with the deployment it was generated from. A backed up set cannot be restored on other servers unless those servers are duplicates of the servers that the backup was taken from.

Full backups can only be generated when the system is in a persistent state. This means that all FAST Search Server 2010 for SharePoint components that modify file contents must be stopped before the backup is generated. It is also a good idea to let the system settle for several minutes after it is suspended before backing up the system.

A few components can stay up so that the system can serve search requests while you perform a full backup. However, when you perform a full restore, all parts of the FAST Search Server 2010 for SharePoint system must be shut down. This includes the FAST Search Server 2010 for SharePoint services.

The full backup and restore uses Robocopy in incremental mode to transfer data between the target system and the backup store. If you have an older backup that you are overwriting, Robocopy will only replace the modified files, which saves bandwidth and time. For this reason, you should use the same backup store for later backups.

Importante:
Always make sure that you have a full copy of the backup store before you run another backup to the same backup store. If the backup procedure fails while you try to run the new backup, the backup store might be corrupted.

A full backup and restore must be associated with a Microsoft SharePoint Server farm backup. Otherwise, there is a risk of duplicates in the index or of indexed content not being searchable. The searchable index and the state of the Content Search Service Application (Content SSA) must be synchronized to avoid duplicates and search problems. Also, People Search is not covered by FAST Search Server 2010 for SharePoint backup and restore, but is instead covered by the Microsoft SharePoint Farm backup and restore. See Backup e ripristino (SharePoint Server 2010) for detailed information about a Microsoft SharePoint Server farm backup.

The restore operation must be performed on an existing FAST Search Server 2010 for SharePoint installation. This means that after a system failure, you must reinstall FAST Search Server 2010 for SharePoint before you perform a restore.

In this article:

• Full backup

• Full backup excluding the searchable index

• Full restore

• Restore a certificate

• Third-party data backup and restore

• Troubleshooting: Windows PowerShell not found after running the restore.ps1 script

Full backup

Because the backup file for the FAST Search Server 2010 for SharePoint administration database is not part of the file set in a full backup, you should move a copy of the SQL backup to the directory where your full backup is stored. More information about the SQL Server backup is written to the files, dbbackup.txt and SQLServerMetaData.txt.

The script will print an error message if the backuppath already exists. If you want to overwrite an existing backup, run the script with the –force parameter set.

When there are multiple servers in the FAST Search Server 2010 for SharePoint deployment, and multiple backup stores are specified in the –backuppath parameter, the system will search the contents of all the backup stores to determine whether there is a backup for all servers on the backup stores. If so, and if the –force parameter is specified, the scripts will update the existing backups. Otherwise the script will write an error message to the console.

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 you start the backup procedure, or restart the failed backup procedure.

Note that some selected services in FAST Search Server 2010 for SharePoint must be stopped before you perform the backup. Also, you must pause the SharePoint Server Content SSA before you run the backup. The system can still serve search requests while you perform the backup.

Perform a full backup

1. On the main SharePoint Server, run the following commands:

   $ssa = Get-SPenterpriseSearchServiceApplication "<FAST Search Content SSA>"

   $ssa.Pause()

2. You can now perform a backup of the SharePoint Server farm. (See Eseguire il backup di una (SharePoint Server 2010) for more information.) Use the SharePoint Server Central Administration or a Windows PowerShell cmdlet, as shown in the following example:

   Backup-SPFarm -BackupMethod full –Directory <path of a SharePoint backup directory>

3. On the FAST Search Server 2010 for SharePoint server, suspend services before you run the backup script. To do this, run the following commands. (You can do this in parallel with step 2.)

   .\suspend.ps1

   .\backup.ps1 –action full –backuppath <path of backup store(s)>

   .\resume.ps1

   Nota

   The suspend.ps1 command suspends the FAST Search Server 2010 for SharePoint feeding and indexing chain, but does not suspend the query processing and query matching components.

4. On the SharePoint Server, resume the SSA by running the following command:

   $ssa.Resume()

Full backup excluding the searchable index

This procedure has the same effect as a full backup except that the content of the <FASTSearchFolder>\data\data_index directory, which contains the searchable index, is not backed up. This data can be reconstructed using the backed up FIXML. This method saves time and space during backup because less data is transferred. The disadvantage is that it takes longer to get a restored system up and running because the searchable index must be rebuilt by the indexer. Note that some selected services in FAST Search Server 2010 for SharePoint must be stopped before you perform the backup. The system can still serve search requests while you perform the backup.

Perform a full backup excluding searchable index

1. On the SharePoint Server, pause the Search Service Application by running the following commands:

   $ssa = Get-SPenterpriseSearchServiceApplication "<FAST Search Content SSA>"

   $ssa.Pause()

2. You can now perform a backup of the SharePoint Server farm. See Eseguire il backup di una (SharePoint Server 2010) for more information.) Use the SharePoint Server Central Administration or a Windows PowerShell cmdlet, as shown in the following example:

   Backup-SPFarm -BackupMethod full –Directory <path of a SharePoint backup directory>

3. On the FAST Search Server 2010 for SharePoint server, suspend services before you run the backup script. To do this, run the following commands. (You can do this in parallel with step 2.)

   .\suspend.ps1

   .\backup.ps1 –action full –backuppath <path of backup store(s)> -excludeindex

   .\resume.ps1

   Nota

   The suspend.ps1 command suspends the FAST Search Server 2010 for SharePoint feeding and indexing chain, but does not suspend the query processing and query matching components.

4. On the SharePoint Server, resume the SSA by running the following command:

   $ssa.Resume()

Full restore

This procedure restores a previous backup to an existing system. The system must be identical to the system that was backed up. In particular:

• the number of servers must be the same

• the roles that are assigned by the installer to the servers must be the same

• the names of the installed servers must be the same

A full restore sets the system back to the state it was in at backup time. A full restore can also be used to recover and re-deploy the system after a disaster.

Perform a full restore

1. On the main SharePoint Server, run the following command:

   $extractorJob = Get-SPTimerJob | where {$_.Name.StartsWith("FAST Search Server 2010 for SharePoint Alternate Access Mapping Extractor Job")}

   Disable-SPTimerJob $extractorJob

2. Perform a restore on the SharePoint Server farm installation. Use the SharePoint Server Central Administration or a Windows PowerShell cmdlet, as shown in the following example. (See Ripristinare una farm (SharePoint Server 2010) for more information.) If you use the Central Administration, the RestoreThreads must be set to 1 before you run the restore.

   Restore-SPFarm -RestoreMethod overwrite –Directory <path of backup directory> -RestoreThreads 1

3. On the main SharePoint Server, run the following commands:

   $extractorJob = Get-SPTimerJob | where {$_.Name.StartsWith("FAST Search Server 2010 for SharePoint Alternate Access Mapping Extractor Job")}

   Enable-SPTimerJob $extractorJob

   $ssa = Get-SPenterpriseSearchServiceApplication "<FAST Search Content SSA>"

   $ssa.Pause()

4. Stop FAST Search Server 2010 for SharePoint services by running the following command on all FAST Search Server 2010 for SharePoint servers:

   Stop-Service FASTSearchService

   Stop-Service FASTSearchMonitoring

5. When all stop commands have finished, run the restore script on the FAST Search Server 2010 for SharePoint administration server:

   .\restore.ps1 –action full –backuppath <path of backup store(s)>

6. Start FASTSearchService and resume services that were suspended during backup on all FAST Search Server 2010 for SharePoint servers:

   Start-Service FASTSearchService

   .\resume.ps1

7. On the SharePoint Server, resume the Content SSA.

   $ssa.ForceResume($ssa.IsPaused())

If you restored to a reinstalled FAST Search Server 2010 for SharePoint or SharePoint Server system, you must now restore the certificates between SharePoint Server and FAST Search Server 2010 for SharePoint as described in Restore a certificate.

Restore a certificate

When you restore a FAST Search Server 2010 for SharePoint system, the installation will refer to the certificates that were installed on the backed up FAST Search Server 2010 for SharePoint installation. If you have reinstalled FAST Search Server 2010 for SharePoint, a new certificate will be installed on the server and the old certificates might be missing. The FAST Search Server 2010 for SharePoint full backup does not handle certificates. You must manually replace the certificates.

Depending on whether the backed up FAST Search Server 2010 for SharePoint installation used the default FASTSearchCert or a certificate signed by a certification authority, follow the steps in one of the following sections:

• Restore certificate configuration when the backed up installation used the self-signed FASTSearchCert certificate

• Restore certificate configuration when the backed up installation used certificates signed by certification authority

Restore certificate configuration when the backed up installation used the self-signed FASTSearchCert certificate

To replace all the certificates in the system, follow this procedure:

1. On all FAST Search Server 2010 for SharePoint servers, stop the two FAST Search Server 2010 for SharePoint services called FAST Search for SharePoint and FAST Search for SharePoint Monitoring, by running the following command:

   Stop-Service FASTSearchService,FASTSearchMonitoring

2. Verify that there are no FAST Search Server 2010 for SharePoint certificates on the SharePoint servers from the previous installation as follows:

   1. Run the Microsoft Management Console (mmc.exe).

   2. Use the Add or Remove Snap-ins function to add the Certificates snap-in for the account on the Local Computer.

   3. Use the Find certificates function to search for a certificate that contains the word FAST. If such a certificate exists, remove it on all SharePoint servers by right-clicking and selecting Delete.

3. Next, any existing SharePoint certificates must be removed from the FAST Search Server 2010 for SharePoint servers. Repeat step 2 on all FAST Search Server 2010 for SharePoint servers, and search for the word sharepoint when you search for a certificate.

4. You can now set up the new certificates. You must set up the certificate on the FAST Search Server 2010 for SharePoint administration server first. On the administration server, from the scripts folder <FASTSearchFolder>\installer\scripts, run the following script:

   .\replacedefaultcertificate.ps1 -generateNewCertificate $true

5. Start the service FAST Search for SharePoint on the FAST Search Server 2010 for SharePoint administration server by using the following command:

   Start-Service FASTSearchService

6. On the remaining FAST Search Server 2010 for SharePoint, run

   .\replacedefaultcertificate.ps1 -generateNewCertificate $true

   Use the same password for the certificate that you used on the administration server.

7. Start the FAST Search for SharePoint service on these servers by using this command:

   Start-Service FASTSearchService

8. Copy the SecureFASTSearchConnector.ps1 script from <FASTSearchFolder>\installer\scripts to the SharePoint Server.

9. Copy the recently created FAST Search Server 2010 for SharePoint certificate from <FASTSearchFolder>\data\data_security\cert\FASTSearchCert.pfx to the SharePoint Server.

10. On the SharePoint Server, run the SecureFASTSearchConnector.ps1 script that you previously copied, by running the following command:

    SecureFASTSearchConnector.ps1 -certPath <path of FASTSearchCert.pfx> -ssaName "<FAST Search Content SSA>" -username "<domain\username>"

    Make sure that the ssaName matches the SSA that you set up in the SharePoint Server installation.

11. Export the SharePoint Server certificate (not to be confused with the previous FAST Search Server 2010 for SharePoint certificate). In a SharePoint Server shell, run the following commands:

    $stsCert = (GetSPSecurityTokenServiceConfig).LocalLoginProvider.SigningCertificate

    $stsCert.Export("cert") | Set-content -Encoding byte MOSS_STS.cer

    Copy the resulting MOSS_STS.cer file to all FAST Search Server 2010 for SharePoint servers.

12. On all FAST Search Server 2010 for SharePoint servers, open a FAST Search Server 2010 for SharePoint administration Windows PowerShell console and go to the <FASTSearchFolder>\installer\scripts directory.

    Run the following command:

    .\installSTSCertificateForClaims.ps1 -certPath '<path of MOSS certificate...\MOSS_STS.cer>'

13. Restart FAST Search Server 2010 for SharePoint and SharePoint servers to make sure that the new certificates are picked up.

You now have a SharePoint Server and FAST Search Server 2010 for SharePoint system with the correct certificates.

Restore certificate configuration when the backed up installation used certificates signed by certification authority

1. Follow the steps in Replace the self-signed certificate with a certificate signed by a certification authority (CA) in Manage certificates (FAST Search Server 2010 for SharePoint)(informazioni in lingua inglese) to replace the self-signed FASTSearchCert certificate.

2. Follow the steps in Create a FAST Search Center site (FAST Search Server 2010 for SharePoint)(informazioni in lingua inglese) to reinstall the SharePoint claims certificate on each FAST Search Server 2010 for SharePoint query server.

Third-party data backup and restore

You can also use a third-party solution to back up and restore a FAST Search Server 2010 for SharePoint system.

When you restore the system using a third-party restore solution, make sure that both SharePoint Server and FAST Search Server 2010 for SharePoint are shut down correctly before you start the process.

1. Suspend the SharePoint Server system by running these commands in a Windows PowerShell on the SharePoint Server:

   $ssa = Get-SPenterpriseSearchServiceApplication "<FAST Search Content SSA>"

   $ssa.Pause()

2. Switch to the FAST Search Server 2010 for SharePoint administration server and suspend the FAST Search Server 2010 for SharePoint system by running:

   .\suspend.ps1

   Nota

   The suspend.ps1 command suspends the FAST Search Server 2010 for SharePoint feeding and indexing chain, but does not suspend the query processing and query matching components.

3. Run the third-party backup of both SharePoint Server and FAST Search Server 2010 for SharePoint.

4. After the backup is complete, resume the FAST Search Server 2010 for SharePoint system by running the resume script on the administration server:

   .\resume.ps1

5. Resume the SharePoint Server system by running the following command on the SharePoint Server:

   $ssa.Resume()

Troubleshooting: Windows PowerShell not found after running the restore.ps1 script

The restore.ps1 script removes the Microsoft.FASTSearch.Powershell snap-in from your current session. You can either start a new Microsoft FAST Search Server 2010 per shell di SharePoint or add the snap-in explicitly.

• In Windows PowerShell, add the Microsoft FAST Search Server 2010 for SharePoint snap-in:

  Add-PSSnapin Microsoft.FASTSearch.PowerShell

Vedere anche

Concetti

Configuration 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)
Ripristinare i componenti di ricerca (SharePoint Server 2010)

Cronologia delle modifiche