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.
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.
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.
|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:
|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.
|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.|
|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.|
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.