Video Screencast Help

SQL Backups

Created: 12 Mar 2014 | 2 comments


We have various SQL database to backup, and have just added some more (SAGE install). The first backup of the SAGE dbs has resulted in an exception about the log files. All of our dbs are set to Simple recovery model, except SAGE, which is set to full. So that explains the exception.

What is the recommended Backup Exec (BE) strategy for Full reovery model SQL backups - I see that log backups have to be done after the full backup, but how can we manage that in practive? Can you start a job on completion of another one?

Does that mean we will always get the exception, or does BE know a log backup has been taken?

How often should log backups be done? Once per day or multiple times?

Why, in practice, would you choose Full recovery model. I know what it offers, but with enterprise disk reliability, is there a need for Full recovery model? Does it offer more than just allowing for a failed log volume (we have logs on separate volume to dbs)

At present, we do 1 full backup of SQL dbs every night.


Operating Systems:

Comments 2 CommentsJump to latest comment

sidd3009's picture


You might want to refer to the following article written by PKH and configure Log Backups:

One more thing that I'd suggest is to create a separate backup job for the databases which run with Simple Recovery Model.


Siddhant Saini
Senior Technical Support Engineer, Symantec Corporation

pkh's picture

With transaction logs, you can do point-in-time restores. Also, there are some applications that needs transaction logs, so don't switch to simple recovery mode without checking with the application owner

My article referenced earlier is for BE 2012. For BE 2010, you need to create a separate log backup job to ensure the log. Once the log is truncated then you will not get the error message.

You can see my blog below on how to chain your jobs