<div>What's important is if they are a TDE type competitor and the data stays encrypted in flight or if it simply stores the data encrypted but decrypts for backup?</div><div></div><div>Either way, LiteSpeed will work, but the latter will allow for compression whereas TDE style encryption does not allow for compression.
How to execute slssqlmaint.exe directly from a command line? ... slssqlmaint.exe can be directly executed at a command prompt. ... at <SQL Server Instance Path>\Binn\slssqlmaint.exe ... For more information on the parameters, user can run "slssqlmaint.exe -?"
JPEG files are already highly compressed. ... And once something is compressed, it's unlikely you'll get additional compression. ... Depending on how much other data exists in the database, you might still see good overall compression, but if a majority of the data is in the JPEG files, then LiteSpeed data compression may not help much.
SQL Server service account and SQL Server Agent service account must have sysadmin permission on accessing the publisher's and vice versa ... Verify that the accounts starting SQL Server service and SQL Server Agent service have the sysadmin permission to access not only the Publisher server, but also the Subscriber SQL Server.
Creating a log shipping plan using the wizard available from within Enterprise Console. ... The process to create the plan fails at the point of creating the restore jobs on the subscriber server.
Maintenance Plan Jobs are not deleting old backups. ... The backup files are older than our retention configuration. ... Steps To Reproduce: ... Create a maintenance plan (MP) with a backup task.
Maintenance plan report formatting is incorrect. ... Steps To Reproduce: ... Run a maintenance plan with maintenance plan reporting enabled. ... Review the MP report. ... Note MP report now list the “backup destination” twice.
Failed to insert data into new table [database]..[tablename] The statement has been terminated. ... OLE DB provider 'STREAM' reported an error. ... The provider did not give any information about the error.
We have a transaction log backup job that is periodically failing. ... When this happens, in the console UI, we see: ... Msg 16389, Sev 16, State 1: The connection is no longer usable because the server response for a previously executed statement was incorrectly formatted.
A nonrecoverable I/O error occurred on file "VDI_DEDCED70-785D-499D-9EA9-C40DFFD841A5_0:" 995(The I/O operation has been aborted because of either a thread exit or an application request.). ... Write on "VDI_DEDCED70-785D-499D-9EA9-C40DFFD841A5_0" failed: 1223(The operation was canceled by the user.)
In LiteSpeed version 8.9.1, when running Maintenance Plans, sporadically fails comes up with the following message in the log file ... Access violation at address 00007FFC09944D62 in module 'ntdll.dll'.
When performing Litespeed backup to TSM (Archive mode) for very large (several TBs) MS SQL database the TSM Active Log expodentially growth till the TSM server is out of space. ... TSM does not correctly estimate the database size.
actual backup taking several times longer than what the Backup Analyzer said the backup would take. ... Possible Cause 1:<br><br>Likely you selected options for the backup different from what had been selected in the Backup Analyzer.<br><br>For example:<br><br><div>AdaptiveCompression='speed'</div><div>OLRMap='1'</div><div></div><div>And/or the 'Verify' option.
<p>What are the IBM Tivoli Storage Manager (TSM) requirements to use with SQL LiteSpeed?</p> <p>You need to have a Tivoli Storage Manager (TSM) Server on a computer as well as the TSM Client installed on the computer where SQL LiteSpeed is installed. The Tivoli Data Protection for Microsoft SQL Server (TDP) Client is not needed for SQL LiteSpeed to interface with TSM.</p>
There are a number of Local repositories on different machine which are to update a central repository stored on another machine. ... It seems that the Central repository is not being updated with information from the local repository.
Native SQL Server 2005 supports full and log backups that are a copy-only backup, which does not affect the normal sequence of backups (LSN numbers). ... A copy-only backup is created independently of the regularly scheduled, conventional backups.
Use a EC2 vm with an IAM role that uses normal recommended AWS permissions. ... Run a backup to an S3 bucket. ... Note error. ... WORKAROUND ... None ... STATUS ... Issue fixed in version 8.9.1.
How to create a scheduled job in Enterprise Console, right click does not allow user to create a new job. ... Right click in Enterprise Console does not provide option to create job, native SQL Server (both 2000 and 2005) utilize right click | create job
Right-clicking a Job or highlighting a Job and clicking "delete" in LiteSpeed for SQL Server does not remove the Jobs. ... Delete function is not available in LiteSpeed.
We want backup templates to have the option to mirror backups Tracked as enhancement request CR100865 Yes, starting with LiteSpeed version 8.6.
How to change the encryption password within a job step from Quest Enterprise Console on a maintenance plan to automatically at update at scheduled intervals. ... Use the LiteSpeed Edit Maintenance Plan function to change the encryption password for the maintenance plan.
Error displays when trial license is expired. ... Server: Msg 50000, Level 19, State 1, Line 0 Object Recovery is only supported in the Professional Edition of LiteSpeed 2005. ... To use Object Recovery please upgrade to the Professional Edition of LiteSpeed 2005.
Automated restore gives incorrect message says database was dropped. ... The reason the database is not dropped is due to the database currently being in use. ... This message is telling us that:
Option "Remove files older than" in the is not removing old Fast Compression backups This option only removes files that match the specified extension from the specified destination folder.<br>The extension of the Fast Compression bakups is different so these backups will not be removed.<br><br>Tip: To remove obsolete files from different locations, use the Clean Up task.
After we had moved the storage directory location of our backups, the next backup attempt returned the error below: ... This error can also happen after a failover if that secondary machine (which has now become the primary) is configured to write/store the backups to a different directory than the original primary had been doing before the failover.
© 2025 Quest Software Inc. ALL RIGHTS RESERVED. Términos de uso Privacidad Cookie Preference Center