Back up a content database (Search Server 2010)
Applies to: Search Server 2010
Topic Last Modified: 2011-08-05
Microsoft Search Server 2010 content databases can grow to be very large. Therefore, you might want to back them up separately from farm backups. Regularly backing up content databases reduces data losses that might occur from hardware failures, power outages, or other problems. It is a simple process and helps to ensure that all the data is available for recovery, if that is required. You can only back up one content database at a time.
This topic describes how to back up a single content database.
Procedures in this task:
To back up a content database by using Windows PowerShell
To back up a content database by using Central Administration
To back up a content database by using SQL Server tools
Task requirements
Before you begin, you must create a folder on the local computer or the network in which to store the backups. For better performance, we recommend that you back up to the local computer and then move the backup files to a network folder.
Use Windows PowerShell to back up a content database
You can use Windows PowerShell to back up a content database manually or as part of a script that can be run at scheduled intervals.
To back up a content database by using Windows PowerShell
Verify that you meet the following requirements: See Add-SPShellAdmin.
In the SharePoint 2010 Management Shell, at the Windows PowerShell command prompt, type the following command:
Backup-SPFarm -Directory <BackupFolder> -BackupMethod Full -Item <ContentDatabaseName> [-Verbose]Where:
<BackupFolder> is the path of the backup folder.
<ContentDatabaseName> is the name of the database that you want to back up. To display the name of the content database, type the following command at the Windows PowerShell command prompt:
Backup-SPFarm -ShowTree.
To view the progress of the backup operation, use the Verbose parameter.
Note
If you are backing up the content database for the first time, you must use the Full option. You must perform a full backup before you can perform a differential backup.
For more information, see Backup-SPFarm.
If you do not use the Verbose parameter, the Command Prompt window displays no message if the operation succeeds. If the job does not finish successfully, the Command Prompt window displays an error message such as the following.
Backup-SPFarm: The operation failed. For more information, see the error log that is located in the backup directory. At line: <line> char:<column>. + <cmdlet> <<<< <location of error>
If there are errors or warnings, or if the backup does not complete successfully, review the Spbackup.log file in the backup folder.
Use Central Administration to back up a content database
You can use Central Administration to back up a content database.
To back up a content database by using Central Administration
Verify that the user account that is performing this procedure is a member of the Farm Administrators group.
In Central Administration, on the Home page, in the Backup and Restore section, click Perform a backup.
On the Perform a Backup — Step 1 of 2: Select Component to Back Up page, select the content database that you want to back up from the list of components, and then click Next.
Note
Not all content databases can be selected in the list. If a database is not selectable, you must use Windows PowerShell to back up the content database.
On the Start Backup — Step 2 of 2: Select Backup Options page, in the Backup Type section, select either Full or Differential.
Note
If you are backing up the content database for the first time, you must use the Full option. You must perform a full backup before you can perform a differential backup.
In the Backup File Location section, type the Universal Naming Convention (UNC) path of the backup folder, and then click Start Backup.
You can view the general status of all backup jobs at the top of the Backup and Restore Job Status page in the Readiness section. You can view the status of the current backup job in the lower part of the page in the Backup section. The status page updates every 30 seconds automatically. You can manually update the status details by clicking Refresh. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the backup to start.
If you receive any errors, review the Failure Message column of the Backup and Restore Job Status page. You can also find more details in the Spbackup.log file at the UNC path that you specified in step 4.
Use SQL Server tools to back up a content database
You can use SQL Server tools to back up a content database.
To back up a content database by using SQL Server tools
Verify that the user account that is performing this procedure is a member of the SQL Server db_backupoperator fixed database role on the database server where each database is stored.
Open SQL Server Management Studio and connect to the database server.
In Object Explorer, expand Databases.
Right-click the database that you want to back up, point to Tasks, and then click Back Up.
In the Back Up Database dialog box, in the Source area, select the kind of backup that you want to perform from the Backup type list. For more information about which backup type to use, see Overview of Recovery Models (https://go.microsoft.com/fwlink/p/?LinkId=114396) in SQL Server Books Online.
In the Backup component area, click Database.
Either use the default name provided or specify a name for the backup set in the Name text box.
Specify the expiration date for the backup set. This date determines how long, or when, the backup set can be overwritten by any later backups that have the same name. By default, the backup set is set to never expire (0 days).
In the Destination area, specify where you want to store the backup.
Click OK to back up the database.
Repeat steps 1-9 for each content database that you want to back up.