Log shipping problem. - SQL Server Forums

Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums

SQL Server 2005 Forums

SQL Server Administration (2005)

Log shipping problem.

Author

Topic

akarra
Starting Member

15 Posts

Posted - 2010-03-29 : 13:51:56

Hi,

I configured logshipping and my restore job is completed successsfully but not restoring the files and giving the below error in the job history..

Could not find a log backup file that could be applied to secondary database 'DBNAME'

I deleted the entire log shipping configuration and once again reconfigured the log shippping but no luck
the copy job is fine but restore is not working.

I can run the restore job manuall and restrore the files but automatic the jobs is success full but no restore is happened.

any ideas please.

Thanks in advance.

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2010-03-29 : 13:59:44

Check the secondary server's log shipping directory to see if the copy job has actually copied the files from the primary server. The copy job could show success even if the files aren't being copied over. I think you'll find the log shipping directory is empty, hence the issue.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog

akarra
Starting Member

15 Posts

Posted - 2010-03-29 : 14:12:11

Hi Tara,

Thanks for the response Yes I could see the files copied in the secondary server with the current timestamp and also the same backup files in primary server with the below queries.

SELECT * FROM msdb.dbo.log_shipping_monitor_primary WHERE primary_database='dbname'
SELECT * FROM msdb.dbo.log_shipping_monitor_secondary WHERE secondary_database='dbname'

yes the copy files are in sync.. this was working file till today morning and started is that any security related options to be checked.

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2010-03-29 : 14:14:11

I meant to look at the directory in Windows Explorer, not through running queries. If the files are in the physical directory, then you should attempt to run RESTORE LOG manually in a new query window to see what the problem is.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2010-03-29 : 14:15:18

One thing that can break log shipping is if anyone/anything runs BACKUP LOG outside of the log shipping maintenance plan. No tlog backups can occur outside of the plan UNLESS someone manually restores that tlog to the secondary server. Also, truncating the transaction log can cause this issue too as it breaks the chain.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog

akarra
Starting Member

15 Posts

Posted - 2010-03-29 : 14:20:38

Yes what the physical files are there in the windows explore log shipping folder. Iam able to run manually the restore job but the job is not automatically executed. Also I just now reconfiugred the entire setup of logshipping from the scratch
even then the problem persists. could you please tell me what could be the reason as I have started the logshipping completely from the beginging.

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2010-03-29 : 16:02:36

If the job is not executing on its own, then something is wrong with its setup. Check that the job is enabled and that the job schedule is enabled.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources