Error Code: -2139684860
timothyawiseman
Posts: 5
Hello;
I have a weekly full backup job that works perfectly for most databases but fails on some of them.
When it fails the messages listed are:
Thread 0 error:
Process terminated unexpectedly. Error Code: -2139684860
Thread 1 error:
Process terminated unexpectedly. Error Code: -2139684860
Thread 2 error:
Process terminated unexpectedly. Error Code: -2139684860
SQL error 3013: Backup Database is terminated Abnormally
SQLError 3271: A nonrecoverable I/O error occurred on file.
This is using Red Gate SQL Backup 5.3.0.178 with SQL Server 2005 SP2 on Windows Server 2003. The compression level is set to 1, encryption is turned on, and it is set to break up the backups in 3 files. At the time this runs there is virtually no other demand on the server.
All the databases that are having the failure are relatively large (150GB up to 500GB), but I have very similar settings with similarly sized databases on other servers with no problem.
I tried looking this up and the main suggestion I found was upgrading to 5.3 which I already have. Does anyone have any other ideas?
I have a weekly full backup job that works perfectly for most databases but fails on some of them.
When it fails the messages listed are:
Thread 0 error:
Process terminated unexpectedly. Error Code: -2139684860
Thread 1 error:
Process terminated unexpectedly. Error Code: -2139684860
Thread 2 error:
Process terminated unexpectedly. Error Code: -2139684860
SQL error 3013: Backup Database is terminated Abnormally
SQLError 3271: A nonrecoverable I/O error occurred on file.
This is using Red Gate SQL Backup 5.3.0.178 with SQL Server 2005 SP2 on Windows Server 2003. The compression level is set to 1, encryption is turned on, and it is set to break up the backups in 3 files. At the time this runs there is virtually no other demand on the server.
All the databases that are having the failure are relatively large (150GB up to 500GB), but I have very similar settings with similarly sized databases on other servers with no problem.
I tried looking this up and the main suggestion I found was upgrading to 5.3 which I already have. Does anyone have any other ideas?
Comments
SQL Backup Consultant Developer
Associate, Yohz Software
Beyond compression - SQL Backup goodies under the hood, updated for version 8