Comments
Sort by recent activity
After tinkering with it a while I finally have it working.
The trick was to edit the registry on the virtual server and then it propagates back to the registry on the nodes once they become active at least once.
Now....having said that the jobs do now xfer to nodes. Some things do not xfer though, for instance the group name. What items are stored in the sdf file that will xfer across nodes? / comments
After tinkering with it a while I finally have it working.
The trick was to edit the registry on the virtual server and then it propagates back to the registry on the nodes once they become active ...
For the 2 keys referenced, I have the first as a 1. However the second DataPath is a local non-shared drive. I selected the cluster install, obvious if #1 was a 1.
Obviously the cluster install did not work for me and I have now installed it on 3 clusters and all 3 of them have the same issue. It has seen both cluster nodes each time. All 3 clusters have a 1 in the IsCluster key but all 3 have local DataPaths.
This explains why none of my settings xfer across nodes.
Is there another way to fix the DataPath issue w/o a remove & reinstall? / comments
For the 2 keys referenced, I have the first as a 1. However the second DataPath is a local non-shared drive. I selected the cluster install, obvious if #1 was a 1.
Obviously the cluster install did...
Peter,
A few weeks ago you referenced the topic for the tasks/jobs to display on both nodes. That post you reference is slightly confusing because it was for v4. Anyhow the SQLBackupAgent cluster resource was created by the install
but I did all a 3rd replicated registry key for :
Software\Wow6432Node\Red Gate\SQL Backup\InstalledInstances\<instance name>\ServiceLogin
The other key mentioned in the post already existed. So I added the key and when I move the cluster to the passive node, which has v5.1 installed, the server that I added on the active node is not there. To reiterate, I have installed v5.1 on each node and each node has been activated via the ProductActivation.exe.
Am I missing something or do the server listings, etc not "replicate" across nodes? / comments
Peter,
A few weeks ago you referenced the topic for the tasks/jobs to display on both nodes. That post you reference is slightly confusing because it was for v4. Anyhow the SQLBackupAgent cluster r...
Another cluster ? ..... I setup my backup v5 jobs on node1 but when I move the sql server and sqlserverbackupagent generic resource to node 2 and start SQL Backup those jobs, the server, etc are not present in SQL Backup.
However I have another cluster with version 4 that works correctly and the jobs, server, et al show on the other node.
A fluke or a difference in versions?
How do I get those jobs to show on both nodes? / comments
Another cluster ? ..... I setup my backup v5 jobs on node1 but when I move the sql server and sqlserverbackupagent generic resource to node 2 and start SQL Backup those jobs, the server, etc are no...
Jason,
I checked again and there were no program files (i.e. C:\Program Files\Red Gate) on the passive node. I took your advice and then ran the installer on the passive node and it looks like everything went ok.
However I want to clarify what you said about the upgrade. You said run 5.1 or whatever in the future on the Active node. Do you mean the active host or the virtual device? Seems like I would have the same issue as before if I ran it only on the active node and have to upgrade on both nodes.
****UPDATED****
I ran 5.1 Update on Active Node and checked the Version # on the virtual device and it reported 5.1. I then moved the resources to Node 2 (Passive) and checked the Version # on the virtual device and it reported 5.0. Then ran the update installer on Node 2 and rechecked virtual device version and it showed 5.1.
Also just FYI the cluster aware installer did not place any dependencies on the SQLBackupAgent resource. Normally there would be 2...SQL Server and SQL Server Agent. / comments
Jason,
I checked again and there were no program files (i.e. C:\Program Files\Red Gate) on the passive node. I took your advice and then ran the installer on the passive node and it looks like ever...
QA message when SQL is running on Server B:
"Trial has expired."
Server A with same command runs the master backup fine.
Matt / comments
QA message when SQL is running on Server B:
"Trial has expired."
Server A with same command runs the master backup fine.
Matt
Works fine now...thanks. / comments
Works fine now...thanks.
As far as I can tell SQL BAckup is installed on both nodes. I followed the instructions given to me from the Red-Gate salesperson for installing in the clustered environment. Those instructions were a reference to a forum post. / comments
As far as I can tell SQL BAckup is installed on both nodes. I followed the instructions given to me from the Red-Gate salesperson for installing in the clustered environment. Those instructions wer...
The job failed. The Job was invoked by Schedule 120 (<Name Removed> Full Backup Schedule). The last step to run was step 1 (Step 1).
This error is from the job history in EM. I assume that was the error message being referred to. / comments
The job failed. The Job was invoked by Schedule 120 (<Name Removed> Full Backup Schedule). The last step to run was step 1 (Step 1).
This error is from the job history in EM. I assume that was th...
My issue was not an issue. The DB that I was trying to restore has just seen it's load increase and I still had users in it thus the exclusive access message. The clear connections in Detach DB via Ent Manager didn't work. I had to take the DB offline and then bring it back online and then run the restore.
In my script I was putting the DB in single user mode but apparently that was not doing the trick. Is there a way via script that I can take the db offline & back online right before I run the restore command?
thx
matt / comments
My issue was not an issue. The DB that I was trying to restore has just seen it's load increase and I still had users in it thus the exclusive access message. The clear connections in Detach DB via...