Comments
1 comment
-
The WAIT_TIMEOUT error is raised by the SQL Backup engine, not by the SQL Server engine. The issue causing this error to be raised had been addressed in build 511 (see http://www.red-gate.com/messageboard/viewtopic.php?t=2387). The error code should indeed have been 5160, and not 0.
Add comment
Please sign in to leave a comment.
I´m using SQL Backup 4.1 to restore files to stand-by server. The database at stand-by server became SUSPECT, but the SQL Backup restore returns exitcode=0 as everything was OK, but the database is NOT ACCESSIBLE !!!
I´m sending the command I´m using to restore, if you take a look you can see a WAIT_TIMEOUT eror, but the exit code remains 0 ????
As soon as possible give me a reply because I may be in trouble if I need to use this backups.
Thanks,
Paulo Ribeiro
##################
Command used to restore
##################
exec master..sqlbackup N
'-SQL "RESTORE LOG dbXYZ
from DISK =
''H:\DUMP_ServerXYZ_DBXYZ_2006-05-23_09-55-00-000_LOG.RGB''
with STANDBY = ''H:\UNDO_FILE_ServerXYZ.STB''"'
SQL Backup (DLL v4.1.0.207)
Error acquiring mutex: WAIT_TIMEOUT
name value
exitcode 0
sqlerrorcode 0