Library Table of Contents Index Previous Page (Alt-p) Next Page (Alt-n) Comments

How SnapManager Backup works

SnapManager Backup uses Snapshot copy functionality to create online, read-only copies of the SQL Server data you specify.

Note
Databases that cannot be backed up by SnapManager are listed in the upper left panel of the Backup and Verification tab or the Backup Wizard with the label Invalid next to the LUN drive letter.

See the following topics for more information:

What SnapManager Backup does  Top

SnapManager for SQL Server performs the following tasks when creating a backup:

  1. Checks the SnapManager license
  2. Renames the most recent SnapInfo directory (if necessary)
  3. Renames the most recent Snapshot copy (if necessary)
  4. Creates a new directory in the SnapInfo directory for this backup

    Note
    During the backup process, SnapManager collects backup metadata that is automatically archived to the SnapInfo directory.

  5. Creates a Snapshot copy of the LUNs containing the database files (if specified)
  6. Backs up transaction logs (if specified)
  7. Creates a Snapshot copy of the LUN that contains the SnapInfo directory
  8. Verifies the databases in the Snapshot copy of the LUN (if specified)
  9. Deletes the oldest backup sets (if specified)
  10. Deletes the oldest Snapshot copy of the LUN that contains the SnapInfo directory

SnapManager Backup requirements and limitations  Top

Be aware of the requirements and limitations of SnapManager Backup:

Attention
In an SQL Server 2000 or 2005 environment, you should perform backups using only the SnapManager application. Making Snapshot copies of the storage system console for backup using SnapManager is not supported and results in an inconsistent Snapshot copy image of online databases. However, you can use SnapDrive to make Snapshot copies of SQL Server databases, although you cannot restore these Snapshot copies using SnapManager.

Library Table of Contents Index Previous Page (Alt-p) Next Page (Alt-n) Comments