Comments
Sort by recent activity
Any word from Red Gate about this? / comments
Any word from Red Gate about this?
That may be a good solution. I'm content to close this out for now and will keep an eye on when 4.5 becomes available. / comments
That may be a good solution. I'm content to close this out for now and will keep an eye on when 4.5 becomes available.
Anyone have any ideas on this? / comments
Anyone have any ideas on this?
They aren't - they are on servers 200 miles apart. This works perfectly fine 99% of the time, the error is intermittent on the tran log backup only. / comments
They aren't - they are on servers 200 miles apart. This works perfectly fine 99% of the time, the error is intermittent on the tran log backup only.
Correct, local SAN drive on the source server. / comments
Correct, local SAN drive on the source server.
Failed the cluster over and upgraded the passive nodes - I'm showing the correct new version now. Thanks Brian and Petey. / comments
Failed the cluster over and upgraded the passive nodes - I'm showing the correct new version now. Thanks Brian and Petey.
That worked, thanks. My console on my PC is still showing the server version at 4.1.0.207, even though I've verified all the EXEs and DLLs on the server are 4.2.0.205. I also used Process Explorer to verify that the running SQBCoreService.exe is 4.2.0.205. It looks like master..sqbutility is still returning 4.1.0.207.
Looks like there is an old version of xp_sqlbackup.dll in C:\Program Files\Microsoft SQL Server\MSSQL\Binn that it must be reading this info from, even though the service starts from C:\Program Files\Red Gate\SQL Backup\(LOCAL).
I can try renaming the one in C:\Program Files\Microsoft SQL Server\MSSQL\Binn if needed, just seems a little weird. / comments
That worked, thanks. My console on my PC is still showing the server version at 4.1.0.207, even though I've verified all the EXEs and DLLs on the server are 4.2.0.205. I also used Process Explorer ...
Doesn't seem to work - I still get the old version even after replacing it with the new DLL in the BINN directory. Guess it is still loaded in memory. I can fail the cluster over after hours - bringing SQL down and back up again should take care of it, unless you want me to try something else. / comments
Doesn't seem to work - I still get the old version even after replacing it with the new DLL in the BINN directory. Guess it is still loaded in memory. I can fail the cluster over after hours - brin...
Nope, same problem with that EXE also. I have a log file from SysInternals FileMon of the filesystem activity if that would help. No virus software on this server that might be locking files.
I do get a System Event Log message when I run the setup: "Cluster resource 'SQL Backup Agent' failed." The service is running when I check it after the fact, but it sounds like it is stopping and being restarted. I have tried running the setup with the service running and stopped. / comments
Nope, same problem with that EXE also. I have a log file from SysInternals FileMon of the filesystem activity if that would help. No virus software on this server that might be locking files.
I do ...