Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Logshipping Restore job is failing Expand / Collapse
Author
Message
Posted Sunday, September 29, 2013 12:04 PM
Say Hey Kid

Say Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey Kid

Group: General Forum Members
Last Login: Monday, October 13, 2014 5:46 PM
Points: 673, Visits: 2,087
Hi,

We are using lite speed for backups. Yesterday, at 6:15pm, the log backup job is failed. The SQL Server error log says, the log backup was done but there is NO backup file on disk. The restore job on Subscriber is trying to restore the 6:15 pm backup file and it's keep failing. The subsequent log backups are running fine but the restore is keep failing to restore the 6:15 pm backup file which dos not exist on disk.


Did not understand the fact that, error log says the backup happened but there is no file, the SQLAgent says the backup job failed.


Backup job log:


Executed as user: abc\sqlservice. 18:15:05 - Starting transaction log backup. Primary ID: '940df8f5-5000-4290-ab92-a59d25853ebb' 18:15:05 - Retrieved backup settings. Primary Database: 'EW', Backup Directory: '\\sqlins1\LogShipping_Backups\', Backup Retention Period: 4320 minute(s) 18:15:05 - Retrieved LiteSpeed backup settings. Compression level: , Encrypted backup: False 18:15:20 - Backup failed. Changed database context to 'master'. LiteSpeed(R) for SQL Server Version 6.5.1.1018 Copyright 2011 Quest Software, Inc. SQL Server has returned a failure message to LiteSpeed for SQL Server which has prevented the operation from succeeding. The following message is not a LiteSpeed for SQL Server message. Please refer to SQL Server books online or Microsoft technical support for a solution: Processed 1 pages for database 'EW', file 'EW_log' on file 1. BACKUP LOG successfully processed 1 pages in 0.293 seconds (0.004 MB/sec). Could not insert a backup or restore history/detail record in the msdb database. This may indicate a problem with the msdb database. The backup/restore operation was still successful. Transaction (Process ID 536) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. Process Exit Code -1. The step failed.


Message from SQL Server error log:

2013-09-28 18:15:08.88 Backup Log was backed up. Database: 2013-09-28 18:15:08.88 Backup Log was backed up. Database: EW, creation date(time): 2011/09/12(15:20:02), first LSN: 517:103852:1, last LSN: 517:103855:1, number of dump devices: 2, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'VDI_10025041-CE56-4272-82F4-69E4CDC7F66C_0', 'VDI_10025041-CE56-4272-82F4-69E4CDC7F66C_1'}). This is an informational message only. No user action is required.o, creation date(time): 2011/09/12(15:20:02), first LSN: 517:103852:1, last LSN: 517:103855:1, number of dump devices: 2, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'VDI_10025041-CE56-4272-82F4-69E4CDC7F66C_0', 'VDI_10025041-CE56-4272-82F4-69E4CDC7F66C_1'}). This is an informational message only. No user action is required.


Restore job failure:


Msg 61700, Level 16, State 1, Line 0
Unexpected termination on thread: 1, Return code: x80770004

RESTORE LOG is terminating abnormally.
The log in this backup set begins at LSN 517000010385500001, which is too recent to apply to the database. An earlier log backup that includes LSN 517000010385200001 can be restored.

Please advise.

Question: how to get the log backup file names from msdb with the log sequence number LSN 517000010385200001?
Post #1499763
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse