Sql 2008 Issue restoring transaction logs....

Question

** Update: I performed the same steps on the corresponding Dev and things worked as expected. Only  our prod environment uses SnapManager for Sql (NetApp) and I'm beginning to suspect that may be behind this issue
Restored a full backup of the prod MyDB from 1/23/2014 in non-operational mode (so trans logs can be added). Planned to apply trans log dumps from 1/24/2014, 7am (our first of the day) to noon. But applying the 7am trans dump gave this error:
>>>>>
Restore Failed for this Server... the Log in this backup set begins at....which is too recent to apply to the database. An earlier log backup that includes LSN....can be restored.
>>>>>
That message is clear but I don't understand it in this case as the full DB dump was taken Thursday night and the tran logs I am trying to restore are all from Friday.
TIA,
edm2

Answer 1

** Update 2 **
I kept checking and am now definitely think that the NetApp SnapManager for Sql product (which is a storage based, not sql based, approach to DR) is the culprit. My view of the world was that a Full Sql Database backup is performed at 7pm and the
Sql translogs are dumped every hour beginning at 7:15am the next day.  This extract from the SnapManager log indicates quite a different story. It takes a full database backup at 11pm (!) that night followed by a translog backup.
No wonder, when I try to restoring things using Sql utilities it doesn't work. BTW: I have no idea where SnapManager's dumps are stored.
>>>>>>>>>>>>>>>>>>>>>>>>
[23:00:32.295]  *** SnapManager for SQL Server Report
[23:00:32.296]  Backup Time Stamp: 01-24-2014_23.00.32
[23:00:32.298]  Getting SQL Server Database Information, please wait...
[23:00:32.299]  Getting virtual disks information...
[23:00:37.692]  Querying SQL Server instances installed...
[23:01:01.420]  Full database backup
[..e
[23:01:01.422]  Run transaction log backup after full database backup: Yes
[23:01:01.423]  Transaction logs will be truncated after backup: Yes
[23:02:39.088]  Database [MyDatabase] recovery model is Full.
[23:02:39.088]  Transaction log backup for database [MyDatabase] will truncate logs...
[23:02:39.089]  Starting to backup transaction log for database [MyDatabase]...
[23:02:39.192]  Transaction log backup of database [MyDatabase] completed.
>>>>>>>>>>>>>>>>>>>>>>>>
Unless anyone has further thoughts I think I will close this case and take it up with NetApp.
edm2
Sorry I wasn't clearer. The Full database backups was taken on 1/23/2014 at 7pm. The trans logs I was trying to restore were from the next day (starting 1/24/2014 at 7:15am, 8:15am, etc.).   I could not find any Sql translog dumps taken after
the full backup (at 7pm) until the next morning's  trans dumps (which start at 7:15am). Here is what I did:
RESTORE DATABASE [MyDatabase] FROM  DISK =
 N'D:\MyDatabase\FULL_(local)_MyDatabase_20140123_190400.bak' WITH  FILE = 1,
 MOVE N'MyDatabase_data' TO N'C:\MSSQL\Data\MyDatabase.mdf', 
 MOVE N'MyDatabase_log' TO N'C:\MSSQL\Data\MyDatabase_1.LDF', 
 NORECOVERY,  NOUNLOAD,  STATS = 10
GO
RESTORE LOG [MyDatabase] FROM  DISK =
N'D:\MyDatabase\MyDatabase_backup_2014_01_24_071501_9715589.trn'
WITH  FILE = 1,  NORECOVERY,  NOUNLOAD,  STATS = 10
GO
Msg 4305, Level 16, State 1, Line 1
The log in this backup set begins at LSN 250149000000101500001, which is too recent to apply to the database. An earlier log backup that includes LSN 249926000000024700001 can be restored.
Msg 3013, Level 16, State 1, Line 1
RESTORE LOG is terminating abnormally.
From Sql Error Log:
2014-01-25 00:00:15.40 spid13s     This instance of SQL Server has been using a process ID of 1428 since 1/23/2014 9:31:01 PM (local) 1/24/2014 5:31:01 AM (UTC). This is an informational message only; no user action is required.
2014-01-25 07:31:08.79 spid55      Starting up database 'MyDatabase'.
2014-01-25 07:31:08.81 spid55      The database 'MyDatabase' is marked RESTORING and is in a state that does not allow recovery to be run.
2014-01-25 07:31:14.11 Backup      Database was restored: Database: MyDatabase, creation date(time): 2014/01/15(16:41:13), first LSN: 249926:231:37, last LSN: 249926:247:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK:
{'D:\MyDatabase\FULL_(local)_MyDatabase_20140123_190400.bak'}). Informational message. No user action required.
Regarding my update note,  the SnapManager for SQL product (which I was tolds simply uses VSS) runs every hour throughout the night. That's why I wondering if it could be interfering with the transaction log sequence.