MSSQL Backups Fail After Restore

[GregE]

I restored a database to an alternate server using TDP. Now, my backups on the original server are failing with the following:

02/11/2010 20:00:29 Backup of DB1 failed.
02/11/2010 20:00:29 ACO5422E Received the following from the MS SQL server:
02/11/2010 20:00:29 [Microsoft][ODBC SQL Server Driver][SQL Server]BackupVirtualDeviceSet::SetBufferParms: Request large buffers failure on backup device 'TDPSQL-00001B74-0000'. Operating system error 0x8007000e(Not enough storage is available to complete this operation.).
02/11/2010 20:00:29 [Microsoft][ODBC SQL Server Driver][SQL Server]A nonrecoverable I/O error occurred on file "TDPSQL-00001B74-0000:" 995(The I/O operation has been aborted because of either a thread exit or an application request.).
02/11/2010 20:00:29 [Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP LOG is terminating abnormally. Microsoft SQL-DMO (ODBC SQLState: 42000) (HRESULT:0x80044722)
02/11/2010 20:00:33 ACO5436E A failure occurred on stripe number (0), rc = 428
02/11/2010 20:00:33 ACO5407E The SQL server aborted the operation.

"Enough storage" is not the problem. There is plenty of disk on this server. I have never restored an SQL database until last week, and again this week. Both times, I restored to an alternate server. And both times, backups taking place after that began failing. I run log backups all day, every hour. Oddly, 2 worked this morning, with two failures in the previous hours, then after the 2 successes, it has failed all day. I would not think a restore to another machine would have anything to do with this, but I question it because failures happened after both restore attempts. Does TDP SQL do anything that I'm unaware of that could be causing this?

 

[zsoltesz]

I think, the "Enough Storage" is related to the TSM server. When you use log or differential backups, the tdpsql has to estimate the amount of storage space suitable for that backup. If the estimation is wrong, the backup will fail.
From the aspect of SQL Server it seems to not enough storage.

 

[GregE]

Ok, I was kind of thinking that too. So, these backup to TSM diskpool, and there is no storage issue there either, so I think the error is not really what it says. But all of my SQL backups continue to fail. Log backups and full, I'm not getting any successes with any of them since the 2 successes that happened after my restore attempt nearly 2 days ago. I find it hard to believe TDP SQL simply reading data from TSM for restore has effected the backups of the production/source databases.

 

[GregE]

Ok I got it working. I still don't know why it only started acting like it did AFTER my restore attempt, but anyway..

I changed the tdpsql.cfg parameters

SQLBUFFers, was 0 (lets SQL decide). Changed to 2.
SQLBUFFERSIze, was 1024. Changed to 512.

We're moving off of this server very soon due to CPU/memory being slammed, so I'm sure this had nothing to do with restore, it just was perfect timing to look like it.