Comments
2 comments
-
I've found this issue is affecting backup jobs too. I've opened a support case with Redgate since upgrading to version 9 of SQL Backup.
-
We are having the same issue, but only on one server in an availability group. The other nodes are working perfectly. This has only started happening since we upgraded to version 9 of SQL Backup Pro.
So update on this... I've now resolved this issue.
I stopped the SQL Agent on the server, then uninstalled version 9, plus version 8 which was still installed on the machine. Then reinstalled SQL Backup Pro V.9. Restarted the SQL Server Agent and this has resolved the issue.
Add comment
Please sign in to leave a comment.
Found this thread but the patch provided is unavailable (dead link). Also according to the documentation this bug was addressed in SQL Backup 7 and I've upgraded to v8 and have run successful restores since upgrading to v8 until today.
Restarting SQL Server did not resolve the issue. Haven't tried restarting the server because the other instances are in use and would have to do so after-hours.
Has anyone seen this issue in SQL2016? Is there an issue with the dll files for this instance? Any help or insight provided is greatly appreciated as I need to get this database back online.