Comments
Sort by recent activity
Not sure what you mean, but you could simply exclude the other databases from backup jobs. Am I missing something? Registering the server on the GUI doesn't mean it's going to start backing up everything. You define that. / comments
Not sure what you mean, but you could simply exclude the other databases from backup jobs. Am I missing something? Registering the server on the GUI doesn't mean it's going to start backing up ever...
No change in behavior for the clustered server, even with the timeline disabled.
Implemented timeline disable regkey on client computer, launched GUI, can see the timeline is disabled for everything listed. Selected a random server from the list, Activity History populated in under a minute.
Selected the SQL server that's giving me problems per the opening post, 10 minutes later I still have a spinning green circle on it and no Activity History to show.
So it is doesn't seem to be that activity timeline is what causing the issue. It is definitely the data.sdf file issue. / comments
No change in behavior for the clustered server, even with the timeline disabled.
Implemented timeline disable regkey on client computer, launched GUI, can see the timeline is disabled for everythin...
I do not. Right now the file is 153MB in size. I still have the old one (renamed it .old) and that one is 173MB in size. / comments
I do not. Right now the file is 153MB in size. I still have the old one (renamed it .old) and that one is 173MB in size.
Need some clarification.
Where do I make this regkey change? On the SQL cluster or on the server I run the GUI on (which is not a SQL server)?
If the later, the server where I installed the GUI for SQL Backup doesn't have a Red Gate\SQL Backup subkey.
In HKLM\Software\Red Gate the only subkey showing is Downloads, under with there IS a SQL Backup subkey which in turn has a '6' subkey in it.
In HKLM\Software\Wow6432Node\Red Gate I have the following subkeys:
Downloads
IPN
Licensing
SQL Changeset
SQL Object Level Recovery Pro
SQLToolsInstalledProducts
Update
So no SQL Backup subkey either. / comments
Need some clarification.
Where do I make this regkey change? On the SQL cluster or on the server I run the GUI on (which is not a SQL server)?
If the later, the server where I installed the GUI for...
Hi Chris, we've gone down to just 30 days retention on history from being initially at 90. I wouldn't want to go lower than that.
What is the effect of disabling the timeline in the GUI? Will it still populate backup history in the GUI if I disable the timeline? / comments
Hi Chris, we've gone down to just 30 days retention on history from being initially at 90. I wouldn't want to go lower than that.
What is the effect of disabling the timeline in the GUI? Will it st...
Not knowing the particular cause of the issues you're having, I'm using SQL Backup 6 on a SQL cluster which has 1100+ databases and growing, with no issues on the backup jobs.
I did have an issue with the GUI console timing out when it was refreshing the activity window during the initial deployment of SQL Backup 6. That was resolved with a patch. It's still pretty slow refreshing, well, slower than I would like, but it won't time out now.
With the backup jobs themselves, it's been smooth sailing so far.
The only thing I would like is for Red Gate to add a parameter so that if a differential or log backup on xyz database is not possible because there's not a full backup yet, it automatically switches the backup for that database to a full.
For the server I reference above, I use the 'USER DATABASES' parameter to backup everything, but if a new db is created in between fulls, I get annoying 'error' messages for the log or diff backups until I manually do a full backup of the offending database. Having SQL Backup handling this automatically via a parameter flag would be a plus. / comments
Not knowing the particular cause of the issues you're having, I'm using SQL Backup 6 on a SQL cluster which has 1100+ databases and growing, with no issues on the backup jobs.
I did have an issue w...
Well, scratch that. Ever since upgrading to 6.5.1.9 this particular server no longer populates the activity history window when I open my SQL Backup GUI console. It just sits there with a green spinning circle and on the SQL server, the process id that is being executed show incrementing wait of type MSQL_XP.
So something is wrong. I have a ticket open with Red Gate but so far I'm not making progress. / comments
Well, scratch that. Ever since upgrading to 6.5.1.9 this particular server no longer populates the activity history window when I open my SQL Backup GUI console. It just sits there with a green spi...
Thanks petey. That worked, except that the model database was included in the list of databases that was backed up.
After some more reading I found that doing: EXECUTE master..sqlbackup '-SQL "BACKUP LOGS EXCLUDE [model] TO ....
was the way to go. This backs up all my user databases while excluding the model database. / comments
Thanks petey. That worked, except that the model database was included in the list of databases that was backed up.
After some more reading I found that doing:EXECUTE master..sqlbackup '-SQL "BACKU...
Just wanted to post an update. Last weekend we had our production servers run through our windows patching maintenance window which requires them to reboot. I just checked the registry keys for the DataPath location on all of our SQL clusters and the path DID NOT revert to the C: volume. It still pointing to the proper location.
So it looks like adding the shared volume where the files reside as a dependency of the SQL Backup Agent cluster resource was the fix, since the SQL Backup Agent cluster resource won't go online until the shared volume does.
I will keep my eyes on this next month but I think this problem is resolved. / comments
Just wanted to post an update. Last weekend we had our production servers run through our windows patching maintenance window which requires them to reboot. I just checked the registry keys for th...
I added the cluster shared drive as a dependency of the SQLBackupAgent cluster resource on a test cluster instance and the registry key didn't revert to the C: drive after our last patch cycle reboot.
I'm not declaring victory yet though. I've since since made this change on all our production clustered SQL instances but won't know for sure this will fix the problem until our next patch cycle next week.
I will update this thread with the results. / comments
I added the cluster shared drive as a dependency of the SQLBackupAgent cluster resource on a test cluster instance and the registry key didn't revert to the C: drive after our last patch cycle rebo...