June 2, 2010 at 5:29 am
Hi all
Currently we have a mirrored setup that has no backup plan in place. As such the log files have grown to excess now, as such I am in the process of having to stop the mirror to backup and shrink the T-logs. That in itself is something I have not done before and I am looking forward to trying to get this backup and working.
My question really was once I have this working again, do you need to backup the T-logs on the principle only or do you also need to backup the logs on the mirror in order to keep the file sizes down?
Thanks
June 2, 2010 at 7:24 am
On the mirror database you don't need to backup the transaction log.
You can only back up the transaction log on the principal database.
If the roles switch, the rule is the same, backup the principal log. When the roles switch, the log sequence numbers stay the same, so you can backup to the same log backup file if you so desire.
June 2, 2010 at 8:19 am
Ah great stuff thanks
June 2, 2010 at 10:27 am
The mirror log files should not be growing. Are they still growing?
June 3, 2010 at 2:12 am
Well I will monitor and let you know. The scenario was that I just logged onto the server and saw the T-logs at 56GB for a database that was 20MB. Perhaps the mirror was restored with the transaction log of that size in the first place.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply