Unable to execute backup LOG because there is currently no database backup.

If you encounter the following error:

Msg 4214, Level 16, State 1, line 1th

Unable to execute backup LOG because there is currently no database backup.

Msg 3013, Level 16, State 1, line 1th

BACKUP LOG is terminating abnormally.

More unfortunate is to do tail-log backup!! The mood at this time is heavy and complex.

The hint is not wrong, although the recovery model of the database is now full, but in a moment the database recovery mode is switched, such as simple. In this case, even if there is a full database backup in the previous fully mode, it is still useful to do a tail-log backup that will also cause this error. Of course, it is clear that simple can not do tail-log backup.

Therefore, if it is possible and you want the database to use BACKUP LOG with no_truncate, then keep the recovery mode of the database in full state. Believe me, if the log grows too large situation, also do not easily go to simple state, when it is necessary to do a log backup.

--Turn: http://blog.csdn.net/kufeiyun/article/details/14231031

Unable to execute backup LOG because there is currently no database backup.