How can we help you today? How can we help you today?
tlbroadbent
Thanks for your replies. I know that Red Gate developers and support personnel are very responsive to user needs. Thanks for the help. I may use SQL Backup 4 client when I'm in a hurry. I'll give it a try. Thanks again. / comments
Thanks for your replies. I know that Red Gate developers and support personnel are very responsive to user needs. Thanks for the help. I may use SQL Backup 4 client when I'm in a hurry. I'll give i...
0 votes
Peter, The service is started and has been running since installation. Regular backups occur. The only problem is getting the client to work on this server. Terry / comments
Peter, The service is started and has been running since installation. Regular backups occur. The only problem is getting the client to work on this server. Terry
0 votes
Yes. SQLBackup is working now because I restarted the SQL Server service. Had to get the nightly backups done. I'll run memstat next time backups begin to fail and post the output. Thanks for your help. / comments
Yes. SQLBackup is working now because I restarted the SQL Server service. Had to get the nightly backups done. I'll run memstat next time backups begin to fail and post the output. Thanks for your ...
0 votes
We perform multiple backups within the backup job. The first time the error occurs, it may happen on the first or any subsequent backup. After that it usually fails on the first backup attempted. Here are the VDI contents for the last error that occurrred. 2006/01/16 18:46:30 pid(3208) tid(5496) Error on Global\SQLBACKUP_{8123B2FB-D86A-46DE-801D-BF12C8A5DAE1} Error at ServerBufferAreaManager::Allocate: Map buffers Status Code: 8, x8 Explanation: Not enough storage is available to process this command. 2006/01/16 18:46:30 pid(3208) tid(5496) Error on Global\SQLBACKUP_{8123B2FB-D86A-46DE-801D-BF12C8A5DAE1} Error at TriggerAbort: invoked 2006/01/16 18:46:30 pid(2860) tid(4624) Error on Global\SQLBACKUP_{8123B2FB-D86A-46DE-801D-BF12C8A5DAE1} Error at CVD::GetCommand: AbortDetected 2006/01/16 18:46:30 pid(3208) tid(3728) Error on Global\SQLBACKUP_{8123B2FB-D86A-46DE-801D-BF12C8A5DAE1} Error at TriggerAbort: invoked 2006/01/16 18:46:30 pid(3208) tid(3728) Error on Global\SQLBACKUP_{8123B2FB-D86A-46DE-801D-BF12C8A5DAE1} Error at SVDS::CloseDevice: Abort detected 2006/01/16 18:46:30 pid(3208) tid(3728) Error on Global\SQLBACKUP_{8123B2FB-D86A-46DE-801D-BF12C8A5DAE1} Error at TriggerAbort: invoked 2006/01/16 18:46:30 pid(2860) tid(4624) Error on Global\SQLBACKUP_{8123B2FB-D86A-46DE-801D-BF12C8A5DAE1} Error at TriggerAbort: invoked 2006/01/16 18:46:30 pid(3208) tid(5496) Error on Global\SQLBACKUP_{8123B2FB-D86A-46DE-801D-BF12C8A5DAE1} Error at TriggerAbort: invoked 2006/01/16 18:46:30 pid(2860) tid(4368) Error on Global\SQLBACKUP_{8123B2FB-D86A-46DE-801D-BF12C8A5DAE1} Error at TriggerAbort: invoked / comments
We perform multiple backups within the backup job. The first time the error occurs, it may happen on the first or any subsequent backup. After that it usually fails on the first backup attempted. H...
0 votes