Forum Discussion

supportsib2's avatar
supportsib2
Level 5
13 years ago

A database backup completes with exception: V-79-40960-37914

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. This will result in the log growing to fill all available disk space.

 

The Exception is throwing for few database only . why this exception not throwing  for some database only . Iam not taking any log backup

2010
Backup and Recovery
Backup Exec
  • Simon_B_'s avatar
    Simon_B_
    13 years ago

    The reason for this is that not all Databases have full recovery mode configured. Transaction logs are not created when the DB runs in simple recovery mode so you wont get a warning for these DBs. This setting depends on the DBA/the application which creates the DB.

    Also BE will only throw this warning if it detects that no log backup has been performed during the last 12 full backups of this DB (see the TN VJware posted)

4 Replies

Sort By
  • CraigV's avatar
    CraigV
    Moderator
    13 years ago

    Hi,

     

    if you change the DB in SQL Manager to Simple recovery, you won't get this message again. BE will be able to do a full backup of them.

    This isn't a BE issue, but an SQL configuration that needs to be changed.


    Thanks!

  • VJware's avatar
    VJware
    Level 6
    13 years ago

    Take a look at this KB - https://www.symantec.com/docs/TECH126063

  • supportsib2's avatar
    supportsib2
    Level 5
    13 years ago

    My question is  why does it happend for certain database. The exception is not throwing for all the database in the set

  • Simon_B_'s avatar
    Simon_B_
    Level 6
    13 years ago

    The reason for this is that not all Databases have full recovery mode configured. Transaction logs are not created when the DB runs in simple recovery mode so you wont get a warning for these DBs. This setting depends on the DBA/the application which creates the DB.

    Also BE will only throw this warning if it detects that no log backup has been performed during the last 12 full backups of this DB (see the TN VJware posted)