Video Screencast Help

Issues on SQL Backup Job even after applying job recomendations

Created: 25 Jan 2014 • Updated: 27 Jan 2014 | 5 comments
This issue has been solved. See solution.

Good Day All.

I' ve followed recomendations from this article.

https://www-secure.symantec.com/connect/forums/how...

But I am still getting SQL Jobs with Warnings: V-79-40960-37914 - Database VCDB is configured to maintain transaction logs...

What else do I need to setup in the SQL Backup Job.

Or will it be better to run a Maintenance Plan on SQL directly?

But I endup doing this what is the point in having a SQL Agent?

Can somebody help me out?

Thanks a lot.

 

Operating Systems:

Comments 5 CommentsJump to latest comment

pkh's picture

Are you on SP3?

For one of these database giving the error message, create a separate backup job with a full backup and log backup and run the two backups. See whether you still get the error message.

You should not use a SQL maintenance plan. Your BE Backup jobs would fail. When did this happen? Did the jobs ever work without the error messages?

nigelg's picture

Hi thanks for answering.

They were working fine but they just started to give this warnings on the SQL Jobs. I also read on another article that the warning starts to appear after 12 full jobs, but this is not the case since they've run like 100+ times already.

The only thing that has changed is the administrator password on the domain which was being used on some jobs.

So I updated credentials and the other jobs File Servers, vmware machine backups are working fine now.

Any ideas?

My Backup Exec version is Backup Exec 2012, Version 14.0 Rev. 1798 (64 Bit)

Installed in a Physical DELL Server Windows 2008 SP2, 64 Bit, with 40 Gb RAM.

Thanks.

 

pkh's picture

Do upgrade to SP3 if you have not already done so.

Create a job including log backup for one of the databases giving the error message and see whether there is still error messages. If there are no error messages, then recreate your job

SOLUTION
nigelg's picture

Ok so I ran a job of only the one database whose transaction log was getting big.

Ran the Full, Incremental 01 and Incremental 02 just like you said in the post and the .ldf file is just 50 Kb in size.

So now I need to add the other databases to this Job that is working fine now, right?

One other question: What happens if I just run Full Backups, the transaction logs will never be cleared?

Thanks a lot.

pkh's picture

So now I need to add the other databases to this Job that is working fine now, right?

Yes.

One other question: What happens if I just run Full Backups, the transaction logs will never be cleared?

Yes.