|
midnight
Starting Member
1 Posts |
 Posted - 02/07/2013 : 22:02:00
|
Our company has never backed up the transaction log file, and is now about 143 gig, with about 35 gig left on the drive, and I have to get this under control. We do a full db backup every night. I would like to start a log file backup about every two hours during business hours to truncate the log file and limit the growth, and after a bit, re-size the log file. I will be doing this through Management Studio. I will be backing this up onto another drive into a backup folder. My question is regarding the overwrite media options. Do I keep appending to the existing backup set? Do we create new files for every time the log file gets backed up, and if so, how do we do this. I guess I'm asking for the proper way to set this up, and make a restore (if needed) as easy as possible. We are on SQL 2008R2.
Any help or direction would be greatly appreciated to get this on track. |
|
|
jackv
Flowing Fount of Yak Knowledge
United Kingdom
1795 Posts |
Posted - 02/10/2013 : 02:02:37
|
If these log backup files are required for Recovery and are part of the Service Level agreement , have you thought of keeping the log backup files in a similar repository to the FULL backups.
I'm thinking about situations where there is a server failure and you need to recover to a point in time
Jack Vamvas
--------------------
http://www.sqlserver-dba.com |
 |
|
Transaction Log Backup
