DB13 there is no current database backup

[Former Member]

Hi people,

I´ve scheduled in DB13, the full database backup and transaction log backup. I´ve scheduled of this way:

For example,

friday, Full backup

saturday, transaction log backup

In the log appear this error message:

Duration: 0 hours(s) 0 min(s) 0 sec(s)

Last msg: Executed as user: NT AUTHORITYSYSTEM. BACKUP LOG cannot be performed because there is no current database backup. (Error 4214) BACKUP LOG is terminating abnormally. (Error 3013) DBCC execution completed. If DBCC printed error messages, contact your system administrator. (Error 2528). The step failed.

If i do the backup and after that the transacction log in the same day, all it´s correct.

[Former Member]

Dear Ruben：

You can use SQL Studio to check the DB mode is Full or not, ( Choose the Property of the DB ) and then see the error log of SQL server from SQL Server Agent. Check the detail error message and to find out the root cause.

Arthur

[ganesh_borase2]

HI!

For log backup, you have minimum one full database backup is needed,

after that you can able to take log backup.

as per posted log, I think you had not taken the full database backup.

so first take full backup of database then try to take log backup.

Thanks

[Former Member]

The last friday I maked a Full database backup via DB13, but the following bakcups of transaction log are incorrect, they are showing this message error:

Executed as user: NT AUTHORITY\SYSTEM. BACKUP LOG cannot be performed because there is no current database backup. [SQLSTATE 42000] (Error 4214) BACKUP LOG is terminating abnormally.

[ganesh_borase2]

Hi!

Try to take full backup from SQL server.

Thanks

[Former Member]

Hi Ruben Torres,

You can schedule database backup(full/transaction) by using Microsoft SQL server management studio.

Regards,

[xymanuel]

Hi Ruben,

before you are able to make an Transaction Log Backup, you have to perform one full backup.

I think this is a new DB, and you never did any backup.

Kind regards

Manuel

[former_member189546]

Hello,

Due to the errors, please check Note :

141118 "DB13 - Planning calendar for 46C, 620 and 640 releases"

=================Naming Conversion========

regards,

John Feely

[clas_hortien]

Hi,

are you switching to simple mode over night or at any other time ? This will break the backup chain and you have to do a full backup first before you can do a log backup. You should avoid to switch to simple mode.

Best regards

Clas

[Former Member]

I believe that this option I´ve never changed.

What can to confirm this?

[clas_hortien]

You should see a message in the SQL Server errorlog like:

2011-02-28 11:23:18.48 spid57 Setting database option RECOVERY to SIMPLE for database <YourDBName>.

2011-02-28 11:23:32.47 spid57 Setting database option RECOVERY to FULL for database <YourDBName>.

It might be part of a maintenance plan e.g. for reindexing.

Best regards

Clas