May 1, 2012 at 3:53 pm
We are using Red-Gate Backup tool for Log Shipping. I have noticed that the log file is increasing in size and became too large on the secondary server. Is there a way to truncate it? The DB on the secondary server is in Standby mode.
I'll appreciate for any advice.
Nadya
May 1, 2012 at 4:03 pm
Are the filenames for the logs on both servers the same?
I'm a DBA.
I'm not paid to solve problems. I'm paid to prevent them.
May 2, 2012 at 11:52 am
Yes, file names are the same and sizes are the same. Red Gate has answered that we need to break the log shipping and restart from the beginning once more. In our case it is not good solution because database is large and it takes many hours to restore it on the secondary server.
The only way is to truncate log file on the primary server. But I am afraid that Log Shipping could get broken.
Thank you for the response,
Nadya
May 2, 2012 at 1:17 pm
If your log file is increasing in size despite taking log backups, perhaps you need to increase the frequency of the log backups.
Reindex jobs are also a frequent cause of log growth.
A shrink of the log on the primary will be reflected on the standby database. Shrinking does not break log shipping.
If the log file is too big for the secondary but ok on the primary, you may need to ensure drive sizes are the same on both servers.
---------------------------------------------------------------------
May 2, 2012 at 1:23 pm
Thank you very much for the advise. I am at about to test the log file truncating on the primary server.
Nadya
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply