Comments
Sort by recent activity
Here is the info from the ApplicationLog on the server when the backups stopped working:
18210 :
BackupVirtualDeviceSet::Initialize: Open failure on backup device 'SQLBACKUP_84B32D32-1B9F-4BD2-A437-BA3288FD4432'. Operating system error 0x80070002(The system cannot find the file specified.).
3041 :
BACKUP failed to complete the command sp_executesql;1
The SQLSERVER LOGS don't show anything.
VDI LOGS follow:
2006/01/06 05:06:31 pid(772) tid(360)
Error on SQLBACKUP_{C85B124F-D2C9-4FF6-819D-5C5D64FCD024}
Error at SVDS::Open: Open(control) Status Code: 2, x2
Explanation: The system cannot find the file specified.
2006/01/09 05:00:19 pid(1032) tid(1736)
Error on SQLBACKUP_{113930C9-47A8-4640-A0BD-2FB9B97F0F0E}
Error at CVDS::Close: Abnormal termination state
2006/01/09 05:00:19 pid(1032) tid(1736)
Error on SQLBACKUP_{113930C9-47A8-4640-A0BD-2FB9B97F0F0E}
Error at TriggerAbort: invoked
2006/01/09 05:06:31 pid(772) tid(776)
Error on SQLBACKUP_{113930C9-47A8-4640-A0BD-2FB9B97F0F0E}
Error at SVDS::Open: Open(control) Status Code: 2, x2
Explanation: The system cannot find the file specified. / comments
Here is the info from the ApplicationLog on the server when the backups stopped working:
18210 :
BackupVirtualDeviceSet::Initialize: Open failure on backup device 'SQLBACKUP_84B32D32-1B9F-4BD2-A437...
Stopping and Startng SQLBACKUP Agent service seems to have cleared up the problem. How long will it be before the problem crops upa again? / comments
Stopping and Startng SQLBACKUP Agent service seems to have cleared up the problem. How long will it be before the problem crops upa again?
Yes. Any backup that is run is producing the same result.
I am going to start tby rebooting the server so I can get a good set of backups. But I feel that the problem will re-occur again after a period of time. / comments
Yes. Any backup that is run is producing the same result.
I am going to start tby rebooting the server so I can get a good set of backups. But I feel that the problem will re-occur again after a pe...
Ok. Now I am not able to backup things again. Log backups and FULL backups both. Below is the results of running a backup attempt. This is after the server has been rebooted. I can't keep reboooting the server to get this to keep backing up. What do I need to do now?
Thanks.
Owen
-SQL " BACKUP LOG [AMEREX] TO DISK='D:\SQLBackups\Daily\AMEREX\TransactionLogs\AMEREX_tlog_20060210102531827.sqt' WITH NAME='LOG AMEREX, 2006-02-10 10:25:31.827', DESCRIPTION='Backup on 02/10/2006 10:25:31 Database: AMEREX Instance: (local) Server: HOU-BEST-PROD', VERIFY, MAILTO_ONERROR='owenh@amerexenergy.com;owen.hebert@gmail.com', ERASEFILES_ATSTART=4, COMPRESSION=2 " -E'
SQL Backup (DLL v4.0.0.113)
Error acquiring mutex: WAIT_TIMEOUT
name value
exitcode 0
sqlerrorcode 0 / comments
Ok. Now I am not able to backup things again. Log backups and FULL backups both. Below is the results of running a backup attempt. This is after the server has been rebooted. I can't keep reboooti...
I will restart the SQLBAckup Service,then try to re-run the logs.
No, this box is not using fiber mode.
On this server, I do Full DB Backups once per day on approximately 9 databases and lot's of log backups throughout the day (probably about 1000+ in a 24 hour period). / comments
I will restart the SQLBAckup Service,then try to re-run the logs.
No, this box is not using fiber mode.
On this server, I do Full DB Backups once per day on approximately 9 databases and lot's of ...
Great! Thanks very much. / comments
Great! Thanks very much.
Will this patch stop the application popup errors that are occuring on the server? If so, please send it.
Thanks / comments
Will this patch stop the application popup errors that are occuring on the server? If so, please send it.
Thanks
The patch for SQLBackup (version 3.2.0.2) appears to have corrected the problems.
Thanks! / comments
The patch for SQLBackup (version 3.2.0.2) appears to have corrected the problems.
Thanks!
The Command prompt shows that the path for the OSQL program is available.
When I log on as the userid running SQLAgent and drop to a command prompt, running OSQL command works properly, i.e., it is finding the program.
As I stated previously, this is intermittent. It is running backups usign the identical criteria for bot logs and full backups all day long. It just appears to be failing at seemingly random times. Some other posts indicated that the error could be being caused by "rapidly creating VDI devices " thus causing a conflict. / comments
The Command prompt shows that the path for the OSQL program is available.
When I log on as the userid running SQLAgent and drop to a command prompt, running OSQL command works properly, i.e., it is...
Thanks everyone for responding. I look forward to the next version then. In the meantime, I will be setting up scripts that will be used to accomplish the same thing, based on examples I have seen in other posts here in the newsgroup. / comments
Thanks everyone for responding. I look forward to the next version then. In the meantime, I will be setting up scripts that will be used to accomplish the same thing, based on examples I have seen ...