Backup failure
BruceB
Posts: 14
Hi,
Someone was working on our db today making some fairly substantial index changes. After running each change, he backedup the transaction log. Most of the time it worked but on a couple of occasions, it failed. This was written this the vdi.log file.
2005/08/14 18:29:08 pid(2108) tid(3416)
Error on Global\SQLBACKUP_14372462
Error at CVDS::Close: Abnormal termination state
2005/08/14 18:29:08 pid(2108) tid(3416)
Error on Global\SQLBACKUP_14372462
Error at TriggerAbort: invoked
2005/08/14 18:29:19 pid(1216) tid(804)
Error on Global\SQLBACKUP_14372462
Error at SVDS::Open: Open(control) Status Code: 2, x2
Explanation: The system cannot find the file specified.
This was in the log file.
14/08/2005 6:28:53 p.m.: SQL Backup 3.2.0, (c) Red Gate Software Ltd 2004 - 2005
14/08/2005 6:28:53 p.m.:
14/08/2005 6:28:53 p.m.: Backing up bigdb (transaction log) to g:\MSSQL\BACKUP\bigdb\bigdb_LOG_20050814_182853.sqb ...
14/08/2005 6:28:53 p.m.:
14/08/2005 6:28:53 p.m.: BACKUP LOG [bigdb] TO DISK = 'g:\MSSQL\BACKUP\bigdb\bigdb_LOG_20050814_182853.sqb' WITH NAME = '', DESCRIPTION = '', COMPRESSION = 1
14/08/2005 6:28:53 p.m.:
14/08/2005 6:28:53 p.m.:
14/08/2005 6:29:08 p.m.: VDI error 1010: Failed to get configuration from server. Check that the SQL Server instance is running, and that you have the SQL Server Systems Administrator server role. Error code: -2139684861 (The api was waiting and the timeout interval had elapsed.)
The job is run from a script that backs up 4 db logs. This db is the first, the following 3 all completed succesfully. This DB is 170Gb, some of todays log backups were 1.5Gb compressed. The other dbs are around 100Mb.
No other backups were running at these times. In the case above the previous backup had been at 6:15 and had completed by 6:20. Nothing else was started until about 8:15.
Any suggestions appreciated...
Someone was working on our db today making some fairly substantial index changes. After running each change, he backedup the transaction log. Most of the time it worked but on a couple of occasions, it failed. This was written this the vdi.log file.
2005/08/14 18:29:08 pid(2108) tid(3416)
Error on Global\SQLBACKUP_14372462
Error at CVDS::Close: Abnormal termination state
2005/08/14 18:29:08 pid(2108) tid(3416)
Error on Global\SQLBACKUP_14372462
Error at TriggerAbort: invoked
2005/08/14 18:29:19 pid(1216) tid(804)
Error on Global\SQLBACKUP_14372462
Error at SVDS::Open: Open(control) Status Code: 2, x2
Explanation: The system cannot find the file specified.
This was in the log file.
14/08/2005 6:28:53 p.m.: SQL Backup 3.2.0, (c) Red Gate Software Ltd 2004 - 2005
14/08/2005 6:28:53 p.m.:
14/08/2005 6:28:53 p.m.: Backing up bigdb (transaction log) to g:\MSSQL\BACKUP\bigdb\bigdb_LOG_20050814_182853.sqb ...
14/08/2005 6:28:53 p.m.:
14/08/2005 6:28:53 p.m.: BACKUP LOG [bigdb] TO DISK = 'g:\MSSQL\BACKUP\bigdb\bigdb_LOG_20050814_182853.sqb' WITH NAME = '', DESCRIPTION = '', COMPRESSION = 1
14/08/2005 6:28:53 p.m.:
14/08/2005 6:28:53 p.m.:
14/08/2005 6:29:08 p.m.: VDI error 1010: Failed to get configuration from server. Check that the SQL Server instance is running, and that you have the SQL Server Systems Administrator server role. Error code: -2139684861 (The api was waiting and the timeout interval had elapsed.)
The job is run from a script that backs up 4 db logs. This db is the first, the following 3 all completed succesfully. This DB is 170Gb, some of todays log backups were 1.5Gb compressed. The other dbs are around 100Mb.
No other backups were running at these times. In the case above the previous backup had been at 6:15 and had completed by 6:20. Nothing else was started until about 8:15.
Any suggestions appreciated...
Comments
This looks like a simple case of the SQL Backup program not being able to run osql.exe. SQL Backup writes a temporary SQL file to disk and then runs it with OSQL. Can you please check your path?
If the SQL Agent account is running as a particular user, log on as that user, open a command prompt, and type PATH. \80\Tools\Binn should be in the path somewhere. If it isn't, you can use 'my computer->Properties' to add the path.
If the agent is running as LocalSystem, use 'my computer->properties' and check and fix the path in the system variables rather than the user variables.
Please let me know if you have any further problems with this.
I've logged in with the service account and confirmed that osql is in the path.
I also checked the tmp dir and it is writeable by this account.
BB.
Can you try and run the backup using the GUI rather than the script to see if it completes.
Regards
Dan
Red Gate Software Ltd