Plug‑in for SQL Server provides the following types of VSS backups:
• |
Full Database backup: Full Database backups are supported by: |
• |
SQL Server versions: Windows - 2008 and later |
• |
Recovery models: All |
• |
Differential Database backup: Differential Database backups are supported by: |
• |
SQL Server versions: Windows - 2008 and later |
• |
Recovery model: All |
IMPORTANT: If a failover occurs in an Active/Passive Failover Cluster and your VSS-based backup strategy includes Differential Database backups, perform a Full Database backup of the modified configuration as soon as possible. When the plug-in detects that a failover occurred and a different node holds the active role, the plug-in automatically runs a full backup for the next scheduled backup. However, if you must perform a restore to the new active node before a new full backup is run, database changes that occurred between the last full backup and the new full backup might be lost. |
• |
Copy-Only backup: Copy-Only backups are supported by: |
• |
SQL Server versions: Windows - 2008 and later |
• |
Recovery models: All |
• |
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. |
• |
Copy-Only backups: When requirements demand that a backup be created without interfering with regular scheduled backup sequences, Copy-Only backups is a valid strategy. Often times, you must create a full backup outside of the regular backup schedule, such as when refreshing your test databases. This process could potentially interfere with the regular backup schedule and throw off subsequent differential backups. The Copy-Only backup allows administrators to run non-regular Full Database backups at any time without interfering with scheduled backups. |
To create and use persistent snapshots, the data that you want to back up must reside on NetVault Backup-supported disk arrays. If you attempt to create persistent snapshots with data residing on an unsupported disk array, or with data residing in local drives (for which snapshots are taken using the Microsoft Software VSS Provider), taking the required hardware snapshots fails, and the plug-in defaults to using software snapshots. When taking software snapshots the data is only backed up to storage (even if the option Backup Files to Storage is not selected), and non-persistent snapshots are created.
For more information about NetVault Backup-supported OS versions and disk arrays, see the Quest NetVault Backup Compatibility Guide.
The system databases that you must always back up include msdb, master, and model. The master and msdb databases have a Simple Recovery Model while the model database has a Full Recovery Model. For replicated databases, you should also back up the distribution database.
• |
master: The master database records system-level information for a SQL Server system. For the master database, SQL Server supports only Full Database backups. Quest recommends that you schedule routine Full Database backups of master. |
• |
msdb and model: SQL Server uses the msdb database to store data. SQL Server uses the model database as a template when you create a user database. Back up the model and msdb databases whenever they are updated. You can back up the model and msdb databases in the same way that you back up user databases. Quest recommends that you create only Full Database backups of the model database. Because it is small and rarely changes, backing up the log is not required. |
For more information, see Backing Up and Restoring System Databases in SQL Server Books Online.
© ALL RIGHTS RESERVED. Conditions d’utilisation Confidentialité Cookie Preference Center