Using the Where to Put the Default SnapInfo Directory for LUNs Shared by Multiple Databases screen

In the unlabeled list, select the LUN or LUNs that you want to map to a shared SnapInfo directory

In the Disk List, select the LUN to move it to.

Click the move (<=>) button.

Result

The Virtual Disk SnapInfo Directory Path List displays the updated path information. The SnapInfo directory for the databases sharing the selected LUN or LUNs will be stored at this location rather than at the default location for the SQL Server instance.

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 multiple databases that share one or two LUNs, do the following:

1. In the Virtual Disk SnapInfo Directory Path List, select the shared LUN.
2. Click Reconfigure.
3. If the databases share a second LUN, repeat the preceding steps.

Result

The LUN is removed from the Virtual Disk 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 Virtual Disk SnapInfo Directory Path List, select the LUN or LUNs 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 databases that share the selected LUN or LUNs.

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