March 27, 2007 at 8:57 am
Hope someone can help. I have setup and configured Log Shipping between two SQL 2005 Standard servers. The SQL Agents on both are running under an domain account that has permissions to the backup directories. I have successfully created the initial backup / restore process. Right now, backup from the primary server succeeds, copy to secondary succeeds, and the restore job on the secondary appears to succeed. However, if I look at the job history for the LSRestore job on the secondary server, it logs the following: Skipped log backup file. Secondary DB: 'DBNAME' File": \\path\to\file.trn. Could not find a log backup file that could be applied to secondary database 'DBNAME'.
March 27, 2007 at 10:29 am
Matt:
Are you doing standard transaction log backups in addition to the log shipping backups? If so, it's possible that your transaction log backups are interfering with the log shipping backups (by taking place out of order and not being applied).
Carlos.
Carlos
March 27, 2007 at 10:58 am
Right on. Transaction logs are being created every hour in a local directory on the server. Should I point the LSCopy job to that directory?
March 27, 2007 at 11:07 am
Matt:
I'm not sure that it would work. I just stopped taking log backups for the database (relying on the backups that the log shipping configuration is doing). I also do a complete database backup once a day and have replication going to a failover server so I'm confident that I can come up if the primary server fails.
Carlos.
Carlos
July 17, 2007 at 11:34 am
Hi,
It seems this almost the only post about this particular problem. I am having the same issue, although i dont have any Tlog maintenance jobs running, only incrementals and full backups.
Any idea where i should be looking to resolve this
many Thanks
July 17, 2007 at 3:08 pm
Matt,Jus do as below,
1.tran log backup on primary server falls into a shared folder
2.the sql service account of secondary shud have modify privilege for that shared folder,so that copy job from secondary will copy it into secondarys folder.....the service account in secondary shud have privileges to this copied tran log folder in secondary......
anything in the error log? ? ?......let us know.
[font="Verdana"]- Deepak[/font]
July 17, 2007 at 3:25 pm
I know you meant this for matt, but since this applies to me too. i went ahead an checked and i have all necessary permissions..backup..copy jobs work just fine..so i just remove the LS config and will redo itr from scratch..see if that helps
July 17, 2007 at 3:30 pm
just check in the log shipping monitor and see what is the last tran log that was restored??? if nothing was restored from the time of configuring the log shipping it mite be a permission issue.........
[font="Verdana"]- Deepak[/font]
July 17, 2007 at 3:33 pm
This is Matt. I posted the original message on 3/27. My problem was that there was another automated backup process running that was executing a full database backup and removing all committed transaction logs. The next time the LS jobs ran, there were missing transactions and the restore failed on the secondary server. I still do a separate full DB backup but I do not remove the committed tran logs. The LS jobs DO remove the committed tran logs.
July 17, 2007 at 3:34 pm
will check the job log history..in my case am not using a monitor server.
Thx
July 18, 2007 at 9:01 am
any idea where i can check if my two maintennace jobs remove the tlogs? i have one full back up and one incremental running in sql 2005
July 18, 2007 at 6:09 pm
unless you specify a cleanup task in the maintenance plan will not remove the old backup files........go to your maintenance plan and right click and modify and see if there is a clean up task to remove the .bak files ot .trn files....else you can add one in the modify step
[font="Verdana"]- Deepak[/font]
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply