Table of ContentsView in Frames

How databases are stored on storage system volumes

About database storage

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
  • You cannot spread a database's files across SAN and NAS.
  • Database files that cannot be integrated to more than two LUNs or VMDKs cannot be used.

SQL Server transaction log files Transaction logs can reside on the same LUN or VMDK that stores the data files, or they can reside on another LUN or VMDK on the same or different volume. Transaction logs that belong to more than two LUNs or VMDKs cannot be used.

SnapInfo directory The SnapInfo directory must reside on a LUN or VMDK that is different from the LUN or VMDK on which the SQL Server data files and SQL Server transaction logs reside.
Note: This restriction does not apply to SMB shares.

Creating a SnapInfo directory When the Configuration wizard is used to migrate SQL Server databases from a local disk to LUNs, SMB shares, or VMDKs, the Configuration wizard 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, the wizard performs the following tasks:

Stage Process


Detaches the selected databases:

  • Before the Configuration wizard migrates SQL Server user databases, it detaches them.
  • While the Configuration wizard is migrating SQL Server system databases, SnapManager stops the SQL Server.
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 storage.


Reattaches the databases.


Brings user databases back online after the migration is complete.