Competition: What’s your favorite Redgate tool? Enter now.

Transaction Log Backup Failing

ToehoToeho Posts: 73
edited May 12, 2008 3:54AM in SQL Backup Previous Versions
I have a condition where a transaction log backup is failing for one database with the errors below. It seems to be fussing about not having a full backup but I have verified that the nightly full backup is successfull. The log backups have been running successfull untill the 2 days ago. Any ideas??

5/9/2008 6:05:02 AM: Backing up TRN (transaction log) to:
5/9/2008 6:05:02 AM: H:\Backups\TRN_05092008_060502_LOG.sqb

5/9/2008 6:05:02 AM: BACKUP LOG [TRN] TO VIRTUAL_DEVICE = 'SQLBACKUP_78285926-7824-4E9E-9BEC-7F2BAE49E191' WITH BUFFERCOUNT = 6, BLOCKSIZE = 65536, MAXTRANSFERSIZE = 1048576, NAME = N'Database (TRN), 5/9/2008 6:05:02 AM', DESCRIPTION = N'Backup on 5/9/2008 6:05:02 AM Server: SWCSAQTS Database: TRN'

5/9/2008 6:05:32 AM: VDI error 1010: Failed to get the configuration from the server because the timeout interval has elapsed. Check that the SQL Server instance is running and that you have the SQL Server System Administrator server role; or try increasing the value of the VDITimeout registry setting in HKEY_LOCAL_MACHINE\SOFTWARE\Red Gate\SQL Backup\BackupSettingsGlobal\[InstanceName]
5/9/2008 6:05:32 AM: SQL error 3013: BACKUP LOG is terminating abnormally.
5/9/2008 6:05:32 AM: SQL error 4214: BACKUP LOG cannot be performed because there is no current database backup.
5/9/2008 6:05:32 AM:
5/9/2008 6:05:32 AM: Memory profile
5/9/2008 6:05:32 AM: Type Maximum Minimum Average Blk count Total
5/9/2008 6:05:32 AM:





5/9/2008 6:05:32 AM: Commit 32063488 4096 207085 21723 4498522112
5/9/2008 6:05:32 AM: Reserve 3154051072 4096 164096 20661 3390402560
5/9/2008 6:05:32 AM: Free 6872986222592 4096 30620919972 287 8788204032000
5/9/2008 6:05:32 AM: Private 3154051072 4096 185731 41917 7785304064
5/9/2008 6:05:32 AM: Mapped 1585152 4096 140361 56 7860224
5/9/2008 6:05:32 AM: Image 32063488 4096 232993 411 95760384
5/9/2008 6:05:32 AM:

Comments

  • peteypetey Posts: 2,358 New member
    5/9/2008 6:05:32 AM: SQL error 3013: BACKUP LOG is terminating abnormally.
    5/9/2008 6:05:32 AM: SQL error 4214: BACKUP LOG cannot be performed because there is no current database backup.
    The error above suggests that the recovery model was changed, or a transaction log backup was ran with the NO_LOG/TRUNCATE_ONLY option (and you were using SQL 2005).
    Peter Yeoh
    SQL Backup Consultant Developer
    Associate, Yohz Software
    Beyond compression - SQL Backup goodies under the hood, updated for version 8
Sign In or Register to comment.