Release Notes

LiteSpeed for SQL Server is a revolutionary, patented development in database backup technology, encompassing the latest encryption and compression algorithms to deliver a complete solution for your archiving needs. LiteSpeed maximizes disk space and process efficiency while greatly reducing the overhead costs associated with maintaining a state-of-the-art database facility.

The size of the backup file is typically only a fraction of the size of the original database. This maximizes storage efficiency and saves significant disk space. The encryption algorithm ensures that data cannot fall into the wrong hands as it is transported to an off-site backup facility.

Downtime and database failures are a reality. Components fail, databases become corrupted, and administrators make mistakes. But by using LiteSpeed, you can reduce restore time and minimize downtime. Mission critical databases can be brought back online quickly and reliably using LiteSpeed’s revolutionary new technology.

For more information about LiteSpeed and interaction with other users, visit the LiteSpeed Community web site at http://sqlserver.quest.com.

New in This Release

New in LiteSpeed 5.0.1

LiteSpeed 5.0.1 is a patch release that fixes issues in Log Shipping, Maintenance Plans, and the Backup Analyzer.

New in LiteSpeed 5.0

LiteSpeed 5.0 has a new look and feel. It has a redesigned user interface as well as several new features to increase productivity and functionality.

Resolved Issues and Enhancements

Resolved Issues in LiteSpeed 5.0.1

The following is a list of issues addressed and enhancements implemented in the LiteSpeed 5.0.1 release:

Feature	Resolved Issue	Defect ID
Install and Uninstall	The LiteSpeed 5.0.1 demo license now includes Enterprise features, such as Object Level Recovery, Advanced Compression, and Log Reader.	ST#52890
Backup and Restore	The Backup Analyzer now includes fields for the estimated backup size and duration.	ST#53702
	The Backup Analyzer now includes Advanced Compression.	ST#53701
	LiteSpeed now allows backups and restores to TSM file spaces with a comma in the name.	ST#53448
	LiteSpeed can now auto-generate a backup file name. This option is available from the Select Backup Destination page of the Backup Wizard. Click Add, and then click the 'generate' link.	ST#53279
	LiteSpeed now supports back ups to TSM if the TSM client is installed to the non-default installation path.	ST#53086
	When users verify a backup, the script no longer creates an extra parameter for xp_restore_verifyonly.	ST#52602
Log Shipping	If users select 'Perform full back up and then restore to initialize subscriber(s)' in the log shipping wizard, LiteSpeed no longer moves the subscriber database to the master file location.	ST#53638
	When users edit a log shipping plan, LiteSpeed saves changes to the 'Backup interval' and 'Acceptable latency' fields.	ST#52641
	Restore jobs succeed after a new full backup has been manually restored to a subscriber database.	ST#49719
	LiteSpeed now supports log shipping plans with the publisher and subscriber on the same instance.	ST#53668
	Users can now define custom restore paths for the subscriber database.	ST#53727
	If the database already exists on the subscriber and the option to backup/restore database is on, it is restored to the same location as original database files but new file names are generated.	ST#53728
	Log shipping restores automatically skip old t-log backups now.	ST#52168
	If some configuration data was not deleted properly from the subscriber, users now get a message to manually remove the old data when they try to recreate the subscriber for the same publisher.	ST#52431
	The Edit Log Shipping Plan wizard no longer displays a 'There are no changes' message when users change the subscriber.	ST#52596
	If users delete one subscriber from a log shipping plan with two subscribers, the Monitoring tab now shows the remaining subscriber when they delete the other one (issue only applied to SQL Server 2000).	ST#52595
	LiteSpeed now saves changes to advanced options in the Edit Log Shipping Plan wizard.	ST#52647
	For native SQL Server 2005 log shipping plans, the plan name now displays correctly in the LiteSpeed Console.	ST#52597
	LiteSpeed now supports log shipping on case-sensitive instances of SQL Server 2000.	ST#54407
	LiteSpeed now supports logging for subscriber.	ST#54229
	Users can now add subscribers to an existing log shipping plan with encryption.	ST#52612
Maintenance Plans	Maintenance plans with the 'all system databases' option in the integrity check no longer fail.	ST#53981, ST#53983, ST#53993
	Databases with a period (.) in the name now successfully back up.	ST#53899
	The notify operator task no longer fails for SSIS.	ST#53671

Resolved issues in LiteSpeed 5.0

The following is a list of issues addressed and enhancements implemented in the LiteSpeed 5.0 release:

