立即与支持人员聊天
与支持团队交流

NetVault Plug-in for SQL Server 11.0 - User Guide

Introducing Dell™ 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

Differential Partial Database Backup for Online VDI

SQL Server® versions: 2005 and later

Examples of VDI online backup sequences

Full Database backups only: When requirements guarantee data protection up to the previous day, performing Full Database backups nightly should be sufficient when one or more of the following conditions exist:
Full Database and Differential Database backups: When requirements guarantee data protection up to the previous day and backups must be completed quickly, Full Database backups coupled with Differential Database backups is a valid strategy. For example, Full Database backups are performed every Sunday night at 11:00 P.M. while Differential Database backups are performed Monday through Saturday at 11:00 P.M. Each Differential Database backup includes all the changes since the last Full Database backup, which is known as the differential base.
Full File and Filegroup backups and Partial Database backups: When a Simple Recovery Model database includes secondary read-only filegroups, a valid strategy includes Partial Database backups for the primary and read/write filegroups and Full File and Filegroup backups for read-only secondary filegroups. This strategy ensures recoverability of the entire database without requiring backup of the read-only filegroups every time the read/write filegroups are backed up.
Full File and Filegroup backups and Partial Database and Differential Partial Database backups: When requirements guarantee data protection for read/write data up to the previous day and backups must be completed quickly, Partial Database backups coupled with Differential Database Backups for the read/write data and Full File and Filegroup backup for the secondary read-only filegroups is a valid strategy.

Full recovery model backup sequences

Full Database and Incremental Transaction Log backups: When requirements mandate PIT data protection, performing Full Database backup nightly plus Incremental Transaction Log backups every four to eight hours should be sufficient when one or more of the following conditions exist:
Full Database and Differential Database and Incremental Transaction Log backups: When requirements mandate PIT data protection and restores of the complete database must be completed quickly, Full Database plus Differential Database plus Incremental Transaction Log backups is an ideal strategy.
Full File and Filegroup and Differential File and Filegroup and Incremental Transaction Log backups: When requirements mandate PIT data protection and restores must be completed quickly, Full File and Filegroup plus Differential File and Filegroup plus Incremental Transaction Log backups is an ideal strategy. This strategy lets you restore a complete database or the files or filegroups that are damaged. By being able to restore only what is needed, restores are faster and data loss is minimized.

Defining a VSS backup strategy and reviewing types

Full Database backup: Full Database backups are supported by:
SQL Server® versions: 2005 and later
Differential Database backup: Differential Database backups are supported by:
SQL Server® versions: 2005 and later
Copy-Only backup: Copy-Only backups are supported by:
SQL Server® versions: 2005 and later
相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级