What is the process to have LiteSpeed activity update to the Local and Central Repositories? From the LiteSpeed Help File:
LiteSpeed 2005 can collect and retain statistics on backups occurring through the LiteSpeed 2005 Engine from the GUI, command line, or extended stored procedures, including backups completed by native SQL Server. This is optional and is activated by running Instance Configuration.
LiteSpeed 2005 uses one or more databases to store the statistics. Each instance of SQL Server on which LiteSpeed 2005 is installed has its own local statistics database (known as the local repository). The backup statistics for a SQL Server workgroup can be consolidated into a central repository.
LiteSpeed uses the LiteSpeed ActivityManager Service to update the Central repository from the Local repositories with LiteSpeed or Job and DTS Statistics activity if set up during the Instance Configuration process. LiteSpeed uses a service to transfer the statistics from each local repository to the central repository.
Specify the account used to run the service during Instance Configuration. This account must be able to log in to the central repository using Windows Authentication. The login for the service must have read/write and dbowner permissions on both SQL Servers (where the LiteSpeedLocal and LiteSpeedCentral are located).
To troubleshoot the statistics process, at the command prompt, navigate to %\Program Files\Imceda\LiteSpeed\SQL Server\Engine and run the following command: activitymanager.exe -logging
The resulting log will be in LiteSpeed’s default log directory, %\Program Files\Imceda\LiteSpeed\SQL Server\Engine\Logs (or %\Documents and Settings\All Users\Application Data\Quest\LiteSpeed after version 4.8x). The log will be named similar to: 'ActivityManager.exe - 13-Jun-2007 09-42-01-643.txt'.
Note: the cmdline will run as the user, as he/she is logged in. The login for the LiteSpeed ActivityManager Service may be a different user.