Chat now with support
Chat mit Support

NetVault Plug-in for SQL Server 11.4.5 - User Guide

Introducing Quest® 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 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

Tail-Log backup for Online VDI

Tail-Log backups are supported by:

•
SQL Server® versions: 2005 and later
•
Recovery models: Full Only

A Tail-Log backup captures the transaction logs that have not yet been backed up and is the last backup restored in a restore sequence. SQL Server requires you to back up the tail of the log before restoring a database that is attached to the SQL Server Instance. Therefore, a Tail-Log backup is the first step in most restore sequences.

A Tail-Log differs from an Incremental Transaction Log in the following ways:

•
You can try to run a Tail-Log backup even if the database does not start, for example if the database is damaged or is offline. If the database is damaged, a Tail-Log backup succeeds only if the log files are undamaged, the database is in a state that supports Tail-Log backups, and the database does not contain any bulk-logged changes.
•
A Tail-Log might contain incomplete metadata if the database is damaged because some of the metadata normally available for log backups may be unavailable in a Tail-Log backup. However, the captured log is complete and usable.

A Tail-Log's data might not be fully self-contained if the database is not online and undamaged at the time of the Tail-Log backup. Transactional data from a Tail-Log is always complete and usable, but if the Tail-Log backup is initiated while the database is damaged or offline, metadata might be only partially captured. If this issue occurs, a recovery from the Tail-Log leaves the “backupfilegroup” table missing some information about filegroups, and the “has_incomplete_metadata” column of the “backupset” table is set to 1.
 
* 
WARNING: Because Tail-Log backups place the databases in Offline Mode, only perform a Tail-Log backup if you are preparing to perform a restore and recovery. Tail-Log backups should not be used as a substitute for regular or unplanned Incremental Transaction Log backups.
•
If you are working with an AlwaysOn Availability Group, use SQL Server Management Studio to remove the primary and secondary databases from the group before completing a Tail-Log backup. After the databases are removed from the group, their status changes to Restoring, and they are owned by the SQL Server Instance assigned the Primary Role in the group. To complete the Tail-Log backup, select the databases under the SQL Server Instance.

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: 2005 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.

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen