LiteSpeed for SQL Server 8.9.7 - Integration with TSM Guide

Configure Server Instances

In the LiteSpeed Instance Configuration wizard you will select the SQL Server instances that will use LiteSpeed and install extended stored procedures that LiteSpeed needs to run on the instances. You must install the extended stored procedures to take full advantage of LiteSpeed functionality on the selected instances.

In addition, you can configure activity logging using this wizard. Activity logging works by installing a local repository on a server instance to record its activity, and then installing a central repository to consolidate information from the local repositories. Quest Software recommends that you configure activity logging to benefit fully from LiteSpeed's features.

To configure server instances on the local computer

1. Start the Instance Configuration wizard from Start | All Programs | Quest Software | LiteSpeed for SQL Server | LiteSpeed Instance Configuration. In the installation scenario, the LiteSpeed Instance Configuration wizard is launched automatically.

2. On the Template page (not available for first time Instance Configuration Wizard use), select a template with the settings configured during first the wizard use (or load from a file by use Load button) and press Apply to automatically fill in all settings in the wizard. To apply changes into the wizard settings press Next and go through all wizard's steps.

3. On the SQL Instances page, select the SQL Server instances on which you want to install the extended LiteSpeed stored procedures. The default behavior is to install the procedures onto all instances. Also, when you re-run the wizard to modify existing options, be sure to select Install.

   Tip: If you do not want to install the procedures on an instance, click the action and change it to Ignore. When you select Uninstall next to an instance, the wizard removes the LiteSpeed extended stored procedures from the instance.

   Verify the connection details for each server. To change login details, select Windows or SQL Server authentication.

4. On the Activity Logging page, select whether you want to configure a central and a local repository, or only a local repository.For more information, see About Collecting Statistics in Repositories.

   LiteSpeed creates a local repository database to collect backup activity information. This database can be a dedicated database or an existing database of your choice. You can create the central repository once and point to it in subsequent installs.

   If you decide to create and configure only local repositories during installation, you may define a central repository later using the LiteSpeed UI Console to enable consolidated logging.

5. Complete the wizard.

   Use the following information to help guide you through instance configuration:

   Page	Description
   Service Account	Specify login information for the LiteSpeed Activity Manager service. This service runs on each server and merges statistics from the LiteSpeed local repositories to the central repository database. Typically the account is a Windows domain account. It must have permissions to update the central repository database using Windows authentication (for a cluster configuration, the Windows account must have permissions on all nodes). For more information, see Privilege and Grant Requirements. NOTE: You should select Local system when the central repository is on the same server as the local repository. If the central repository is on another server, the Activity Service will not be able to use Windows authentication to access it. You will need to provide SQL Server login and password on the Central Repository screen.
   Local Repository	LiteSpeed uses the login details you specify to connect to the server instance, create the database, and add objects to it. This account must have the appropriate permissions.
   Native Backup Activity	Select whether you want to update the local repository with information about native SQL Server backup activity and view it in the LiteSpeed UI Console. Click Schedule to modify the default schedule.
   Central Repository	Point to the server instance and database. Create and upgrade a Central Repository database. LiteSpeed creates the database if it does not already exist. It checks the version and upgrades if necessary.
   Repository Update	Indicate when you want the central repository to be updated with backup and job statistics. You can have LiteSpeed update the central repository: Automatically after any LiteSpeed activity, such as after every backup/restore operation (best for real time statistics). Via a scheduled SQL Server job (best for minimal network traffic). Manually. For more information, see Push Statistics to Central Repository. NOTE: Quest Software recommends that you select Automatically after any LiteSpeed activity for both selections.
   Repository Cleanup	Select to set repository maintenance, including when to delete old data from repositories, and how much of that data to delete. Old data can be deleted from the local repository, central repository, or both. The repositories are individually selected to remove activity older than a user-selectable number of days, weeks, months, or years. Additionally, Edit Schedule launches a screen where schedule information can be changed. Tip: Further repository cleanup can be accomplished by using the Purge Repository Data procedure.
   Proxy settings	Select Use proxy settings for cloud connections. When selected, you can add the proxy address and port. Optionally, you can select to use authentication and then enter username and password. In most cases, proxy settings are not required. It is recommended to do not use proxy settings by default.
   Summary	Displays a summary of instance configuration selections. Save As Template button allows saving selected in the wizard options locally for next time use in the wizard