Comments
Sort by recent activity
petey wrote:
Could you pls post the values for 'Free' memory for the first and last failures? Thanks.
For the 1st time the backup needs to retry, the Free memory is:
Type Maximum Minimum Average Blk count Total
Free 5550080 4096 28891 4166 120360960
Then for the last time where backup is failing and we need to reboot the machine:
Type Maximum Minimum Average Blk count Total
1st retry:
Free 196608 4096 27162 4413 119869440
4th retry:
Free 196608 4096 27162 4413 119869440 / comments
petey wrote:
Could you pls post the values for 'Free' memory for the first and last failures? Thanks.
For the 1st time the backup needs to retry, the Free memory is:
Type Maximum ...
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?
Thanks.
I just took a look at the SQL Backup log files and it looks like it gradually comes to a halt. For example, when the problem first occurs, the backup fails, but it succeeds on the 1st retry. It continues like this for like an hour. Then the backup starts failing on the 1st retry and will succeed on the 2nd retry. So and so forth until it fails for all 4 retries.
And we are not backing up to multiple files. / comments
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 hit...
petey wrote:
It appears that there is adequate free memory at this point. Do the backups and restores currently work?
Yeah, they work and then over some period time I get the errors above. It seems like it degrades over time and it renders my production DB server useless. This has happened twice over the past month. / comments
petey wrote:
It appears that there is adequate free memory at this point. Do the backups and restores currently work?
Yeah, they work and then over some period time I get the errors above. I...
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.
How do I prevent this error from happening? Would changing the MAXTRANSFERSIZE or MAXDATABLOCK fix this error? / comments
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.
How do I prevent thi...
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.
EXEC master..sqbmemory
DB #1
Type Minimum Maximum Average Blk count Total
Commit 4096 1073414144 2117388 1178 2494283776
Reserve 4096 158007296 3504834 116 406560768
Free 4096 110034944 743191 431 320315392
Private 4096 1073414144 4936024 571 2818469888
Mapped 4096 1060864 50991 334 17031168
Image 4096 24711168 167978 389 65343488
DB #2
Type Minimum Maximum Average Blk count Total
Commit 4096 60817408 209310 859 179798016
Reserve 4096 1012596736 23315597 116 2704609280
Free 4096 131465216 1544736 218 336752640
Private 4096 1012596736 6043590 465 2810269696
Mapped 4096 1060864 71982 122 8781824
Image 4096 24723456 168442 388 65355776 / comments
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...