Using the Where to Put the Default SnapInfo Directory for Each SQL Server Instance screen

In the unlabeled list, expand an SQL Server instance.

In the Disk List, select the LUN on which you want to create the default SnapInfo directory for this instance.

Note
For more information about any LUN in the Disk List, move the mouse over the LUN name. This causes a tooltip to appear and display the IP address or host name of the storage system and the name of the volume that houses the LUN.

Click the move (<=>) button.

Result

The Default SQL Server SnapInfo Directory Path List displays the path for the SnapInfo directory.

Note
The Configuration Wizard will allow you to create the SnapInfo directory only in valid locations. For more information, see SQL Server database configuration restrictions enforced.

If you want to unmap the SnapInfo directory for an SQL Server instance, do the following:

1. In the Default SQL Server SnapInfo Directory Path List, select the SQL Server instance.
2. Click Reconfigure.

Result

The LUN is removed from the Default SQL Server SnapInfo Directory Path List. The LUN is returned to the list of unconfigured database LUNs, and you can reassociate its SnapInfo directory with any available LUN.

By default, the SnapInfo directory name is SMSQL_SnapInfo. If you want to specify a different location or name, complete the following steps:

1. In the Default SQL Server SnapInfo Directory Path List, select the SQL Server instance for which you want to change the location or name of the SnapInfo directory.
2. Click Details.

   The Default SnapInfo Property dialog box appears and displays the current location specified for the SnapInfo directory for the selected SQL Server instance.

3. In the New SnapInfo Directory Path box, enter the new path.
4. Click OK.

   The dialog box closes, and the To column of the Default SQL Server SnapInfo Directory Path List displays the updated path information.

   Note
   The Configuration Wizard will allow you to create the SnapInfo directory only in valid locations. For more information, see SQL Server database configuration restrictions enforced.