How can we help you today? How can we help you today?
qcjims
Activity overview Badges (0) Posts (11) Comments (16)

Comments

Sort by recent activity
RBA wrote: Yes, MSCS replicates keys on failover (which seems slightly odd, since the previously active node might well be offline) so you won't see registry changes propagate until later. so taking the SQLBACKUP_AGENT offline and then bringing it back online is not enough? This KB article seems to indicate that registry changes are replicated when the resource goes offline. So, if i just fail the resource then it should replicate across all nodes right? http://support.microsoft.com/kb/174070 Any inconsistencies are probably a result of the fact that key replication breaks when this bug occurs. What bug are you referring to? -js / comments
  1. Community
  2. SQL Backup Previous Versions
  3. Error in system event log on x64 cluster system
RBA wrote: Yes, MSCS replicates keys on failover (which seems slightly odd, since the previously active node might well be offline) so you won't see registry changes propagate until later. so t...
0 votes
registry replication appears to be the culprit for us. I removed the entries in cluster admin for the individual SQLBACKUP_AGENT cluster resources and the errors in the System event log have disappeared. If I look in the cluster.log for errors, I see the following entries (or similar). The .tmp file mentioned matches up with the error in the event logs. Here are the cluster.log entries: 000010a8.00001a38::2009/09/17-23:23:21.391 WARN [CP] CppRegNotifyThread CppNotifyCheckpoint due to timer failed, reset the timer. 000010a8.00001a38::2009/09/17-23:23:21.391 INFO [CP] CppRegNotifyThread checkpointing key Software\Wow6432Node\Red Gate\SQL Backup\BackupSettings\B to id 2 due to timer 000010a8.00001a38::2009/09/17-23:23:21.391 INFO [Qfs] QfsGetTempFileName C:\DOCUME~1\MCS64\LOCALS~1\Temp\, CLS, 54807 => C:\DOCUME~1\MCS64\LOCALS~1\Temp\CLSD617.tmp, status 0 000010a8.00001a38::2009/09/17-23:23:21.391 INFO [Qfs] QfsDeleteFile C:\DOCUME~1\MCS64\LOCALS~1\Temp\CLSD617.tmp, status 0 000010a8.00001a38::2009/09/17-23:23:21.391 INFO [Qfs] QfsRegSaveKey C:\DOCUME~1\MCS64\LOCALS~1\Temp\CLSD617.tmp, status 5 000010a8.00001a38::2009/09/17-23:23:21.391 INFO [Qfs] QfsDeleteFile C:\DOCUME~1\MCS64\LOCALS~1\Temp\CLSD617.tmp, status 0 000010a8.00001a38::2009/09/17-23:23:21.391 WARN [CP] CppCheckpoint failed to get registry database Software\Wow6432Node\Red Gate\SQL Backup\BackupSettings\B to file C:\DOCUME~1\MCS64\LOCALS~1\Temp\CLSD617.tmp error 5 000010a8.00001a38::2009/09/17-23:23:21.391 INFO [Qfs] QfsDeleteFile C:\DOCUME~1\MCS64\LOCALS~1\Temp\CLSD617.tmp, status 2 000010a8.00001a38::2009/09/17-23:23:21.391 WARN [CP] CppRegNotifyThread CppNotifyCheckpoint due to timer failed, reset the timer. Here is the corresponding error in the system event log: Event Type: Error Event Source: ClusSvc Event Category: Database Mgr Event ID: 1080 Date: 9/17/2009 Time: 4:23:21 PM User: N/A Computer: XXXXXXXXXXXX Description: Cluster service could not write to a file (C:\DOCUME~1\MCS64\LOCALS~1\Temp\CLSD617.tmp). The disk may be low on disk space, or some other serious condition exists. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 05 00 00 00 .... When I add the replicated registry entries back using CLUADMIN, the errors do not return. However, it does not appear that registry replication is actually doing anything at this point (which might explain the lack of errors). When I attempt to make changes to these values using the SQLBackup GUI (changing smtp setting for example), the values are recorded on the node that the cluster group is running on, but the values are not replicated to the other nodes. I have also noticed that there are inconsistencies between the instances listed under the BackupSettings, BackupSettingsGlobal and InstalledInstances registry keys across the cluster nodes. Shouldn't all the instances listed under each key be the same across the entire cluster? -js / comments
  1. Community
  2. SQL Backup Previous Versions
  3. Error in system event log on x64 cluster system
registry replication appears to be the culprit for us. I removed the entries in cluster admin for the individual SQLBACKUP_AGENT cluster resources and the errors in the System event log have disap...
0 votes
I was curious about the feature set since the roadmap indicates releases this year. I don't have anything in particular that I'd like to see at this point. / comments
  1. Community
  2. SQL Backup Previous Versions
  3. SQL Backup Pro 6.5 and 7
I was curious about the feature set since the roadmap indicates releases this year. I don't have anything in particular that I'd like to see at this point.
0 votes
I was fed up with this product too. Too many issues to deal with and try to troubleshoot. I just simply gave up and will wait for these bugs to be fixed. Maybe version 3 will work a little better. For now, 2.1 is basically unusable in a large environment. -jim / comments
  1. Community
  2. SQL Monitor Previous Versions
  3. Monitoring Stopped - NOT INFORMED OF THIS
I was fed up with this product too. Too many issues to deal with and try to troubleshoot. I just simply gave up and will wait for these bugs to be fixed. Maybe version 3 will work a little bette...
0 votes
Angus C wrote: Hi Linque, I work in the DBA sales team here at Red Gate and I happen to know that we have some iPads left over from the iPad contest we recently ran. As a result we have a limited supply of those beautiful tablets that we are GIVING away for FREE to customers who purchase more than 10 licenses of SQL Monitor on one Invoice. This needs to be mentioned at the time of quoting with one of our sales reps, but I just thought it worth a mention on this forum chain. Angus. [image] We purchased a 100 license package and didn't get anything like this [image] We actually purchased the 100 licenses to get SQL Backup, SQL Monitor was just an added benefit. We can't even use the product though because of all the bugs. -jim / comments
  1. Community
  2. SQL Monitor Previous Versions
  3. Need Monitoring Software ASAP, but 2.1 Will Not Cut It
Angus C wrote: Hi Linque, I work in the DBA sales team here at Red Gate and I happen to know that we have some iPads left over from the iPad contest we recently ran. As a result we have a limit...
0 votes
We have 250+ servers to monitor. I was getting random failures with monitoring my test systems (hand picked, new deployments btw, not 2-3 year old systems). This product fails randomly all over the place. As I said in my original post, I don't have the 2-4 hours free time to spend troubleshooting each failure. For now we will stick to using SCOM 2007 R2 (ughh), Quest foglight and spotlight, and our own custom scripts to handle our monitoring tasks. Why can't someone get basic monitoring for windows right? I just don't get it. -jim / comments
  1. Community
  2. SQL Monitor Previous Versions
  3. We are abandoning SQL monitor for now
We have 250+ servers to monitor. I was getting random failures with monitoring my test systems (hand picked, new deployments btw, not 2-3 year old systems). This product fails randomly all over t...
0 votes
i will try the two steps you mentioned. however, why doesn't SQL monitor do these steps and then report on what is/is not actually working? -jim / comments
  1. Community
  2. SQL Monitor Previous Versions
  3. Monitoring stopped (Incorrect credentials or insufficient
i will try the two steps you mentioned. however, why doesn't SQL monitor do these steps and then report on what is/is not actually working? -jim
0 votes
yes it is win2k8 R2. i'll check for the KB article on the memory leak, but in case I can't find it please post the information you have. thanks. -js / comments
  1. Community
  2. SQL Monitor Previous Versions
  3. Connection failed (Cannot Connect)
yes it is win2k8 R2. i'll check for the KB article on the memory leak, but in case I can't find it please post the information you have. thanks. -js
0 votes
THanks Harold. I grabbed that hotfix and have it applied. We'll see if the error goes away, but it definitely looks to be a match. I also ran across this WMI memory leak article. http://support.microsoft.com/kb/977357 -js / comments
  1. Community
  2. SQL Monitor Previous Versions
  3. Connection failed (Cannot Connect)
THanks Harold. I grabbed that hotfix and have it applied. We'll see if the error goes away, but it definitely looks to be a match. I also ran across this WMI memory leak article. http://support.mi...
0 votes
ok, i will give the comma-delimited approach a try. I am concerned though with the number of servers/instances that a single SQL MOnitor environment can effectively monitor. Is there any guidance for this? Right now I have 55 servers/instances monitored (this is the number in Global Overview) and the system is running at close to 100% cpu at all times. We installed all SQL Monitor components on a single host though for this test, so maybe we need to break things up a bit. -js / comments
  1. Community
  2. SQL Monitor Previous Versions
  3. Is there a way to bulk add servers to monitor?
ok, i will give the comma-delimited approach a try. I am concerned though with the number of servers/instances that a single SQL MOnitor environment can effectively monitor. Is there any guidance...
0 votes
Total activity
37
Last activity
Member since
Following
0 users
Followed by
0 users
Votes
0
Subscriptions
10