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


Database Backup Strategy


Database Backup Strategy

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

Group: General Forum Members
Points: 339 Visits: 610
Dear,

Currently we are taking full database backup twice. There is no log backup in our plan. If transaction log grows larger, we just shrink the log file to 1 MB.

We have already implemented snapshot replication. It is scheduled to occur once in a day.


Please let us know the ins and outs of our database backup strategy. If you have better suggestion, please let me know.

Thank in advance.
e4d4
e4d4
SSC-Addicted
SSC-Addicted (467 reputation)SSC-Addicted (467 reputation)SSC-Addicted (467 reputation)SSC-Addicted (467 reputation)SSC-Addicted (467 reputation)SSC-Addicted (467 reputation)SSC-Addicted (467 reputation)SSC-Addicted (467 reputation)

Group: General Forum Members
Points: 467 Visits: 2399
There is no good or bad backup strategy, if it meet yours company RTO (recovery time objective) and RPO (recovery point objective) then it is good. But why you truncate log, and why to 1mb? If there are any dml operations, that cause to grow log, than this is too small amount and bad idea
Suresh B.
Suresh B.
SSCommitted
SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)

Group: General Forum Members
Points: 1974 Visits: 5326
shohelr2003 (11/27/2012)
There is no log backup in our plan. If transaction log grows larger, we just shrink the log file to 1 MB.

You can consider to change the recovery model to "Simple"
Note that file growth and shrinking is bad for performance. You should pre-size the files.
shohelr2003
shohelr2003
Old Hand
Old Hand (339 reputation)Old Hand (339 reputation)Old Hand (339 reputation)Old Hand (339 reputation)Old Hand (339 reputation)Old Hand (339 reputation)Old Hand (339 reputation)Old Hand (339 reputation)

Group: General Forum Members
Points: 339 Visits: 610
Actually transaction log file keeps on growing, so my database file also grows which consumes more disk spaces. To make database size smaller, I shrink log file that serves my purpose.

If I set recovery model SIMPLE then how would I be benefited?

Please clarify me these things.
anthony.green
anthony.green
SSChampion
SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)

Group: General Forum Members
Points: 10188 Visits: 6378
Simple recovery will mark the log as re-usable as soon as a checkpoint happens within the DB which will prevent the need for regular log backups and will stop the log from growing and growing as it sounds like your not doing proper transaction log management.

Managing Transaction Logs - http://www.sqlservercentral.com/articles/Administration/64582/

Also read the stairway to transaction log management section



Want an answer fast? Try here
How to post data/code for the best help - Jeff Moden
When a question, really isn't a question - Jeff Smith
Need a string splitter, try this - Jeff Moden
How to post performance problems - Gail Shaw
CrossTabs-Part1 & Part2 - Jeff Moden
SQL Server Backup, Integrity Check, and Index and Statistics Maintenance - Ola Hallengren
Managing Transaction Logs - Gail Shaw
Troubleshooting SQL Server: A Guide for the Accidental DBA - Jonathan Kehayias and Ted Krueger


SQLSACT
SQLSACT
SSCrazy
SSCrazy (2.1K reputation)SSCrazy (2.1K reputation)SSCrazy (2.1K reputation)SSCrazy (2.1K reputation)SSCrazy (2.1K reputation)SSCrazy (2.1K reputation)SSCrazy (2.1K reputation)SSCrazy (2.1K reputation)

Group: General Forum Members
Points: 2106 Visits: 2931
shohelr2003 (11/27/2012)
Actually transaction log file keeps on growing, so my database file also grows which consumes more disk spaces. To make database size smaller, I shrink log file that serves my purpose.

If I set recovery model SIMPLE then how would I be benefited?

Please clarify me these things.


All inactive VLF's in the transaction log will be truncated upon Checkpoint. Causing the transaction log to stay at a minimum size.

Note: Long running transactions can still fill up your log and and ause it to grow
sanket kokane
sanket kokane
SSC-Addicted
SSC-Addicted (481 reputation)SSC-Addicted (481 reputation)SSC-Addicted (481 reputation)SSC-Addicted (481 reputation)SSC-Addicted (481 reputation)SSC-Addicted (481 reputation)SSC-Addicted (481 reputation)SSC-Addicted (481 reputation)

Group: General Forum Members
Points: 481 Visits: 1022
http://msdn.microsoft.com/en-us/library/ms189275.aspx
http://www.codeproject.com/Articles/380879/About-transaction-log-and-its-truncation-in-SQL-Se

-----------------------------------------------------------------------------
संकेत कोकणे
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