(Message 4035) BACKUP LOG cannot be performed because there is no current database backup

Hi everyone, last time I got a disk space issue, after purging some data and backup, I tried to run the biztalk jobs. But the DTA backup job  failed with this error

Executed as user: xxx. Processed 3233 pages for database ‘BizTalkDTADb’, file ‘BizTalkDTADb_log’ on file 1. [SQLSTATE 01000] (Message 4035) BACKUP LOG successfully processed 3233 pages in 0.400 seconds (63.133 MB/sec). [SQLSTATE 01000] (Message 3014) Processed 2 pages for database ‘BizTalkMgmtDb’, file ‘BizTalkMgmtDb_log’ on file 1. [SQLSTATE 01000] (Message 4035) BACKUP LOG successfully processed 2 pages in 0.008 seconds (1.342 MB/sec). [SQLSTATE 01000] (Message 3014) Processed 13829 pages for database ‘BizTalkMsgBoxDb’, file ‘BizTalkMsgBoxDb_log’ on file 1. [SQLSTATE 01000] (Message 4035) BACKUP LOG successfully processed 13829 pages in 1.118 seconds (96.631 MB/sec). [SQLSTATE 01000] (Message 3014) Processed 1 pages for database ‘BizTalkRuleEngineDb’, file ‘BizTalkRuleEngineDb_log’ on file 1. [SQLSTATE 01000] (Message 4035) BACKUP LOG successfully processed 1 pages in 0.022 seconds (0.044 MB/sec). [SQLSTATE 01000] (Message 3014) Processed 1 pages for database ‘SSODB’, file ‘SSODB_log’ on file 1. [SQLSTATE 01000] (Message 4035) BACKUP LOG cannot be performed because there is no current database backup. [SQLSTATE 42000] (Error 4214) BACKUP LOG is terminating abnormally. [SQLSTATE 42000] (Error 3013) BACKUP LOG successfully processed 1 pages in 0.018 seconds (0.271 MB/sec). [SQLSTATE 01000] (Error 3014). The step failed.

To summarize, the job could not find the full backup which is the reference for one day (but  does exist on disks).

Fortunately, it appends on test environnement. So I decide to clear all Backup and force the job to create a new full one. Here is the process:

  • First delete all biztalk Backup
  • Connect Sql server management studio, to  the BizTalk management Database
  • Execute the stored procedure [dbo].[sp_ForceFullBackup]
  • Next re-run the job, a newly ful backup is created

This workaround is effective, but in production environnement, you must keep an eye on the backup disk and prevent any empty space to avoid this problem.

Publicités

Laisser un commentaire

Choisissez une méthode de connexion pour poster votre commentaire:

Logo WordPress.com

Vous commentez à l'aide de votre compte WordPress.com. Déconnexion / Changer )

Image Twitter

Vous commentez à l'aide de votre compte Twitter. Déconnexion / Changer )

Photo Facebook

Vous commentez à l'aide de votre compte Facebook. Déconnexion / Changer )

Photo Google+

Vous commentez à l'aide de votre compte Google+. Déconnexion / Changer )

Connexion à %s