Video Screencast Help

How to create a second backup job to clear the transaction logs

Created: 25 Apr 2013 • Updated: 02 May 2013 | 2 comments
This issue has been solved. See solution.

V-79-40960-37914 - Database wsrm is configured to maintain transaction logs.  Transaction log backups are not being performed.  This will result in the log growing to fill all available disk space.  Regular log backups should be scheduled or the database should be changed to the simple recovery mode.

I have read that creating a second SQL backup will take care of the transaction logs. The database is MICROSOFT##SSEE
a Windows dB that is created if SQL is not on the server when loading Backup Exec. TIA Any methods that will help clear the eror would be nice. I am doing a full system backup when this happens. I have the SQL License that costs extra with Backup Exec 2012.

Operating Systems:

Comments 2 CommentsJump to latest comment

Sush...'s picture

Hello there,

   Please refer to the following technote

http://www.symantec.com/docs/TECH126063 : A database backup completes with exception: V-79-40960-37914 - Database DATABASENAME is configured to maintain transaction logs. Transaction log backups are not being performed

 

So basically what you have to do is create another backup job for that server and select only the SQL databases and then select the type of SQL backup as Log backups.

 

Thanks,

-Sush...

Hope this piece of Information Helps you... and if it does then mark this response as Solution....!!!

pkh's picture

BE 2012 does not allow you to run a log backup on its own.  You would have to create a job to do a database backup of this problem database and then add an incremental job which specifies log backup.

BE 2012 - edit job properties.png

BE 2012 - add job.png

BE 2012 - SQL log backup.png

SOLUTION