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