지금 지원 담당자와 채팅
지원 담당자와 채팅

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

Full Database backup for Online VDI

Full Database backups are supported by:

•
SQL Server® versions: All
•
Recovery models: All

A Full Database backup is a backup of the entire database. It also includes part of the transaction log, which enables recovery of the database to the point at which the backup was completed.

Full Database backups consume more space and time per backup and are typically supplemented by differential backups, which are created more frequently. With Full Database backups, you can re-create an entire database in one step by restoring the database.

Differential Database backup for Online VDI

Differential Database backups are supported by:

•
SQL Server® versions: All
•
Recovery models: All

With a Differential Database, back up only the data that has changed since the last Full Database backup is backed up. Differential backups are smaller and faster to create than the full backups.

A Differential Database backup is useful if some of the database’s tables are modified more frequently than others. In this case, Differential Database backups allow you to back up frequently without the overhead of Full Database backups.

Copy-Only backup for Online VDI

Copy-Only backups are supported by:

•
SQL Server® versions: 2005 and later
•
Recovery models: All

Copy-Only backups are independent of the normal sequence of backups. A Copy-Only backup cannot serve as the base backup for a series of differential backups as a Full Backup can. Performing a Copy-Only backup does not affect what is backed up by the next differential backup. Copy-Only backups are ideal for situations that require special purposes, such as creating test environments or standby databases.

Incremental Transaction Log backup for Online VDI

Incremental Transaction Log backups are supported by:

•
SQL Server® versions: All
•
Recovery Models: Full or Bulk-Logged Only

SQL Server Transaction Logs are essential to data recovery and must be backed up regularly. With Transaction Log backups, you can recover the database to a point-of-failure or specific point.

An Incremental Transaction Log backup captures all the transaction logs including those logs generated since the last Full Database/File or Filegroup, Differential Database/File or Filegroup, or Incremental Transaction Log backup. An Incremental Transaction Log backup should not be performed in the following conditions:

•
Until a Full Database or Full File and Filegroup backup has been created because the transaction log contains changes made to the database after the last backup was created.
•
After the transaction log has been manually truncated, until a Full Database or Differential Database backup has been performed. Microsoft strongly recommends against manually truncating transaction logs.
관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택