Previous Topic: Backup Options Dialog in SharePoint Server 2010/2013Next Topic: Perform a Database-Level Backup in SharePoint Server 2010/2013


Agent Backup Options

The backup options dialog allows you to choose the following methods of database protection:

Database Agent

Uses the Agent to back up your SharePoint data.

Hardware Snapshot

Backs up your SharePoint data using a VSS hardware snapshot. In order to use this option, you must install the Arcserve Backup Enterprise Module. For more information, see the Arcserve Backup VSS Guide.

Database Complete

Use full backups to back up your SharePoint Server database. You can also use full backups to back up all your SharePoint Server non-database data (such as search indexes).

Note: For non-database data, the agent supports only complete backups.

Database Differential

Backs up database data that has changed since the last complete backup. For example, if you ran a complete backup of your database on Sunday night, you can run a differential backup on Monday night to back up only the data that changed on Monday.

Files and FileGroups

Backs up selected files in a database. Use this option to back up a file or FileGroup when the database size and performance requirements make it impractical to perform a full database backup.

Files and FileGroups; Differential

Backs up database data changed in selected files since the last file and FileGroup backup. Differential file backups reduce recovery time by reducing the number of transactions from the Transaction log that must be restored.

Transaction Log

Backs up the Transaction log. Transaction log backups provide the following options:

The following Database Consistency Checks are also supported:

Before backup

Checks consistency before the database backup is performed.

After backup

Checks consistency after the database backup is performed.

Continue with backup if DBCC fails

Performs a database backup even if the consistency check fails.

Check the physical consistency of the database

Detects torn pages and common hardware failures, the integrity of the physical structure of the page and record headers, and the consistency between the page's object and Index IDs.

Do not check indexes

Checks the database for consistency without checking indexes for user-defined tables.