File name is too long when using Fast Compression.
Errors may include:
SqlLiteSpeed has returned failure exit code: 10405
Msg 60405, Level 16, State 1, Line 1572864: SqlLiteSpeed has returned failure exit code: 10405
-or-
Executing the query "execute master..xp_slssqlmaint N'-D "ALL DATABASES..." failed with the following error: "31 09-33-30).d0.bkp
> LiteSpeed(R) for SQL Server Version 6.5.x
FIle names for backup files may be long when a Ful backup was created outside the Fast Compresion maintenance plan.
I created a database with a long name and just ran xp_backup_database to create this full backup file file:
testdbtestdbtestdbtestdbtestdbtestdbtestdbtestdbtestdbtestdbtestdbtestdbtestdbtestdb123606.bak
Then I created my Fast Compression Maintenance Plan with “separate backup files” and I got this file the first time I ran it (notice, it references the Full backup of the database).
(testdbtestdbtestdbtestdbtestdbtestdbtestdbtestdbtestdbtestdbtestdbtestdbtestdbtestdb123606.bak 2011-11-01 12-36-56).d0.bkp
I changed the Fast Compression Maintenance Plan from “separate backup files” to “Self-contained Backup Sets” and reran the job.
Result: the modify date changed, the size changed on this file, but the shorter name was used.
testdbtestdbtestdbtestdbtestdbtestdbtestdbtestdbtestdbtestdbtestdbtestdbtestdbtestdb123606.bak
When I run this query, I see all the backups that are included:
EXEC master.dbo.xp_restore_headeronly
@filename = 'filename_here.bak'
WORKAROUND:
Change the Fast Compression Maintenance Plan from “separate backup files” to “Self-contained Backup Sets”
STATUS:
Waiting for fix in future versin of LiteSpeed for SQL Server.
© 2025 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center