Hello,
This post originally started in the Government VOGUE group and was recommended to ask our question here in the Database Technical Forum.
We have already reviewed the Database Reference Guide, Disaster Recovery and High Availability guide, along with other referenced materials within Hyland's and Microsoft's documentation, but we have still been left with unanswered questions in reference to the AlwaysOn and RecreateDBUsers.exe utility usage/need. Perhaps there is someone that may be able to provide us a more simple and/or direct response.
We have reached out to our FLOS previously for guidance, but did not receive the direction/information we were looking for. This led us to posting in Hyland Community for guidance.
In your Production environment, do you have for disaster recovery a database failover from site A to site B?
If so, how did you get passed the need to run RecreateDBUsers.exe utility manually?
Our environment is a SQL AlwaysOn Availability Group, not a SQL database mirror, where we are expecting an automatic failover. Initially, during our testing we found that we had to run RecreateDBUsers.exe utility after the initial failover from Primary to Secondary. Then we had to run it again when failing over from Secondary to Primary, as we were having issues logging into the Thick Client(s), but we did not have issues logging into the Web Client.
After that round, we discovered that we were not syncing the SQL logins. We went ahead with a SQL login sync from Primary to Secondary, one time and only ran into one server issue where we were unable to login via the Thick Client, but all other servers we were able to login successfully to the Thick Client.
Failover back to Primary was successful and while now we're scratching our heads on the previous 1 lone Thick Client login issue, it would seem that Primary/Secondary are synced and we did not have to run the RecreateDBUsers.exe utility at all. The OnBase Web Client maintained successful login during both failover tests.
Prior to the previous round, we had also reached out to our FLOS who was not able to provide adequate direction and we had researched the RecreateDBUsers.pdf that is included with the download from Hyland's Community site for the utility.
The document discusses (on page 9) the ability to run the utility with command line switches, giving us the idea that one could put the utility into a script/batch file, to execute should there be a logging into OnBase issue upon failover; calling the utility executable within the batch to run to resolve OnBase login issues.
The problems with this are how to set the trigger to listen for failover to occur to run the batch file and the command line switch listed for the SQL server login account's password is unencrypted. So one probably would not want to use the SA account/password in this scenario. However, with our latest testing, it doesn't seem necessarily necessary to run the utility. In fact, we surmise that running the utility will unsync the SQL logins at this point in time.
We were hoping there was a simpler or more direct way of not having to have manual intervention of a failover.
Thank you, in advance to anyone who is able to provide more information.
