Comments
7 comments
-
Could you please locate the SQL Backup Agent service in Windows Services, and see if it's started? If not, could you try to start it and see what happens?
If it does not start, try using a startup account that is an Administrator on the machine. Will the service start then? -
SQL Backup Agent located and running without event log error. Running with local services; Double checked by trying to run as administrator... still same message "error mapping to memory mapped file".
Also tried with Hyperbac service turned off. -
When you run the following in Management Studio, what is the result:
EXEC master..sqlbackup '-sql "BACKUP DATABASE model TO DISK = [<AUTO>]"'
-
Apologies for not having checked docs first... appreciate guidance where to start and the cool command to learn.. here is the result...
SQL Backup 7.6.029
ERRSQB: 5220 (Error mapping to memory mapped file.) (SQBMmf_): 8 (Not enough storage is available to process this command.)
name::value
exitcode::5220
sqlerrorcode::0
-- current
use master
go
BACKUP DATABASE MODEL TO DISK = 'F:\Model.bak' --1500K on disk
BACKUP DATABASE MODEL TO DISK = 'F:\Model.zip' --0150K on disk -
Could you please run the following in Management Studio and post the result:
EXEC master..sqbmemory
Thanks. -
Type Minimum Maximum Average Blk count Total ---------------- -------------------- -------------------- -------------------- -------------------- -------------------- Commit 4096 262733824 50892 14560 740999168 Reserve 4096 16773120 105625 12357 1305219072 Free 4096 983040 166996 606 101199872 Private 4096 262733824 74437 26345 1961050112 Mapped 4096 1060864 107861 63 6795264 Image 4096 24948736 153974 509 78372864 (6 row(s) affected
-
The problem seems to be that your SQL Server process has very little free memory left, and the largest contiguous block of free memory is only 983040 bytes. That's why SQL Server is raising the error 'Not enough storage is available to process this command.'.
If possible, try restarting the SQL Server instance to reset the memory allocations, and try running the backup. Then you could run sqbmemory periodically to try and identify which process in SQL Server is taking up all the memory.
Add comment
Please sign in to leave a comment.
Very new to SQL Backup Pro... search docs and asking question now in forums before using support. Appreciate any insight.
The tree of servers has just one with red x
Installed GUI on aging SQL2005/W2003 Enterprise and tried registering, importing but no joy... yet :-)
Thank you!