Getting error 602 randomly since last week
jimmytodo
Posts: 2
Hi i am using sql backup 5.3 but recently started getting the following errors since last week. All the error messages are same so i am just pasting the recent ones. We have backup schedule of 4 databases but this is the only one which has a problem. It failed on three days last week. Can somebody help diagnose the problem.
SQL error 3202: Write on "SQLBACKUP_5679FD87-A493-44A4-9779-E7E6B9F6ED04" failed: 1117(error not found)
Thread 0 error:
Error 620: Error writing to backup file(s).
Process terminated unexpectedly. Error code: -2139684860
SQL error 3013: BACKUP DATABASE is terminating abnormally.
SQL error 3271: A nonrecoverable I/O error occurred on file "SQLBACKUP_5679FD87-A493-44A4-9779-
E7E6B9F6ED04:" 995(error not found).
Thread 2 error:
Error 620: Error writing to backup file(s).
Process terminated unexpectedly. Error code: -2139684860
Thread 1 error:
Error 620: Error writing to backup file(s).
Process terminated unexpectedly. Error code: -2139684860
SQL error 3202: Write on "SQLBACKUP_5679FD87-A493-44A4-9779-E7E6B9F6ED04" failed: 1117(error not found)
Thread 0 error:
Error 620: Error writing to backup file(s).
Process terminated unexpectedly. Error code: -2139684860
SQL error 3013: BACKUP DATABASE is terminating abnormally.
SQL error 3271: A nonrecoverable I/O error occurred on file "SQLBACKUP_5679FD87-A493-44A4-9779-
E7E6B9F6ED04:" 995(error not found).
Thread 2 error:
Error 620: Error writing to backup file(s).
Process terminated unexpectedly. Error code: -2139684860
Thread 1 error:
Error 620: Error writing to backup file(s).
Process terminated unexpectedly. Error code: -2139684860
Comments
The error message isn't very informative, so I can't say for sure why you're getting this error.
I suspect that you are possibly backing up over a network and this error is caused by some kind of connection loss.
If you are backing up over a network, then you might like to consider upgrading to SQL Backup 6 as this version contains some network resilience features to retry after any network related failures.
If you do not wish to upgrade, then I would recommend backing up to a local drive first, and then copy the file to the network location using the COPYTO command.
If you are already backing up locally first, can you post the backup script you are using, and I’ll see if there could be anything else that might be causing this error.
I hope this is helpful.