Error on restore of Transaction Log
SamC
Posts: 28
After restoring multiple transaction log files successfully, SQL Backup terminated with "Restore Failed" with the message "Log file is not a valid tape backup".
It is only then that I realized the individual Log filenames are not listed in the restore log.
It is only then that I realized the individual Log filenames are not listed in the restore log.
Comments
If you restore multiple log files, the log file does contain the individual log file names that were restored e.g.
5/5/2005 12:16:56 PM: Restoring transaction logs for database logtest from "c:\@backups\*.sqb"
5/5/2005 12:16:56 PM:
5/5/2005 12:16:56 PM: Processing log group 224409789 ...
5/5/2005 12:16:56 PM: c:\@backups\logtest_log_01.sqb
5/5/2005 12:16:56 PM: RESTORE LOG [logtest] FROM DISK = 'c:\@backups\logtest_log_01.sqb' WITH NORECOVERY
5/5/2005 12:16:56 PM:
5/5/2005 12:16:56 PM:
5/5/2005 12:16:56 PM: Completed.
5/5/2005 12:16:56 PM:
5/5/2005 12:16:57 PM: Processing log group 224442557 ...
5/5/2005 12:16:57 PM: c:\@backups\logtest_log_02.sqb
5/5/2005 12:16:57 PM: RESTORE LOG [logtest] FROM DISK = 'c:\@backups\logtest_log_02.sqb' WITH NORECOVERY
5/5/2005 12:16:57 PM:
5/5/2005 12:16:57 PM:
5/5/2005 12:16:58 PM: Completed.
5/5/2005 12:16:58 PM:
5/5/2005 12:16:59 PM: Processing log group 224495805 ...
5/5/2005 12:16:59 PM: c:\@backups\logtest_log_03.sqb
5/5/2005 12:16:59 PM: RESTORE LOG [logtest] FROM DISK = 'c:\@backups\logtest_log_03.sqb' WITH RECOVERY
SQL Backup Consultant Developer
Associate, Yohz Software
Beyond compression - SQL Backup goodies under the hood, updated for version 8
I'll try to locate the file today by restoring the transaction logs individually. Assuming the logs are processed individually, it's number 16 out of 22 transaction logs.
5/4/2005 8:18:22 AM: Restoring file: \Program Files\Microsoft SQL Server\MSSQL\BACKUP\nimc\LOG_(local)_nimc_20050504 054500.sqb
There's no proprietary data in this transaction log. I can provide a zipped copy (5Kb) for your review.
Try converting the file to a regular MTF file using sqb2mtf, and restore using that.
SQL Backup Consultant Developer
Associate, Yohz Software
Beyond compression - SQL Backup goodies under the hood, updated for version 8
Wanted to let you know that I unzipped and installed the SQL Backup update.
Unfortunately the problem doesn't seem to be corrected with this update.
Sam
It's a big pain because this leaves my database in "Loading" and sometimes "Loading/Suspect" status, which I have not been able to get the database out of, without re-creating.
Is there a backup verify command I can at least run before I retore a bad full backup, so my database isn't left in non-recoverable "Loading" state?
Thanks!
SQL Backup Consultant Developer
Associate, Yohz Software
Beyond compression - SQL Backup goodies under the hood, updated for version 8