Solved

SQL Transaction log is not being backed up

Posted on 2007-11-22
4
615 Views
Last Modified: 2013-12-01
Hey all,

Got 11d for windows 2003

Got windows 2003, exchange, Adavanced OFO and sql agents on

When the SQL server is being backed up (remote agent used)

Not enabled Advanced OFO.

When backup occurs, SQL database gets backed up but NOT transaction log.,.. so log is steadlily increasing in size an dproperties of db shows it has not been backed up for a while

I can see under the SQL option in the backup setup, that I can change it to 'log file' instead of FULL.

I thought FULL would include TLog and therefore backup etc..
I could enable Advanced OFO.. but considering nothing is open but exchange and sql and other usual like virus scan etc.. thought maybe will be ok as I saw FULL option and now TLog option.

Is this something whereby I must enable Advanced OFO or do I need to do another backup daily for just the TLog (seems odd)

Thanks

R
0
Comment
Question by:roycasella
[X]
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
  • 2
4 Comments
 
LVL 25

Expert Comment

by:imitchie
ID: 20336236
these two together should help

where it states "To select SQL data, click the domain icon or icons that contain the SQL installations, and then click the actual computer icon that contains the SQL installations. If you are using a cluster server, make backup selections from virtual server." They should point out that you need to select the db associated with the ldf you want to backup from the SQL node, not the transaction log file itself.

truncate it
http://www.experts-exchange.com/Storage/Backup_Restore/Q_22826496.html
0
 
LVL 2

Accepted Solution

by:
Neer_Thadarai earned 500 total points
ID: 20525093
The Full backup of SQL database doesn't truncate the SQL logs. Infact Backup Exec Doesn't truncate the SQL logs at all. If you do the log backup for SQL it marks them for truncate but you need to run some SHRINK command from SQL to shrink the log size.
Please refer this Article.
http://support.veritas.com/docs/270043
0
 
LVL 7

Author Comment

by:roycasella
ID: 22214636
Many Thanks

I wanted it to be an all in one process.

Have shrunk manually

Many thanks for your help..

R
0
 
LVL 7

Author Closing Comment

by:roycasella
ID: 31410588
Did not give me the 1x step process,

However, was answered correctly .. hence the A
0

Featured Post

Edgartown IT Case Study

Learn about Edgartown's quest to ensure the safety and security of the entire town's employee and citizen data. Read the case study!

Question has a verified solution.

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

Microservice architecture adoption brings many advantages, but can add intricacy. Selecting the right orchestration tool is most important for business specific needs.
This article shows how to use a free utility called 'Parkdale' to easily test the performance and benchmark any Hard Drive(s) installed in your computer. We also look at RAM Disks and their speed comparisons.
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…
This tutorial will show how to configure a single USB drive with a separate folder for each day of the week. This will allow each of the backups to be kept separate preventing the previous day’s backup from being overwritten. The USB drive must be s…

707 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