September 10, 2008 at 8:14 am
Hi,
Has anyone come across this error when trying to restore a litespeed backup?
SLS Error: XML returned from Engine was invalid. :
Error Msg: (0): '2008-08-31 21:00:12' restore failed for "dbname".
52008: Failed to uncompressing data block.RESTORE DATABASE is terminating abnormally. Read on "VDI_51170ACF-4C5D-42C4-B9AE-7713EFF4C848_6" failed: 1223(The operation was canceled by the user.)
I'm on ls version 4.8.4.00086 and the backups where done in 4.6.0.00293 (my understanding is that ls its backward compatible).
Any help is greatly appreciated.
- Thanks
MCTS: BI 2008, MCITP: BI 2008
Stay Thirsty My Friends
September 10, 2008 at 7:34 pm
If you dont have a recent backup, try using the 4.6 version to restore to be on the safe side or else do a backup with the 4.8 version and then restore.
As far the help file on 4.8 there is a list of bugs that are resolved from the previous version. See if you can locate something pertaining to this error.
Hope this helps....
The_SQL_DBA
MCTS
"Quality is never an accident; it is always the result of high intention, sincere effort, intelligent direction and skillful execution; it represents the wise choice of many alternatives."
September 11, 2008 at 9:33 am
There are a few things that could cause this.
- If you are restoring from a mapped drive
- If you are restoring from a TSM backup
- If you created a backup with a different version and a different compression level
You could try to extract the backup file using the extractor.exe and then restoring the file using the standard RESTORE DATABASE command. I would search the Quest KB and open a support case b y emailing support@quest.com.
September 11, 2008 at 1:16 pm
Thanks guys -- you've pointed me in the right direction. I will use the extractor to figure out if the backup is bad.
MCTS: BI 2008, MCITP: BI 2008
Stay Thirsty My Friends
September 30, 2008 at 10:21 am
I am having the same issue. It appears the problem really resides in the backup. When this error happens I can fix it by redoing the backup (even though the original backup showed success). The restore then typically succeeds.
Tom Andrix
September 21, 2011 at 6:33 pm
From my experience, this type of error usually indicates resource issue on the server. For example: SLS requires a certain amount of memory to be able to perform a backup or restore.
Hope this helps.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply