Refer to the Release Notes for the current list of issues known to exist in this version of LiteSpeed.
If the computer name is changed, the local repository settings are not found, because LiteSpeed refers to the old computer name. As a result, the Local Repository database is not being populated and you cannot view LiteSpeed activity.
You need to update @@SERVERNAME for all instances on that computer and re-run the Instance Configuration wizard.
To update @@SERVERNAME value
Run the following:
exec sp_dropserver 'old_name'
exec sp_addserver 'new_name', 'local'
To run Instance Configuration
The timeline does not automatically show 4.x backup/restore jobs. However, you can manually rename the jobs and they will appear in the timeline.
To view 4.x jobs
Rename backup jobs to:
LiteSpeed Backup SERVER_NAME.database_name
Rename restore jobs to:
LiteSpeed Restore SERVER_NAME.database_name
Be sure to use upper case for SERVER_NAME. Additionally, you need to add a comment to maintenance plans to provide information about the databases involved in the plan:
LiteSpeed has been tested and is certified to work with Dell DR4000, DR4100, and DR6000 storage appliances. In rare cases the DR storage appliance may not work with LiteSpeed.
To check the DR storage appliance
Some tasks and advanced options can be unavailable if you do not select Use LiteSpeed when configuring tasks. See About Automating Maintenance Tasks for more information.
If you receive one of the following error messages, you probably need the Backward Compatibility components installed:
For more information, see http://support.microsoft.com/kb/955626.
LiteSpeed plans may fail after the in-place upgrade of SQL Server. Upgrade LiteSpeed Maintenance Plans
Enable advanced logging and review log files for errors or work with Quest Software support to identify and resolve plan problems. Reporting and Logging in Maintenance Plans
NOTE: For all scenarios, the best is to upgrade all of your servers to the latest LiteSpeed version.
If upgrading LiteSpeed 5.x or later, the Maintenance Plans should remain intact and no additional steps are required.
If upgrading LiteSpeed 4.x, the SSMS plug-in maintenance plans need to be manually upgraded. LiteSpeed allows you to read SSMS plug-in maintenance plans and upgrade them to SSIS LiteSpeed maintenance plans.
NOTE: The Remove files older than option in the Backup Database task does not remove LiteSpeed 4.x SSIS maintenance plans backups. To remove old backup files for these plans, you can use a separate Clean up maintenance plans task.
SSIS LiteSpeed plans must be manually upgraded to use the appropriate library, otherwise they will fail after SQL Server upgrade. If you have at least one LiteSpeed task in a SSIS plan, then you need to upgrade the plan after upgrading SQL Server to a higher version.
To upgrade plans in LiteSpeed 6.1 or later
Right-click an instance in the Maintenance Plan pane and select Upgrade LiteSpeed Maintenance plans.
© ALL RIGHTS RESERVED. Feedback Termini di utilizzo Privacy Cookie Preference Center