April 26, 2010 at 8:49 am
Hi all,
I have a database which is 86Gb in size and every 10 minutes we log ship to our DR environment which is in a remote location 50 miles away. The transaction logs on the database at the DR environment have grown to 43Gb and I am now out of disk space on that particular partition.
I firstly attempted to shrink the log file but received the error that I cannot do this when a database is recovering. Then, thought I would move the log file to another drive which has more space using the usual detach > move > reattach commands. I detatched OK, copied OK, but can't now reattach because of a "Cannot attach a database that was being restored". Dammit.
Firstly, should the log file in the destination database be growing like it has been? It doesn't make sense to me for the log file in the destination DB to be set to 'Full Recovery' - the log file in the source database is only 112Mb.
Secondly, am I now forced to reinitialize the TxLog shipping by copying another 86Gb database to our DR location or is there a way out of this mess?
Thanks in advance,
Martin
April 30, 2010 at 11:12 am
Are you backing up your transaction logs at your DR environment?
January 23, 2016 at 10:05 pm
I have a similar problem. 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. What are the possible causes and the 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 Full backup every night and transaction log backup every 30 minutes.
Thanks
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply