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.
LiteSpeed uses Virtual Device Interface (VDI) to generate its backups. This operates in a single contiguous region of addresses within the SQL Server process space known as MemToLeave memory area. It is set aside at startup and is left unallocated by SQL Server for the use by components in the SQL Server process space, such as extended procedures, COM/OLE Automation objects, and linked server queries. Memory allocations by SQL Server larger than 8 KB are also made from the MemToLeave area.
SQL Server's MemToLeave area becoming fragmented so that there is insufficient contiguous space to allocate the buffers required for the backups. Rebooting SQL Server will free the memory, but the underlying cause of memory fragmentation should be addressed for long-term resolution.
Factors that can drain this memory area:
To check the available contiguous memory, do one of the following:
If you experience issues with the previous versions of LiteSpeed and they are not discussed in the documentation set delivered with your LiteSpeed version, please visit https://www.quest.com/products/litespeed-for-sql-server/ to access support documentation and search the extensive Knowledgebase for published solutions and case data.
Note that for most cases the best is to upgrade all of your servers to the latest LiteSpeed version.
Logging is available for the following areas in LiteSpeed:
NOTE: Log shipping plans activity is also logged and displayed in the History tab of the Log Shipping pane (CTRL+2). See the Configure Log Shipping guide for more information.
Installer log files are created in the default output directory. When you use the Remote Deploy Configuration wizard to deploy LiteSpeed on SQL Server instances, this creates a 'RemoteDeploy'-prefixed log file on the machine where you run the remote deploy from and 'SLSInstall'-prefixed log files on all target servers. For more information, see Log File Naming and Location.
Using the following instructions you can enable logging for a particular backup or restore activity. To log all backup/restore activity on the server, see Instance-Wide LiteSpeed Logging.
To enable backup/restore logging, do one of the following:
LiteSpeed's advanced tracing facility allows for even more granular control over the major LiteSpeed features at the server level.
To enable/disable advanced logging
Right-click an instance in the server tree, select Support and then LiteSpeed Logging.
Select one or more of the following options:
Clear one or more checkboxes to disable advanced logging for those options.
Complete the dialog. Review the following for additional information:
| Option | Description |
|---|---|
| Log file path |
This parameter specifies a path to a default output directory into which the log files are written. For more information, see Log File Naming and Location. |
| Flush output to log file after every write (slower) | LiteSpeed will perform a disk flush after each record. Select this parameter if you experience program exceptions resulting in a process abort. |
| Delete log file on success | A log file is only saved if an error has occurred during execution. |
| Log rollover size | This will limit the size of the log file, so that only the last records that fit within the specified size will be kept. Use this option in the case of a long running application, when the log file becomes overly large, or when an error happens near the end of execution. Otherwise, set the rollover size value to zero. |
NOTES:
By default, log files are written to C:\Documents and Settings\All Users\Application Data\Quest Software\LiteSpeed\SQL Server\Logs (or C:\ProgramData\Quest Software\LiteSpeed\SQL Server\Logs). This location is specified by the logpath value in the LiteSpeedSettings.ini file. (Usually, C:\Documents and Settings\All Users\Application Data\Quest Software\LiteSpeed\SQL Server\LiteSpeedSettings.ini.)
To change the default output directory
Right-click an instance in the server tree, select Support and then LiteSpeed Logging.
Enter a new location in the Log file path field.
Log files will have one of the following formats:
Where source components are the following:
Other components of the log file name are as follows:
When you use the Remote Deploy Configuration wizard to deploy LiteSpeed on SQL Server instances, this creates a 'RemoteDeploy'-prefixed log file on the machine where you run the remote deploy from and 'SLSInstall'-prefixed log files on all target servers.
The LiteSpeed UI Console activity is logged in the Windows Application event log.
To set the LiteSpeed UI Console logging level
© ALL RIGHTS RESERVED. 使用条款 隐私 Cookie Preference Center
