Backup to network share fails

fahd

I backup a database to a network share. This used to work fine until a few days ago. Now it wont backup. I get the error below ( from the log )

---

SQL Backup log file
11/2/2006 8:00:00 AM: Backing up Selestia_BI_Staging_Source (full database) to:
\\slprdp01\mibackup$\FULL_(local)_Selestia_BI_Staging_Source_20061102_080000.sqb

11/2/2006 8:00:00 AM: BACKUP DATABASE [Selestia_BI_Staging_Source] TO DISK = '\\slprdp01\mibackup$\FULL_(local)_Selestia_BI_Staging_Source_20061102_080000.sqb' WITH NAME = '<AUTO>', DESCRIPTION = '<AUTO>', ERASEFILES_ATSTART = 2, COMPRESSION = 3, THREADS = 1

11/2/2006 8:00:00 AM: Deleting old backup file: \\slprdp01\mibackup$\FULL_(local)_Selestia_BI_Staging_Source_20061030_080000.sqb
11/2/2006 8:00:02 AM: Thread 0 error:
Error 620: Error writing to backup file(s).
Process terminated unexpectedly. Error code: -2139684860
Thread 0 warning:
Warning 210: Error writing to backup file: \\slprdp01\mibackup$\FULL_(local)_Selestia_BI_Staging_Source_20061102_080000.sqb
Warning: System error code: (Insufficient system resources exist to complete the requested service)

11/2/2006 8:00:02 AM: Server: Msg 3013
BACKUP DATABASE is terminating abnormally.
11/2/2006 8:00:02 AM: Server: Msg 3202
Write on 'SQLBACKUP_003E0A23-2AAE-4495-AB5C-83459B822B62' failed, status = 112. See the SQL Server error log for more

---

Can someone tell me why its failing all of a sudden?

My version of SQL Backup is 4.6.0.815

Regards

Brian Donahue

Hello,

I don't know the exact reason, but it may help to use the MAXDATABLOCK command in your backups to try to prevent this. The 112 error means the disk is full, but on network backups, it can also mean that there are problems with the buffer space. If you add MAXDATABLOCK=524288 to the backup command along with the rest of the parameters after the keyword WITH, this may well get the backups working again.

Please let us know if this helps.

jpassarelli

Has there been any further insight as to what causes this? What are the performance implications setting a different MAXDATABLOCK size? I have found that I can go to a maximum of 3407872 before it breaks, but I didn't see any performance difference at lower values.

Brian Donahue

Hi,

I wouldn't think this setting impacts performance that much; certainly not as much as the difference between backing up to the network as opposed to local disk.

As far as I know, the errors are a result of a lack of non-contiguous memory in the SQL Server process space, preventing SQB from being able to allocate the right buffer size.