Comments
Sort by recent activity
Good Lord!
16GB in 38seconds?!?
How do you live with yourself? [image] / comments
Good Lord!
16GB in 38seconds?!?
How do you live with yourself?
Yes, there are certainly many ways to work around the issue, and if I had such a tight backup window as I described above, I would probably create a seperate job as well. One would just do local backups, and the other would do the copy. However, in the context of providing feedback for the network resiliency feature, it'd be nice to see a queuing option and be able to have the solution all bundled up. / comments
Yes, there are certainly many ways to work around the issue, and if I had such a tight backup window as I described above, I would probably create a seperate job as well. One would just do local b...
Glad to hear it. Also glad to know it wasn't just me! [image] Seems like I'm the only one who was seeing this issue. / comments
Glad to hear it. Also glad to know it wasn't just me! Seems like I'm the only one who was seeing this issue.
Cool. I've saved the profile history for those three servers. If you end up needing the history to see the order of events that the GUI is doing, let me know, and I'll e-mail it. / comments
Cool. I've saved the profile history for those three servers. If you end up needing the history to see the order of events that the GUI is doing, let me know, and I'll e-mail it.
There's nothing in the log files except these two lines:
12:57:29.740|Info |UI |1 |SQL Backup Client 6.0.0.339
12:57:29.755|Info |UI |1 |=======================================
However.... I went ahead and set up profiler on several SQL servers waiting for the the error to show up and then seeing what the final command was. I found a commonality, and can reproduce the error when I run the following command in query analyzer / managment studio.
master..sqbdata 'SELECT COUNT(*) FROM backuphistory WHERE id > 0 AND backup_start < ''0001-01-06 00:00:00'' AND backup_end > ''0001-01-01 00:00:00'' '
This same command was sent to three different servers at just about the same time... All of them then had the error. For some reason the year is being sent as 0001.
Even if the year were correct, I would expect you to always get a count of 0 with that logic.
From what I can see in the profile history..nowhere else is that command sent before this occurrence with or without valid year.
Hopefully, this info will let you find it in the code.
Good luck,
Dan W / comments
There's nothing in the log files except these two lines:
12:57:29.740|Info |UI |1 |SQL Backup Client 6.0.0.339
12:57:29.755|Info |UI |1 |====================...
I just E-mailed a CamStudio video I took this morning. So the error definitely is a recurring one.
Email subject:
SQLBackup 6 PreRelease Recurring Error / comments
I just E-mailed a CamStudio video I took this morning. So the error definitely is a recurring one.
Email subject:
SQLBackup 6 PreRelease Recurring Error
Wow! I was sure the licensing would be per virtual server instance. This is great news. Let's say I want to run 30 Virtual servers on 1 physical server. How does your license activation mechanism handle this?
If I only buy 1 license and activate it over the internet on Virtual Server 1, will I have to call in for each of the other 29 to have Red Gate adjust the number of times I can use the same serial Number?
Thank You,
Dan / comments
Wow! I was sure the licensing would be per virtual server instance. This is great news. Let's say I want to run 30 Virtual servers on 1 physical server. How does your license activation mechani...
Good to know. I see now the NOTE below that options not only speaks of msdb, but also of the 'internal cache'. I had always just assumed it was for msdb only since I didn't know about the CE file.
Thanks for the answers. I appreciate that Red Gate was open and willing to share that info. Like I said in my first post, this could have easily gone the proprietary route.
Dan / comments
Good to know. I see now the NOTE below that options not only speaks of msdb, but also of the 'internal cache'. I had always just assumed it was for msdb only since I didn't know about the CE file...
Thanks Petey!
Two more questions sprang from your answer. Is there any purging of old data that happens, and where can i find that data.sdf file in a clustered environment. I just checked on one of ours (expected the sdf to have a lot of data), and couldn't find it where you specified. I did find it on a non-clustered install, with no problems, however.
Thank again,
Dan / comments
Thanks Petey!
Two more questions sprang from your answer. Is there any purging of old data that happens, and where can i find that data.sdf file in a clustered environment. I just checked on one ...
Got it!
Thanks / comments
Got it!
Thanks