Table of ContentsView in Frames

Migrating databases and configuring SnapManager for SQL Server instances

Before you can back up your databases using SnapManager, you need to run the SnapManager Configuration wizard for each SQL Server instance. You use the Configuration wizard to migrate databases to NetApp storage and to configure SnapManager for the SQL Server instances.

Before you begin

You must have shut down any applications that are accessing the databases that you want to migrate. Database migration fails if an application accesses a database.

About this task

Attention: SnapManager takes databases offline when it migrates them. SnapManager takes the entire SQL Server offline when it migrates the system databases.

You use the SnapManager Configuration wizard to select a verification server, migrate data files and log files to NetApp storage, map those files to their respective SnapInfo directories, and configure automatic event notification.

When migrating databases, SnapManager ensures that the files are placed in locations that meet SnapManager configuration requirements. If you use a separate tool to migrate databases, run the Configuration wizard to ensure that the files are in correct locations. Incorrectly located files can impair SnapManager operations.

Even if you create new databases directly on NetApp storage, you need to run the Configuration wizard to create a mapping between those databases and the SnapInfo directory.


  1. If the Configuration wizard is not open, click Configuration Wizard in the Actions menu.
    Screen shot: The Configuration Wizard icon in the Actions pane.
  2. On the Start page, click Next.
    This page includes an option to use a control file. A control file contains configuration details about an SQL Server instance. You might use this option at another time to export and then import a configuration. For information about using control files, see the SnapManager 7.1 for Microsoft SQL Server Administration Guide.
  3. On the Verification Settings page, define how SnapManager should verify backup copies:
    For this field... Do this...
    Verification Server For optimal performance, choose a remote verification server, which offloads work from the SQL production server.
    SQL Server Connection Choose an authentication method for SnapManager to connect to the SQL Server on the verification server during backup verification:
    Use Windows authentication
    SnapManager connects to the SQL Server using the Windows account under which SnapManager runs (the SnapManager service account). This is the most common method.
    Use SQL Server authentication
    SnapManager connects to the SQL Server using an account defined on the SQL Server. The account must have sysadmin server role privileges on the SQL Server instance.
    Access a mounted LUN in snapshot Keep the default option for mounting Snapshot copies to an empty NTFS directory.

    SnapManager mounts Snapshot copies to the verification server when it verifies backup copies. Using an empty NTFS directory is typically better than assigning drive letters because the verification server can run out of drive letters if there are more backup copies than available drive letters.

    For a Windows Failover Cluster, the mount point directory must be a shared disk.

  4. On the Database Selection page, assign your database files and transaction logs to LUNs or VMDKs and then view the results of your selections:
    1. In the Database Selection pane, select a database file or transaction log:
      Screen shot: A database file selected in the Configuration wizard.
    2. In the Disk Selection pane, select a LUN or VMDK:
      Screen shot: A LUN selected in the Configuration wizard.
    3. Click the Screen shot: The button in the Configuration wizard that assigns a database file or log to a storage location. button.
    4. Repeat substeps a to c for each database's files and logs.
    5. In the Database Location Results pane, review the results of your selections:
      Screen shot: Database location results showing a database file assigned to a LUN.
    Tip: To change your selections, click Undo All or select a database and click Reconfigure.
  5. On the SnapInfo settings page, choose whether you want a single SnapInfo directory for your databases or multiple SnapInfo directories.
    A single SnapInfo directory works well for many configurations.
  6. On the remaining SnapInfo Settings pages, specify where you want to place the SnapInfo directory or directories.
  7. In the Data Protection page, assign a protection policy to the dataset, if you installed OnCommand Unified Manager to use SnapManager's integrated SnapVault technology.
    A protection policy contains a set of rules that define how to protect data and how long to retain backups.
  8. On the Setup SnapManager Share page, specify a share to ensure that backups of transaction logs are available to all replicas within an Availability Group.
    SnapManager uses the transaction log backups for up-to-the-minute restore operations, database reseeding, and for using clones as replicas.
  9. On the Database Migration Settings page, choose settings for physical database verification, database deletion, and updates to database table statistics:
    For this field... Do this...
    Run DBCC physical integrity verification before/after migration Clear these fields.

    The integrity verification runs on the production database and is resource intensive, which can negatively impact the performance of your database. You should run verification on the initial backup set instead.

    Delete Copy of Migrated Database at Original Location Clear this field.

    You should always delete the database yourself, in case there are problems during the migration.

    Run UPDATE STATISTICS on tables before detaching the databases Leave this field selected.
    The following image shows the Database Migration Settings page with the recommended settings selected:
    Screen shot: Fields selected in the Database Migration Settings pane, with only the "Run UPDATE STATISTICS on tables before detaching the database" field selected.
  10. On the iSCSI Initiator Information page, choose whether to set the iSCSI service as a dependency and click Next:
    • If you use iSCSI, you should keep the option selected.
    • If you do not use iSCSI, clear the option.
    Setting the iSCSI service as a dependency for all SQL Server services helps protect SQL data if there is a problem with iSCSI.
  11. In the E-Mail Notification Settings page, configure settings for email notifications, event logging, and AutoSupport notifications.
    Most of the fields on this page are self-explanatory. The following table describes fields for which you might need guidance:
    Field Description
    Send e-mail notification Enables email notifications to the specified address about the success or failure of SnapManager operations.

    If you select this field, click Advanced to tune the notification settings—for example, to receive notifications only when operations fail.

    Log SnapManager events to storage system syslog If AutoSupport is enabled on the storage system, posts SnapManager events to the storage system's event log.

    Technical support can use this information to troubleshoot issues.

    Send AutoSupport notification If AutoSupport is enabled on the storage system, enables email notifications to technical support about SnapManager events or storage system problems that might occur.
    On failure only Limits the SnapManager events that are posted to the storage system event log and sent through AutoSupport to failure events only.
  12. In the Monitoring and Reporting Settings page, choose whether you want to receive email notifications that contain the status of backup, verification, and clone operations during the specified time frame.
    To receive these email notifications, you must have enabled email notifications on the previous page.
  13. In the Finish page, review the settings and click Finish.
  14. In the Configuration Status dialog box, click Start Now.
    SnapManager migrates the databases and updates your SnapManager configuration. You can view details of the operation in the Configuration Report.
  15. After the operation completes, click OK and then click Close.

After you finish

You can rerun the Configuration wizard at any time to make changes to your database configurations.

When you add new databases, you should run the Configuration wizard to ensure that the databases are stored in valid locations and to create a mapping between those databases and their respective SnapInfo directories.