Feature	Resolved Issue	Defect ID
General	LiteSpeed correctly returns processor/affinity details.	ST#38969
General	A bug with MDAC which caused the DbMaintStatus query to be malformed has been fixed.	ST#38951
Install and Uninstall	During install when using the 'Use same login for all instances' option and SQL Authentication, the install script no longer swaps the user name and password.	ST#43981
Install and Uninstall	The SSMS plug-in is now fully uninstalled if LiteSpeed is uninstalled from a system running X64\X86 side-by-side.	ST#38691
Backup and Restore	Collations which have commas in their environment values instead of periods are now interpreted properly so that statistics work.	ST#43848
	Changed Monitor Background Jobs/Background Job Monitor to Monitor Background Tasks/Background Tasks Monitor to clarify that a job is not running.	ST#39142
	When users enter the same filename more than once for a striped backup or restore, LiteSpeed checks for duplicates and responds properly.	ST#38992
	When users back up to a root directory, they can now specify root with \(C:\) or with C:	ST#38970
	LiteSpeed can now mirror a striped backup. Previously, this could only be done for native backups.	ST#38961
	The Done button is now available in the Edit Connection Properties window when performing SSMS plug-in native Maintenance Plan conversion.	ST#38952
	Even if the MSDB table is not updated after the backup successfully completes, the backup file is not deleted.	ST#38945
	Users can now restore some but not all attached files without the process hanging or ending.	ST#38853
	Scheduling a job from the Backup or Restore wizard no longer fails if the IP address is used as the instance name.	ST#38848
	The 'Backups in progress' statistic now shows activity when jobs are running.	ST#38809
	Restore from tape 'backup content' window intelligently chooses a database to match the selected file. Users no longer have to use a drop-down menu to choose the correct database.	ST#38808
	When performing a backup to tape, the UNLOAD parameter now works when used with xp_restore_verifyonly.	ST#38924
	Attempting to restore multiple transaction logs from TSM using the user interface console no longer fails with an error message.	ST#38796
	The Restore wizard correctly identifies differential backups appended to the same file created with the NON-Wizard Backup option.	ST#38692
Log Shipping	For jobs scheduled for intervals of 60 minutes or more, log shipping converts the time to hours so that the job runs successfully.	ST#38802
	The stored procedure (SLS_Init_LogShipping) allows users to choose whether or not to delete old backup files.	ST#38773
	An enhancement to log shipping automatically synchronizes the subscriber server when it falls behind. It runs the stored procedure (SLS_LopShipping_Sync_subscribers).	ST#38713
	Log Shipping now handles NULL values correctly and always returns FALSE. This is the SQL Server default which, when changed, caused log shipping to fail.	ST#38694
	Users can now monitor log shipping from the UI console.	ST#38686
Maintenance Plans	LiteSpeed now retains all options correctly when it converts a SQL Studio maintenance plan to LiteSpeed.	ST#49621
	The size limit for a SQL command in a task was increased so that the SQL task does not get cut off.	ST#44792
	A LiteSpeed differential backup maintenance plan remembers settings even if users do not select the 'Use LiteSpeed for SQL Server' Backup option.	ST#38959
	Maintenance plans no longer retain an extra backup when users delete old backups and convert the maintenance plan to LiteSpeed.	ST#38646
	When creating a maintenance plan in the LiteSpeed Console, tape drives were not listed in the drop-down list even though the the user entered the device name in the LiteSpeed Maintenance Plan. Now, the list updates properly.	ST#38626
	The slsreg.exe file is now removed after users uninstall LiteSpeed.	ST#38790
Object Level Recovery	A stack dump no longer occurs if users click Finish before the bulk copy process completes.	ST#38971

Known Issues

The following is a list of issues known to exist at the time of the LiteSpeed 5.0.1 release:

Feature	Known Issue	Defect ID
Install and Uninstall
	The uninstall process occasionally does not remove all of the Maintenance Plan DLLs. They are located in the LiteSpeed directory and you can manually remove them from the following location: C:\Program Files\Quest Software\LiteSpeed\SQL Server	ST#48517
	Remote installation for Windows 2008 fails.	ST#52244
	If users upgrading from 4.x select 'Ignore' for server instances in the Instance Configuration Wizard, the LiteSpeed 4.x engine files (extended stored procedures and .exe files) are still removed. However, the LiteSpeed 5.0 engine files are not installed.	ST#52347
	A cluster uninstall does not remove the StatsService.exe file and extended stored procedures on 32-bit passive nodes.	ST#38801
	Remote Deploy to 64-bit machines sometimes fails with the following error: "Unable to execute installer on remote machine: Range check error".	ST#54647
	The Remote Deploy Configuration wizard cannot retrieve information about SQL Server 2000 64-bit Itanium machines.	ST#54648
	Remote installation only works if the local machine has all LiteSpeed components (console and engine) installed. If users try to install LiteSpeed from a machine that only has the console, the remote installation will fail.	ST#53452
