When attempting to restore a LiteSpeed backup file with TSM and a problem occurs, what can you do?
Sometimes we can have workarounds to gain some time and restore a database which would be using a SQL Server native mode or a script, this solution describes the only way that a manual workaround can be implemented with LiteSpeed and TSM Server.
Restoring from TSM tape to disk to SQL LiteSpeed work when performing a backup to disk and letting TSM back it up to tape. But SQL LiteSpeed to TSM and then TSM to disk and then to SQL LiteSpeed does not work.
So if there is a problem restoring a database with TSM, if the backup was created direct to tape, there is no workaround to restore manually, the problem has to be found and fixed. It could be TSM server settings and "n" other reasons, bottom line is, this seems to be the only situation that we cannot provide a solution and the production can be down, any other backup/restore problem we can provide workarounds from SQL Server and scripts.
If using TSM Server and LiteSpeed, the best recommendation would be to create a backup file to a disk, then create the backup file from TSM to a tape, instead of creating the backup file directly to the tape. It could require time and hard disk space, but it will ensure more possibilities to recover the backup file.
© 2025 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center