emulator Posted October 9, 2008 Report Share Posted October 9, 2008 (edited) Hi All... I've been having a BUNCH of problems backing up a Windows Server 2008 cluster of two nodes running SQL Server 2005. The data coming from that backup client would do one of two things: 1. corrupt the Retrospect DAT file 2. cause Retrospect to crash with the dreaded "assertion" error Each time I restored the DAT file to a point in time before the crashes AND removed the cluster from backup, Retrospect was happy as a clam(AV). On the flip side, the cluster would stop responding when our database admin performed a "detach" function on the database. The SQL Server data, located on a shared volume between the two nodes, would then become inaccessible. The only fix was to completely reconstruct the cluster. This happened five times. I can't help but think that this issue and the backup issues with Retrospect are connected, as we have a non-clustered Server 2008/SQL2005 box that backs up just fine. Fast forward to today, where we found this article on Microsoft's site: http://support.microsoft.com/kb/955825 This article appears to work for MSSQL Server 2005, even though it states that it applies only to MSSQL Server 2008. The fix in this article appears to have solved the problem of the shared disk and detaching databases. I'm *hoping* that the fix also corrects the problems with Retrospect. I'll post back here to let you all know if there are any further issues. Robin, you might want to log this with your tech teams that this obscure *Microsoft* bug might make Retrospect unhappy. Edited October 9, 2008 by Guest Quote Link to comment Share on other sites More sharing options...
Mayoff Posted October 9, 2008 Report Share Posted October 9, 2008 I will let our engineers know about the MS issue. Quote Link to comment Share on other sites More sharing options...
emulator Posted October 19, 2008 Author Report Share Posted October 19, 2008 Since applying the Microsoft fix, we have seen zero crashes. This did it! Quote Link to comment Share on other sites More sharing options...
emulator Posted October 22, 2008 Author Report Share Posted October 22, 2008 I spoke too soon. Since posting the last message, we have seen 3 crashes (assertion errors). I am trying the following: 1. remove the cluster from our backup rotation ("forget" the client from Retro) 2. add the client to another Retrospect server we have I'll report back on my findings. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.