SQL Server Performance

Log Shipping failing due to large trn files

Discussion in 'SQL Server Log Shipping' started by Jack Vamvas, Mar 4, 2008.

  1. Jack Vamvas Member

    SQL Server 2000 Enterprise Edition
    At certain times of the day the transaction log files created are to large to be handled by the Log Shipping process. Due to large batch jobs.
    As a consequence I have to reinitialize the Log Shipping process
    -Primary Server - the Transaction Log Back Up job runs every 5 minutes from 00:00:00 to 23:59:59
    -Secondary Server : The Transaction Log Copy Job - runs every 5 minutes from 00:01:00 to 23:59:59
    -Secondary Server : The Transaction Log Restore Jobs - run every 5 minutes from 00:02:00 to 23:59:59
    It is necessary to keep the Log Shipping process 24 hrs a day , does any one have any strategies which may assist in dealing with very large .TRN files in
    the log shipping context ?
  2. satya Moderator

    What is the frequency of transaction log backup?
  3. Jack Vamvas Member

    Every 5 minutes ,
  4. Jack Vamvas Member

    Satya , I also forgot to mention - I've reset everything to 15 minutes and seem to run through the night OK. But I am still interested in any strategies related to log shipping
  5. satya Moderator

Share This Page