Console	The Database Properties dialog displays 'Unknown' for Backup Status instead of the last backup status.	ST#49441
	Jobs that run at midnight do not appear in the status report.	ST#38712
	If a backup directory is deleted or renamed outside of LiteSpeed, the directory still appears in the LiteSpeed Console list of backup directories.	ST#51960
	The timeline on the LiteSpeed Activity tab displays grey lines instead of actual results if users run a maintenance plan with a large number of databases.	ST#52470
	The LiteSpeed Console cannot connect to an instance when its affinity mask conflicts with the IO affinity mask.	ST#53233
	The entire help file is not available if it is accessed from Maintenance Plans, Log Reader, or Job Manager in the LiteSpeed Console.	ST#51590
Backup and Restore	LiteSpeed 5.0 does not support mirroring for TSM.	ST#49305
	The Restore Wizard shows overwritten backup sets in the Backup Content step.	ST#44282
	Restore fails if users restore native and LiteSpeed backup files at the same time with the following error: “The media family on device '<…>' is incorrectly formed.”	ST#44098
	If users simultaneously run more than one Backup Analyzer test in the background, LiteSpeed returns incorrect results for the tests.	ST#52699
	LiteSpeed incorrectly writes successful backup details to the SQL Server error log or event viewer if DBCC TRACEON (3226) is run with the backup. These details are not written for a native backup.	ST#38972
	Multiple backups with the exact same start time can cause the count for 'databases with backups' and 'databases without backups' to be wrong.	ST#38654
	The LiteSpeed Backup and Restore wizards return an error if users try to delete a device with a name that contains a space (example: ‘test device’).	ST#51402
	If users right-click a TSM backup in the Backup History tab and select Restore, the Restore wizard completes with errors.	ST#50270
	Users must be administrators to execute double-click restore files on Windows Vista and Windows 2008. If they are not, the restore fails.	ST#51986
	Back ups and restores of database snapshots fail.	ST#48383
	Users cannot archive TSM files through the Backup wizard. If they select this option in the wizard, LiteSpeed omits the 'TSMarchive' command from the script.	ST#52479
	TSM back ups for servers configured to write directly to tape occasionally fail when if the TSM server cannot satisfy a tape mount request within the timeout period following a back up.	ST#47499
	LiteSpeed cannot restore a backup file using the restore wizard if fiber mode is enabled.	ST#53230
	SQL Server 2008 backups fail when it uses the filestream data file type.	ST#53205
Log Shipping
	When one publisher has multiple subscribers for a LiteSpeed 5.0 log shipping plan, the restore job on some of the subscribers fails when a shared directory is used. Litespeed overwrites the .TUF files.	ST#52559
	If users register a subscriber server two times - the first time using valid credentials and second using invalid credentials - and then try to edit the log shipping plan, they may get a 'login failed' error.	ST#52646
	The publisher and subscriber servers must have the same version of LiteSpeed installed for log shipping to complete successfully. See Solution 45391 on SupportLink for information on upgrading log shipping plans from LiteSpeed 4.x.	ST#52230
	SQL Server 2000 Standard Edition does not support Log Shipping.	ST#54099
	Not all jobs are shown in Job Manager for a LiteSpeed 4.8 log shipping plan.	ST#53025
Maintenance Plans	Maintenance plans to perform a back up intermittently fail with a 'Failed to Login to SQL Server' error in the LiteSpeed error logs, but with no failure in the SQL Server error log. This may only be an issue if a user is backing up multiple consecutive small databases.	ST#51488
	The 'Remove files older than' option for SSIS maintenance plans does not remove 4.8 old backup files.	ST#52721
	LiteSpeed maintenance plan plug-in tasks are not removed from the SSMS toolbox when users upgrade.	ST#53074
Object Level Recovery	Object Level Recovery does not support all SQL Server 2005 data types.	ST#46004
	The @onFileGroup parameter only recovers tables to the PRIMARY filegroup.	ST#44044
	If a transaction occurs on the database during a back up, Object Level Recovery may read the backup file incorrectly or close LiteSpeed.	ST#38958
	Users sometimes receive an error when trying to restore objects from a SQL Server 2005 backup.	ST#53781
	Object Level Recovery does not support the IDENTITY data type.	ST#38827
	The create script for check constraint uses the WITH NOCHECK option when it should use the WITH CHECK option.	ST#53043
	The Select Script 'Not Like' condition in the WHERE clause does not filter correctly.	ST#53036
	The Select Script search condition in the WHERE clause does not return the correct result set for columns with certain data types.	ST#53037

