6.4 Upgrade Registry Surprise
DonFerguson
Posts: 202 Silver 5
It appears that with version 6.4 the registry location for 64 Bit machines was moved from "HKLM\SOFTWARE\Wow6432Node\Red Gate\SQL Backup" to "HKLM\SOFTWARE\Red Gate\SQL Backup". While most of the keys were automatically copied to the new location running the SQBServerSetup.exe in silent mode, the datapath key was not. It instead defaulted to the C: path instead of the shared drive path that I use on the PolyServe clusters.
After burning a few hours, I was able to resolve this, so this post it to just confirm the issue, and make you aware that the datapath gets reset on installation. That in turn messed up log shipping.
After burning a few hours, I was able to resolve this, so this post it to just confirm the issue, and make you aware that the datapath gets reset on installation. That in turn messed up log shipping.
Comments
The installer works with the Microsoft clustering service to determine the shared drive assigned to the chosen SQL instance. Since you're using a different clustering provider (I'm not familiar with PolyServe) I expect the installer chose the default path and overwrote any existing datapath value. However, if the key already exists its value could be respected.
I've raised your scenario as a bug, with the intent that future versions of the installer will not initialise the datapath if an existing value can be found.
I'm sorry to hear that you had this problem with the upgrade. Thanks for reporting this.
Regards,
Development
Red-Gate Software
Cheers,
Development
Red-Gate Software