Log Shipping - Restoring Logs Error
barrys
Posts: 5
Ok,
This one is making me pull my hair out.
I am running a completely automated process. I run a T-Log backup every hour. I run a T-Log restore (on a seperate box) twice a day.
I keep getting a LSN out of order error sporadically. Sometimes it will work fine and other times it will just say out of order. But since this is 100% automated I do not understand how that is possible.
Each time the restore runs there are about 10 - 15 log files to restore. Here is the latest log file that shows the failure SMACK in the middle of restoring. The first 5 or 6 are fine and then....
Please Help!!
SQL Backup 3.2.0, (c) Red Gate Software Ltd 2004 - 2005
Serial number: 010-001-024332-7A3C
Restoring transaction logs for database BEMetadata from "c:\SCDB01\BEMetadata\logs\*.sqb"
Processing log group 49790957 ...
c:\SCDB01\BEMetadata\logs\LOG_(local)_BEMetadata_20050824 070001.sqb
Completed.
Moved LOG_(local)_BEMetadata_20050824 070001.sqb to c:\SCDB01\BEMetadata\logs\processed\.
Processing log group 49786861 ...
c:\SCDB01\BEMetadata\logs\LOG_(local)_BEMetadata_20050824 080001.sqb
Completed.
Moved LOG_(local)_BEMetadata_20050824 080001.sqb to c:\SCDB01\BEMetadata\logs\processed\.
Processing log group 49795053 ...
c:\SCDB01\BEMetadata\logs\LOG_(local)_BEMetadata_20050824 090000.sqb
Completed.
Moved LOG_(local)_BEMetadata_20050824 090000.sqb to c:\SCDB01\BEMetadata\logs\processed\.
Processing log group 26546557 ...
c:\SCDB01\BEMetadata\logs\LOG_(local)_BEMetadata_20050824 100002.sqb
c:\SCDB01\BEMetadata\logs\LOG_(local)_BEMetadata_20050824 110001.sqb
Completed.
Moved LOG_(local)_BEMetadata_20050824 100002.sqb to c:\SCDB01\BEMetadata\logs\processed\.
Moved LOG_(local)_BEMetadata_20050824 110001.sqb to c:\SCDB01\BEMetadata\logs\processed\.
Processing log group 26542189 ...
c:\SCDB01\BEMetadata\logs\LOG_(local)_BEMetadata_20050824 120001.sqb
Completed.
Moved LOG_(local)_BEMetadata_20050824 120001.sqb to c:\SCDB01\BEMetadata\logs\processed\.
Msg 4305, Level 16, State 1, Server SCBAK01, Line 1
The log in this backup set begins at LSN 127696000005460100001, which is too late to apply to the database. An earlier
log backup that includes LSN 127612000007758400001 can be restored.
Msg 3013, Level 16, State 1, Server SCBAK01, Line 1
RESTORE LOG is terminating abnormally.
Msg 4305, Level 16, State 1, Server SCBAK01, Line 1
The log in this backup set begins at LSN 127696000010665000001, which is too late to apply to the database. An earlier
log backup that includes LSN 127612000007758400001 can be restored.
Msg 3013, Level 16, State 1, Server SCBAK01, Line 1
RESTORE LOG is terminating abnormally.
Msg 4305, Level 16, State 1, Server SCBAK01, Line 1
The log in this backup set begins at LSN 127697000004371100001, which is too late to apply to the database. An earlier
log backup that includes LSN 127612000007758400001 can be restored.
Msg 3013, Level 16, State 1, Server SCBAK01, Line 1
RESTORE LOG is terminating abnormally.
Msg 3259, Level 16, State 1, Server SCBAK01, Line 1
The volume on device 'SQLBACKUP_{246E52AE-8B5C-4468-9822-BE02260E6C20}' is not part of a multiple family media set.
BACKUP WITH FORMAT can be used to form a new media set.
Msg 3013, Level 16, State 1, Server SCBAK01, Line 1
RESTORE LOG is terminating abnormally.
Msg 4305, Level 16, State 1, Server SCBAK01, Line 1
The log in this backup set begins at LSN 127701000000031800001, which is too late to apply to the database. An earlier
log backup that includes LSN 127612000007758400001 can be restored.
Msg 3013, Level 16, State 1, Server SCBAK01, Line 1
RESTORE LOG is terminating abnormally.
This one is making me pull my hair out.
I am running a completely automated process. I run a T-Log backup every hour. I run a T-Log restore (on a seperate box) twice a day.
I keep getting a LSN out of order error sporadically. Sometimes it will work fine and other times it will just say out of order. But since this is 100% automated I do not understand how that is possible.
Each time the restore runs there are about 10 - 15 log files to restore. Here is the latest log file that shows the failure SMACK in the middle of restoring. The first 5 or 6 are fine and then....
Please Help!!
SQL Backup 3.2.0, (c) Red Gate Software Ltd 2004 - 2005
Serial number: 010-001-024332-7A3C
Restoring transaction logs for database BEMetadata from "c:\SCDB01\BEMetadata\logs\*.sqb"
Processing log group 49790957 ...
c:\SCDB01\BEMetadata\logs\LOG_(local)_BEMetadata_20050824 070001.sqb
Completed.
Moved LOG_(local)_BEMetadata_20050824 070001.sqb to c:\SCDB01\BEMetadata\logs\processed\.
Processing log group 49786861 ...
c:\SCDB01\BEMetadata\logs\LOG_(local)_BEMetadata_20050824 080001.sqb
Completed.
Moved LOG_(local)_BEMetadata_20050824 080001.sqb to c:\SCDB01\BEMetadata\logs\processed\.
Processing log group 49795053 ...
c:\SCDB01\BEMetadata\logs\LOG_(local)_BEMetadata_20050824 090000.sqb
Completed.
Moved LOG_(local)_BEMetadata_20050824 090000.sqb to c:\SCDB01\BEMetadata\logs\processed\.
Processing log group 26546557 ...
c:\SCDB01\BEMetadata\logs\LOG_(local)_BEMetadata_20050824 100002.sqb
c:\SCDB01\BEMetadata\logs\LOG_(local)_BEMetadata_20050824 110001.sqb
Completed.
Moved LOG_(local)_BEMetadata_20050824 100002.sqb to c:\SCDB01\BEMetadata\logs\processed\.
Moved LOG_(local)_BEMetadata_20050824 110001.sqb to c:\SCDB01\BEMetadata\logs\processed\.
Processing log group 26542189 ...
c:\SCDB01\BEMetadata\logs\LOG_(local)_BEMetadata_20050824 120001.sqb
Completed.
Moved LOG_(local)_BEMetadata_20050824 120001.sqb to c:\SCDB01\BEMetadata\logs\processed\.
Msg 4305, Level 16, State 1, Server SCBAK01, Line 1
The log in this backup set begins at LSN 127696000005460100001, which is too late to apply to the database. An earlier
log backup that includes LSN 127612000007758400001 can be restored.
Msg 3013, Level 16, State 1, Server SCBAK01, Line 1
RESTORE LOG is terminating abnormally.
Msg 4305, Level 16, State 1, Server SCBAK01, Line 1
The log in this backup set begins at LSN 127696000010665000001, which is too late to apply to the database. An earlier
log backup that includes LSN 127612000007758400001 can be restored.
Msg 3013, Level 16, State 1, Server SCBAK01, Line 1
RESTORE LOG is terminating abnormally.
Msg 4305, Level 16, State 1, Server SCBAK01, Line 1
The log in this backup set begins at LSN 127697000004371100001, which is too late to apply to the database. An earlier
log backup that includes LSN 127612000007758400001 can be restored.
Msg 3013, Level 16, State 1, Server SCBAK01, Line 1
RESTORE LOG is terminating abnormally.
Msg 3259, Level 16, State 1, Server SCBAK01, Line 1
The volume on device 'SQLBACKUP_{246E52AE-8B5C-4468-9822-BE02260E6C20}' is not part of a multiple family media set.
BACKUP WITH FORMAT can be used to form a new media set.
Msg 3013, Level 16, State 1, Server SCBAK01, Line 1
RESTORE LOG is terminating abnormally.
Msg 4305, Level 16, State 1, Server SCBAK01, Line 1
The log in this backup set begins at LSN 127701000000031800001, which is too late to apply to the database. An earlier
log backup that includes LSN 127612000007758400001 can be restored.
Msg 3013, Level 16, State 1, Server SCBAK01, Line 1
RESTORE LOG is terminating abnormally.
Comments
Processing log group 26546557 ...
c:\SCDB01\BEMetadata\logs\LOG_(local)_BEMetadata_20050824 100002.sqb
c:\SCDB01\BEMetadata\logs\LOG_(local)_BEMetadata_20050824 110001.sqb
A patch exists for this.
SQL Backup Consultant Developer
Associate, Yohz Software
Beyond compression - SQL Backup goodies under the hood, updated for version 8
I already patched it once for a different issue (was getting some VDI error) - will this other patch void the original patch? Also, where can I get the patch that fixes that?
SQL Backup Consultant Developer
Associate, Yohz Software
Beyond compression - SQL Backup goodies under the hood, updated for version 8