Upgrade and Compatibility

You can upgrade directly from LiteSpeed 5.0 to 5.0.1. However, there are special considerations if you are upgrading from LiteSpeed 4.x to LiteSpeed 5.0 or 5.0.1. Review the following before upgrading from LiteSpeed 4.x to LiteSpeed 5.0 or later:

Log Shipping

LiteSpeed 5.0 does not support LiteSpeed 4.x log shipping plans. If you are upgrading and have LiteSpeed 4.x log shipping plans, you must follow Solution 45391 on SupportLink to update your log shipping plans. If you do not follow these instructions, your log shipping plans will fail after the upgrade is complete.

Maintenance Plans

LiteSpeed 5.0 does not support SSMS plug-in functionality. However, the LiteSpeed Console allows you to read SSMS plug-in maintenance plans and upgrade them to SSIS LiteSpeed maintenance plans.

In LiteSpeed 5.0 maintenance plans there are two ways to remove old backup files: the 'Clean up maintenance plans' task (which is only available for SSIS plans) and the 'Remove files older than' option in the 'Back Up Database' task. The 'Clean up maintenance plans' task removes LiteSpeed 4.8 and LiteSpeed 5.0 backup files. The 'Remove files older than' option removes both LiteSpeed 4.8 and LiteSpeed 5.0 backup files for legacy plans. However, for SSIS maintenance plans it only removes LiteSpeed 5.0 backup files.

LiteSpeed Activity

The timeline on the LiteSpeed Activity tab does not display activity from certain kinds of jobs if you upgrade from LiteSpeed 4.x. You can manually correct this by following Solution 45390 on SupportLink.

System Requirements

Before installing LiteSpeed, ensure your system meets the following minimum hardware and software requirements:

Global Operations

This section contains information about installing and operating this product in non-English configurations, such as those needed by customers outside of North America. This section does not replace the materials about supported platforms and configurations found elsewhere in the product documentation.

This release is Unicode-enabled and supports any character set. In this release, all product components should be configured to use the same or compatible character encodings and should be installed to use the same locale and regional options. This release is targeted to support operations in the following regions: North America, Western Europe and Latin America, Central and Eastern Europe, Far-East Asia, Japan.

This release has the following known capabilities or limitations: Litespeed for SQL Server 4.8.4 has been localized in Japanese. LiteSpeed 5.0 is an English only version.

Getting Started

Contents of the Release Package

Installation Instructions

Double-click on the installer (for instance, LiteSpeed.msi for 32-bit) and follow the on-screen directions. See the LiteSpeed 5.0 Installation Guide for full details on installing LiteSpeed. The installation guide is located on the product web site and the Quest Library. You must have Adobe Reader 8 to view the installation guide.

For More Information

Contacting Quest Software:

Contacting Quest Support:

Quest Support is available to customers who have a trial version of a Quest product or who have purchased a commercial version and have a valid maintenance contract.

Quest Support provides around the clock coverage with SupportLink, our web self-service. Visit SupportLink at http://support.quest.com.

View the Global Support Guide for a detailed explanation of support programs, online services, contact information, and policy and procedures.

This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser’s personal use without the written permission of Quest Software, Inc.

If you have any questions regarding your potential use of this material, contact:

Trademarks

Quest, Quest Software, the Quest Software logo, Imceda, LiteSpeed, and SQL LiteSpeed are trademarks and registered trademarks of Quest Software, Inc in the United States of America and other countries. Other trademarks and registered trademarks used in this guide are property of their respective owners.

Third Party Contributions

Disclaimer

The information in this document is provided in connection with Quest products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest products. EXCEPT AS SET FORTH IN QUEST'S TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest does not make any commitment to update the information contained in this document.

Email	info@quest.com
Mail	Quest Software, Inc. World Headquarters 5 Polaris Way Aliso Viejo, CA 92656 USA
Web	http://www.quest.com

Welcome to LiteSpeed for SQL Server	New in This Release	Resolved Issues and Enhancements	Known Issues	Upgrade and Compatibility
System Requirements	Global Operations	Getting Started	For More Information

Contents

Welcome to LiteSpeed for SQL Server