Chatee ahora con Soporte
Chat con el soporte

NetVault Plug-in for SQL Server 12.0 - User Guide

Introducing NetVault Backup Plug-in for SQL Server Planning your SQL Server deployment Installing and removing the plug-in Configuring the plug-in Backing up data
Defining a backup strategy Understanding snapshot-based backups Reviewing the compression features Performing Online VDI backups Performing VSS backups in SQL Server Example of creating a full VDI backup of an AlwaysOn Availability Group
Restoring data Troubleshooting

Full File and Filegroup backup for Online VDI

Full File and Filegroup backups are supported by:

•
SQL Server versions: All
•
Recovery models: All

A Full File and Filegroup backup backs up all the data in one or more files or filegroups. A complete set of Full File and Filegroup backups is equivalent to a Full Database backup.

Full File and Filegroup backups have the following advantages over Full Database backups:

•
With a Full File and Filegroup backup, you can back up and restore the files in a database individually. This process can speed up the recovery process as you can restore only damaged files without restoring the rest of the database.
•
Full File and Filegroup backups increase the flexibility in dealing with large databases that contain data with varying update characteristics. For example, consider the following recommendations:
•
Back up frequently modified data often.
•
Back up infrequently modified data less often.
•
Back up read-only data once.

The primary disadvantage of Full File and Filegroup backups is the risk that a media failure can render an entire database unrecoverable if a damaged file lacks a backup.

By default, file backups contain enough log records to roll forward the file to the end of the backup operation. Under Simple Recovery Model, the Full File and Filegroup backups are restricted to read-only secondary filegroups. You can create a file backup of a read/write filegroup, but before you can restore the read/write file backup, you must set the filegroup to read-only and take a differential read-only file backup.

Differential File and Filegroup backup for Online VDI

Differential File and Filegroup backups are supported by:

•
SQL Server versions: All
•
Recovery models: All

A Differential File and Filegroup backup captures only the data changed since the last file backup. These backups are fast because the Database Engine tracks changes made since the file was last backed up, eliminating the need to scan the file.

For Simple Recovery Model databases, Differential File backups provide a faster, space-saving way to create backups of current files. Differential File backups also reduce recovery time for Full Recovery Model databases by reducing the number of transaction logs that must be restored.

Differential File and Filegroup backups should be considered when:

•
You are backing up some files much less frequently than others.
•
Your files are large and the data is updated infrequently, or the same data is updated repeatedly.

Partial Database backup for Online VDI

Partial Database backups are supported by:

•
SQL Server versions: 2008 and later
•
Recovery models: Simple

Designed to create flexibility for Simple Recovery Model databases, a Partial Database backup is similar to a Full Database backup except that a Partial does not contain all the database’s filegroups. A Partial Database backup contains all the data in the primary filegroup and every read/write filegroup. Optionally, specified read-only files can also be included. However, a partial backup of a read-only database contains only the primary filegroup.

A Partial Database backup is useful when a database contains read-only files that you do not need to include in every database backup. A Partial Database backup can also be used as a basis for a piecemeal restore scenario, which the plug-in does not support.

Differential Partial Database Backup for Online VDI

Differential Partial Database backups are supported by:

•
SQL Server versions: 2008 and later
•
Recovery Models: Simple

Used only with Partial Database backups, a Differential Partial backup contains only those extents changed in the primary filegroup and read/write filegroups since the previous partial backup. If only some of the data captured by a partial backup has changed, using a Differential Partial backup lets you back up frequently without the overhead of Full Database backups.

For more information on the effect of adding, deleting, or modifying Filegroups on Partial Differential backups, see Differential Partial Backups in the SQL Server Books Online.

Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación