When you save a customized configuration in the LiteSpeed Engine Configuration editor, the driver is automatically updated with the new configuration settings. If you open the .ini file and edit it manually, the driver must be manually updated. This may be accomplished by opening the configuration file designed for the local server and selecting the File | Driver Management | Refresh driver configuration option. Alternately, you may simply resave the configuration file for the local server. This will force a driver update on the local server.
If you did not install the LiteSpeed Engine Configuration editor on the server and need to refresh the driver, run UpdateDriver.exe on that server. For more information, see Refresh the Driver Using UpdateDriver.exe .
The configuration file can be saved with any name and to any location to be used on another machine, that is particularly useful when you are managing configurations for multiple servers from a remote location.
Select File | Open and select the desired .ini file. (If your file extension settings are saved to an .ini file other than the default.)
To view the default configuration file
Launch LiteSpeed Engine Configuration from Start | All Programs | Quest Software | LiteSpeed Engine for SQL Server.
You can remotely manage configurations without installing the LiteSpeed Engine Configuration editor on the remote server.
To configure and update the remote servers
Do one of the following:
Use LiteSpeed Engine Configuration editor on another computer to create the .ini file and then save it to the default directory of the remote SQL server. For more information, see About LiteSpeed Engine Configurations. on the configuration file default location.
After the configuration file has been edited and saved to the default directory of the SQL server, run the UpdateDriver.exe application on the SQL server. For more information, see Refresh the Driver Using UpdateDriver.exe .
If the .ini file is not saved to the default location, refer to the
HKEY_LOCAL_MACHINE\Software\Quest Software\LiteSpeedEngine\IniPath registry key. Please exercise caution when using the Windows Registry Editor.
For cluster installs, you need to install LiteSpeed Engine on all relevant nodes. For more information, see To install LiteSpeed Engine.
Configure each node to look for the same backup extensions. This can either be done manually on each node or you can create the .ini file on a single node and then copy it to the other nodes. For more information, see About LiteSpeed Engine Configurations. on the default configuration directory.
If you copied the .ini file to all nodes, refresh the driver configuration on each node. Select File | Driver management | Refresh driver configuration or run the UpdateDriver.exe. For more information, see Refresh the Driver Using UpdateDriver.exe .
NOTE: As an alternative to the above, you can locate the .ini configuration file in a shared UNC path location, then you will need to specify where the driver looks for the .ini file by changing the HKEY_LOCAL_MACHINE\Software\Quest Software\LiteSpeedEngine\IniPath registry key and refreshing the driver configuration on each node. If this shared UNC path is not available for some reason when the node starts and the driver is initialized, select File | Driver management | Refresh driver configuration from that node’s LiteSpeed Engine Configuration editor or run the UpdateDriver.exe.
Thу UpdateDriver.exe utility allows you to perform various tasks directly from the command-line interface.
NOTE: The UpdateDriver.exe application must be run by a user that has administrator privileges. If the driver update encounters issues and returns an error message, consult the Windows Event Viewer for detailed error messages.
To perform tasks from the command line
|?||Help||Displays syntax and accepted arguments.|
|c||ClearLog||Clears tracing log.|
|d||Disable||Stops the engine.|
|e||Enable||Starts the engine.|
|r||Rescan||Rescans for new drives. You may need to rescan the newly added disk devices to be able to do compressed backups to these drives.|
|s||Status||Displays driver status.|
|u||Update||Refreshes driver configuration. For more information, see Manage Configuration Files.|