Comments
4 comments
-
Backup files may sometimes be locked by anti-virus software, preventing SQL Backup from updating the file header. Without the file header, SQL Backup is unable to sort the group of log files in the correct order during the restore.
Try restoring only the log file that is missing its header. Then move the file out of the staging folder to the processed folder, and restart the restore job. -
Hi Peter,
Could you please let us know how we could restore the file without header?
Thanks -
E.g.
EXEC master..sqlbackup '-sql "RESTORE LOG pubs FROM DISK = [e:\backups\pubs_log_04.sqb] WITH NORECOVERY, MOVETO = [e:\backups\processed]" '
When you restore only a single backup set, SQL Backup doesn't attempt to filter/sort the file using information that would normally be contained in the header. -
Hi Peter,
When we tried to restore the log file without header, here is the error that we have been getting:
Thread 0 error:
Data decompression error: Access violation at address 0050BC83 in module 'SQBCoreService.exe'. Read of address 7FE9E28C
Server: Msg 3013
RESTORE LOG is terminating abnormally.
Server: Msg 3242
The file on device 'SQLBACKUP_06F8443D-3DC7-4F2E-B6D1-B0921AA23955' is not a valid Microsoft Tape Format backup set.
SQL Backup exit code: 790
SQL error code: 3242
Any ideas on how to resolve it?
Thanks
Add comment
Please sign in to leave a comment.
Does anyone have ever run into the following issue?
It only happens from time to time, and it is not consistent. When SQL backup runs the scheduled log shipping file, it generates the log file; however, the property of the file indicates that it is "transaction log backup" with the date and time instead of saying it is transaction log encrypted. Whenever this happens, this log file can't be restored from the restore server until the process start over again, meaning we have to have a full restore before the log shipping files can be restored on the restore server.
Is there any way to fix the log file instead of starting all over?
Thanks