Moderator: Chris Auckland
petey wrote:It appears that SQL Server has run out of large memory blocks to allocate to the backup/restore process. If you run the sqbmemory extended stored procedure on both servers, what is the result that's displayed e.g.
petey wrote:It appears that there is adequate free memory at this point. Do the backups and restores currently work?
petey wrote:I would suggest monitoring the memory usage pattern over time, with and without SQL Backup running. The numbers to look out for are the 'free' memory values.
petey wrote:When a backup fails due to the lack of a large enough configuous block of free memory, SQL Backup automatically retries the backup using smaller MAXTRANSFERSIZE values, until it hits the minimum of 65536 bytes. Even this does not seem to work in your case.
Could you pls check the SQL Backup log file for the failed backup, to see if the backups were re-attempted, and if so, how many times?
Also, are you backing up to multiple files?
petey wrote:Could you pls post the values for 'Free' memory for the first and last failures? Thanks.
petey wrote:Start Profiler, filter on the application name SQBCoreService.exe. Then start a backup using SQL Backup. You should see 2 backup commands, one identical to the one you issued, and another similar to the first, but using VIRTUAL_DEVICE = ... instead of DISK = ...
Users browsing this forum: No registered users and 0 guests