Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 150
  • Last Modified:

SQL Server 2005 -- logshipping -- not restore

Hello,
  I setup log shipping for  a DB. The logs are generated and copied . However, in the SSMS, I notice that no logs are applied.
This is the message I see in the viewer
Skipped log backup file. Secondary DB: 'docnumdb', File: 'F:\logshipping\Other\\docnumdb\docnumdb_20140909013558.trn'
2014-09-08 21:37:08.22      Could not find a log backup file that could be applied to secondary database 'docnumdb'.

This is a fresh Log Shipping setup. The previous setup was deleted
Thanks for your help
0
SiemensSEN
Asked:
SiemensSEN
1 Solution
 
Eugene ZCommented:
check if you logship set by using UNC path visible and accessible by secondary server
and insure that you do not have an another trans log backup  for the same  DB

BTW: check 3rd party backup apps: e,g. Idera sqlsafe  has ability t5o set logshipping without copy translog files using the same set  location for backups and restores
0

Featured Post

NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now