Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people, just like you, are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
Solved

SQL 2005 logs not flushing and taking up space

Posted on 2009-05-05
4
713 Views
Last Modified: 2013-12-01
Hi Guys,
I've got an SQL database that takes up what little space we have on the drive, we run the shrink command on it and manage to get back about 7GB each time but we also have Symantec Backup Exec installed with the SQL agent and were under the impression that this would flush the logs when the backup had completed.
Does having the database in Simple or Full mode affect this and if not then what could be going wrong or what can we do ?

Thanks
0
Comment
Question by:Netexperts
  • 2
  • 2
4 Comments
 
LVL 23

Expert Comment

by:Rahul Misra
ID: 24303314
Backup Exec does not Flush the logs when you perform a FULL DATABASE BACKUP
Run a backup of the LOGS

Backing up SQL transaction logs
http://support.veritas.com/docs/300158 

Setting backup options for SQL
http://support.veritas.com/docs/310364 




Also check the following for a better understanding of how SQL backups work

How do the Simple, Bulk-logged, and Full Recovery modes in Microsoft SQL 2000  apply to Backup Exec?
http://support.veritas.com/docs/236600 

The size of the log file does not decrease when performing a backup operation of  Microsoft SQL although the "truncate log on checkpoint" option was selected
http://support.veritas.com/docs/233168 

After performing "Log - Backup Transaction Log" of SQL databases using Backup  Exec, the size of the physical log file remains unchanged.
http://support.veritas.com/docs/270043 

0
 
LVL 1

Author Comment

by:Netexperts
ID: 24304072
Thanks for that but the information isn't that clear. Does this mean that i need to setup a seperate Backup Exec job to just backup the Transaction logs ?

Thanks
0
 
LVL 23

Accepted Solution

by:
Rahul Misra earned 500 total points
ID: 24304156
Yes, as the TRUNCATE option works only for LOG backups not when you backup the databases
Also when you run the log backup the LOGS are marked for TRUNCATION and then deleted by SQL and not BEWS
Check the articles for more information on setting up LOG BACKUP
0
 
LVL 1

Author Closing Comment

by:Netexperts
ID: 31577952
Makes sense now.
Many Thanks
0

Featured Post

Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In this article we will get to know that how can we recover deleted data if it happens accidently. We really can recover deleted rows if we know the time when data is deleted by using the transaction log.
Microsoft will be releasing the Windows 10 Creators Update in just a matter of weeks. Are you prepared? Follow these steps to ensure everything goes smoothly and you don't lose valuable data on your PC.
This tutorial will walk an individual through the steps necessary to install and configure the Windows Server Backup Utility. Directly connect an external storage device such as a USB drive, or CD\DVD burner: If the device is a USB drive, ensure i…
This tutorial will show how to configure a new Backup Exec 2012 server and move an existing database to that server with the use of the BEUtility. Install Backup Exec 2012 on the new server and apply all of the latest hotfixes and service packs. The…

839 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question