Chat now with support
지원 담당자와 채팅

NetVault Backup Plug-in for SQL Server 12.2 - 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 on Windows
Restoring data Using the CLI with the plug-in Troubleshooting

Incremental Transaction Log backup for Online VDI

Incremental Transaction Log backups are supported by:

SQL Server versions: Windows - 2008 and later; Linux - 2017 and later
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:

Tail-Log backup for Online VDI

Tail-Log backups are supported by:

SQL Server versions: Windows - 2008 and later; Linux - 2017 and later

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:

Full File and Filegroup backup for Online VDI

Full File and Filegroup backups are supported by:

SQL Server versions: Windows - 2008 and later

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:

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: Windows - 2008 and later

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:

관련 문서