SQL Server Performance

Log Shipping - Copy job not working

Discussion in 'SQL Server Log Shipping' started by saigeeta, May 26, 2009.

  1. saigeeta New Member

    Hi,
    I am trying to set up log shipping between two servers. The secondary database is Read-Only. Everything seems to be working fine for a short time. The transaction log is backed up every 15 minutes and i can see the .trn files in the file share on the primary server. The copy and restore jobs on the secondary servers do not seem to be working. The copy job is reporting as successful and the duration recorded for the copying is either 0 or 1 seconds in the job history. However, as soon as the threshold is met, the monitor reports that the secondary server is out-of-sync. Anyone know why the copy job isn't working correctly? Anyone come across this problem before and know how to resolve it?
    Thanks in advance.
  2. satya Moderator

    Can you check the error log on both SQL Servers to match the backup & restore timings to ensure the log shipping process is working or not.
    As a test you may try get the database on secondary server by using RESTORE DATABASE <DBNAME> WITH RECOVERY that can confirm whether the transactions are copied.
    Also confirm the service pack levels between Primary & Secondary servers.
  3. ghemant Moderator

    [quote user="saigeeta"]The copy and restore jobs on the secondary servers do not seem to be working. The copy job is reporting as successful and the duration recorded for the copying is either 0 or 1 seconds in the job history.[/quote]
    Check the error log for the exact error message, also check the what was the last restored t-log and see (to get the idea about if it is sync or out-sync time)
    If the copy t-log file to secondary server failes, it should be some issue with network(may be intermittently, try to re-run the copy t-log job); and/or ensure that there is no change in the ntfs/file share permission happen for the shared folder

Share This Page