Hi, We have one of the databases on SQL Server 2005 Enterprise edition. Its around 500 GB and is configured for mirroring as well as log shipping.Mirroring is configured through SQL Server database properties where as log shipping is happening through a 3rd party tool by redgate called SQL Backup.There are jobs to restore the logs on the logshipping server. We have a challenge in this setup. The log file on the primary server is growing enormously high. We are not able to shrink the log file.We cannot truncate it as well, because log shipping is also in effect. When ever log grows high, we are breaking the mirroring and logshipping, truncating the log and shrinking, then restore the full backup, differentials and log backups on mirrored and logshipping servers and then reconfiguring them. Client is unhappy that we are breaking the mirror quiet frequently. Please help me out to find a solution to maintain the size of the log file on the primary database.