How databases are stored on storage system volumes

During the data migration process, the Configuration Wizard enforces the following rules for storing your SQL Server database files and transaction log files on storage system volumes.

SQL Server database files

Database files that belong to more than one database cannot share a LUN, if all the database files do not reside on that LUN.

SQL Server transaction log files

Transaction logs can reside on the same LUN that stores the data files, or they can reside on another LUN on the same or different volume.

SnapInfo directory

The SnapInfo directory must reside on a LUN that is different from the LUN on which the SQL Server data files and SQL Server transaction logs reside.

Creating a SnapInfo directory

When the Configuration Wizard is used to migrate SQL Server databases from local disk to LUNs, it creates a SnapInfo directory that stores SnapManager information about the backup sets and the backed-up transaction logs.

If you use the Configuration Wizard to move databases to LUNs, the wizard performs the following tasks:

Detaches the selected databases.
- Before the Configuration Wizard migrates SQL Server user databases to LUNs, SnapManager detaches them. After the migration is complete, the user databases are brought back online.
- While the Configuration Wizard is migrating SQL Server system databases to LUNs, the SQL Server is stopped by SnapManager.

Note
Migrating SQL Server databases causes them to be taken offline during the move operation.

Moves the SQL Server database files and transaction log files to the correct locations on the specified LUNs.
Reattaches the databases.