Transaction log backup Failed

Question

Transaction log backup Failed

Elaya-535392

Old Hand

Points: 378
More actions
March 5, 2009 at 11:50 pm

#201035

Hi,
I have found some error messages
BACKUP failed to complete the command BACKUP LOG [DBName] TO DISK = N'D:\mssql\Backup\DBName_Log_200704120400.TRN' WITH INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
Source Spid 91
Downgrading backup buffers from 960K to 64K
Source Spid 107
Error: 515, Severity: 16, State: 2
Windows Application Event Log Entry:
Event ID:17055
3041 :
BACKUP failed to complete the command BACKUP LOG [DBname] TO DISK = N'D:\MSSQL\Backup\DBName _tlog_200704130800.TRN' WITH INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
Version:
Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
Drive Space - 90 GB
Need some helps to resolve this issue permanatly

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply

John H Marsh SSChampion Points: 11671 More actions · Answer 1

Hello,

There are a couple of threads around that suggest it may be as a result of memory issues on your server. May be take a look at these:-

http://social.msdn.microsoft.com/Forums/en-US/sqldatabaseengine/thread/2689fb21-f3c8-4754-b0d0-09b91886c8ea/

http://support.microsoft.com/kb/904804/en-us

http://www.sqlservercentral.com/Forums/Topic605571-24-1.aspx

Regards,

John Marsh

www.sql.lu
SQL Server Luxembourg User Group

Elaya-535392 Old Hand Points: 378 More actions · Answer 2

Hi John,

We have truncated the log & after that restarting our jobs, now the Transaction Log Backup running successfully

Can you please tell me, this is the right solution or we need to take any actions before occuring this same probs in future.

Also please let me know, how the transaction log is happening

when our data is 14 gb & log is 2 gb.

MANU-J. SSC-Dedicated Points: 31126 More actions · Answer 3

Are there any memory related errors in sql server error log?

MJ

amarnath_sk Right there with Babe Points: 740 More actions · Answer 4

amarnath_sk

Right there with Babe

Points: 740

March 9, 2009 at 4:59 am

#955867

Better to take full backup after truncating log file.

Elaya-535392 Old Hand Points: 378 More actions · Answer 5

Hi Manu,

Yes, but it is OS level.

one of our server we increased the virtual memory in operating system, now the log backup is working fine.

But today we are getting the same log back up error in our another server system. So here also we are planning to increase the memory size.

Can you please reply me this is the right solution or we need to take any other steps.

In sql error log, we are getting the below meesage:-

Downgrading backup buffers from 960K to 64K

MANU-J. SSC-Dedicated Points: 31126 More actions · Answer 6

As suggested by John go thru this(http://support.microsoft.com/kb/904804) KB article and you will get your answer.

This error message indicates that the contiguous virtual memory is either insufficient or is too fragmented for the computer to successfully perform a backup. Contiguous virtual memory that is insufficient or that is fragmented could lead to performance problems when you try to back up the database.

MJ

Glenn Dorling SSCertifiable Points: 7878 More actions · Answer 7

A reboot of the server will resolve the problem in the short term, but you'll get the same problem again sooner rather than later.

We've found we've had to add the MAXBUFFERSIZE option to our backup commands on some servers where the backups are large and/or being made to more than one file. MAXBUFFERSIZE can be 65536 (64k) to 1048576 (1GB). We found we had to drop it to 262144 (256k) to get it to work on one server, which increased the backup time by ~10%, and to 65536 on another server.