[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 631
  • Last Modified:

SQL 2005 and Backup Exec causes Log File Problems

I have a microsoft sql 2005 x64 database(Windows 2003 x64 as well) which is extremely active and has grown to over 800gb in size in the past 60 days.  We have our catalogs, logs, and database on 3 separate disks.  The log disk is 65gb and in the past two years this has been more than enough space.  We use simple logging in the database.

However, we created this new database two months ago and when using Backup Exec 11d, the backup process causes the log files to grow excessively filling up the disk.  This of course fails the backup job and causes havoc with the database itself.

Prior to the database getting so large, we were able to use sql backup and successfully backup to disk with no excessive log file growth.

We suspect that the issue is the volume of transactions that is being pumped through the database between backup cycles.  However, we cannot find any known issues and the Backup Exec support team is less than helpful.

We are trying to determine what causes the excessive log file growth...or any log file growth and any thoughts on what would fix this issue.


0
lstanke
Asked:
lstanke
  • 4
  • 2
1 Solution
 
Kevin3NFCommented:
How long does it take to backup that db?  Full, or Diff?
0
 
Kevin3NFCommented:
And have you considered using something like Red Gate SQL Backup or Litespeed to increase the speed and reduce the size of the backups?  I've seen Litespeed work really well on a 2TB database with massive activity
0
 
lstankeAuthor Commented:
I cannot change to another backup solution at this time.  It is controlled by my colo facility.

Full or differential, should be the same for sql databases.  It takes about 4 hours on the few times it does work.

We suspect its the high volume of transactions going on and Backup Exec cant get access to the disks in a timely fashion.
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
Kevin3NFCommented:
No...full and diff should not be the same time, unless the majority of the data is being changed.

The T-log (.ldf) will grow during this backup...not a thing you can do about it.  If you need confirmation that it is transactions, set up a server side trace to capture that activity.  Don't use Profiler, as this will consume resources you don't sound like you have available to spare.
0
 
lstankeAuthor Commented:
Why does the transaction log grow during the backup?   And why would it grow over 500gb trying to backup a 1tb database?
0
 
Kevin3NFCommented:
During the backup, transactions continue to happen.  They go into the T-Log.  T-log purging is not ahppening until the backup completes.  Is it possible you have that much activity in 4 hours?  Every Insert, Update and Delete counts.
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now