Log file for the secondary database in log shipping grows fast

  • We have a log shipping setup for DR. The transaction log file of the secondary database, which is in restoring mode, is 7 times larger than the data file and is filling up the disk space. What are the possible causes and fixes?

    Note that it is the transaction log file of the secondary database the is growing fast.

    For your information, for the corresponding primary database, we take a Full backup every night and transaction log backup every 30 minutes. The transaction logs are shipped every 1 hour to the secondary database.

    Thanks

Viewing 0 posts

You must be logged in to reply to this topic. Login to reply