SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


TLOG GROWING VERY LARGE


TLOG GROWING VERY LARGE

Author
Message
shohelr2003
shohelr2003
Old Hand
Old Hand (333 reputation)Old Hand (333 reputation)Old Hand (333 reputation)Old Hand (333 reputation)Old Hand (333 reputation)Old Hand (333 reputation)Old Hand (333 reputation)Old Hand (333 reputation)

Group: General Forum Members
Points: 333 Visits: 610
Hi,

I have implemented mirroring (high safety without automatic failover) and replication (snapshot replication) simaltaneously on the same database. But my tlog started growing very large which cause backup file to be grown as well. I take full backup everyday once.

What can I do to prevent tlog from growing? Is there any inconsistency with my backup plan?

Please help me to sort out the problem.

Regards,
Akbar
GilaMonster
GilaMonster
SSC Guru
SSC Guru (87K reputation)SSC Guru (87K reputation)SSC Guru (87K reputation)SSC Guru (87K reputation)SSC Guru (87K reputation)SSC Guru (87K reputation)SSC Guru (87K reputation)SSC Guru (87K reputation)

Group: General Forum Members
Points: 87073 Visits: 45267
shohelr2003 (12/22/2012)
I take full backup everyday once.


That's not enough.

Please read through this - Managing Transaction Logs

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass


shohelr2003
shohelr2003
Old Hand
Old Hand (333 reputation)Old Hand (333 reputation)Old Hand (333 reputation)Old Hand (333 reputation)Old Hand (333 reputation)Old Hand (333 reputation)Old Hand (333 reputation)Old Hand (333 reputation)

Group: General Forum Members
Points: 333 Visits: 610
That's not enough.


Please suggest me what can I do to prevent tlog from growing. In addition to, I need your support to develop an effective backup plan. What activities should my backup plan include?

I am also reading your two links.

Please help me.
Ravi SQL
Ravi SQL
Ten Centuries
Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)

Group: General Forum Members
Points: 1018 Visits: 577
Taking full backup once in a day is not enough, you need to take backup of transaction log as well to truncate the log file. Once the transaction log backup is taken, the inactive portion of the log (all its log records) will be captured in the log backup.

Link given by Gail Shaw is good one to understand how the transaction log works.

Regards,
Ravi.
shohelr2003
shohelr2003
Old Hand
Old Hand (333 reputation)Old Hand (333 reputation)Old Hand (333 reputation)Old Hand (333 reputation)Old Hand (333 reputation)Old Hand (333 reputation)Old Hand (333 reputation)Old Hand (333 reputation)

Group: General Forum Members
Points: 333 Visits: 610
Imagine that I take one full backup at the beginning of the day and later on take four log backups at two hours interval and again take another full backup at the end of the day.

How is this backup plan? Please suggest me.
GilaMonster
GilaMonster
SSC Guru
SSC Guru (87K reputation)SSC Guru (87K reputation)SSC Guru (87K reputation)SSC Guru (87K reputation)SSC Guru (87K reputation)SSC Guru (87K reputation)SSC Guru (87K reputation)SSC Guru (87K reputation)

Group: General Forum Members
Points: 87073 Visits: 45267
shohelr2003 (12/22/2012)
That's not enough.


Please suggest me what can I do to prevent tlog from growing. In addition to, I need your support to develop an effective backup plan. What activities should my backup plan include?


Please read the articles I referenced.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass


GilaMonster
GilaMonster
SSC Guru
SSC Guru (87K reputation)SSC Guru (87K reputation)SSC Guru (87K reputation)SSC Guru (87K reputation)SSC Guru (87K reputation)SSC Guru (87K reputation)SSC Guru (87K reputation)SSC Guru (87K reputation)

Group: General Forum Members
Points: 87073 Visits: 45267
shohelr2003 (12/23/2012)
Imagine that I take one full backup at the beginning of the day and later on take four log backups at two hours interval and again take another full backup at the end of the day.

How is this backup plan? .


Does it allow you to restore the DB and meet your RPO and RTO requirements? If so, it's fine. If not, it's inadequate.
There's no one-size-fits-all backup plan, it has to be tailored to meet the requirements for recovery for that DB.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass


Joy Smith San
Joy Smith San
Hall of Fame
Hall of Fame (3.2K reputation)Hall of Fame (3.2K reputation)Hall of Fame (3.2K reputation)Hall of Fame (3.2K reputation)Hall of Fame (3.2K reputation)Hall of Fame (3.2K reputation)Hall of Fame (3.2K reputation)Hall of Fame (3.2K reputation)

Group: General Forum Members
Points: 3198 Visits: 3200
Taking full backups do not truncate the logs, log backup does. I have faced this issue sometime back and log backups at appropriate intervals resolved the issue as well. You can check 'log_reuse_wait_desc' in sys.databases. Go through the link Gilas has mentioned, it will help to identify and solve your issue.
shohelr2003
shohelr2003
Old Hand
Old Hand (333 reputation)Old Hand (333 reputation)Old Hand (333 reputation)Old Hand (333 reputation)Old Hand (333 reputation)Old Hand (333 reputation)Old Hand (333 reputation)Old Hand (333 reputation)

Group: General Forum Members
Points: 333 Visits: 610
Thanks All. My problem has been solved. Now I take log backup regularly. It prevents tlog to be grown abnormally.

Special thanks to Gail Shaws' links.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search