Have you success configured one cluster vIDM with a SQL AAG?
Because when I switch AAG on other SQL, I have a msg in the log of SQL Server, "login failed for user "Horizon" error 18456 / 14/ 38"
And my vIDM is down.
When I create the database Saas, I used this script. But after that database is created, I add this DB on AAG but on second server I don't have this user SQL "horizon". I add manually this user SQL, but I must forget one configuration for this account because it's doesn't work.
Is there a script to create the user on the second SQL server?
Thanks all, for reply
If you want vIDM have clustered I have a few tips:
- Use 2.9.1 instead of 2.8.1 :smileyalert: (please do.... forget 2.8.1. clustered....)
- Use SQL 2014 at minimum
- Deploy 1 vIDM with Active Directory Configuration as it should be (so, vIDM fully configured) (and ofcourse, with the connection/configuration to database...)
- Turn the Appliance off (graceful shutdown), and do a clone of that machine, you will get questions about installation of the 2nd appliance (so configure it, with your settings for the 2nd appliance, ip, hostname etc etc etc, you will get it in the clone proces, and after that, clone the first one again for the 3rd)
- When cloning is done, turn on the first appliance, wait until fully loaded, turn on 2nd node, and when it is finished, turn on the 3rd node...
You should be fine than, you have a clustered configuration which uses 1 SQL database
Thanks you for reply,
But I Have Horizon 7.0.3 and on VMware Product Interoperability Matrices , only vIDM 2.8.1 is supported. I prefered vIDM 2.9.1 or later but it's not compatible.
But on vIDM and SQL AAG, how to create the user SQL "horizon" on second SQL server? Because when I create manualy on the second server and when I switch my DB on second SQL, vIDM don't access at DB with error on second SQL server in my first post.
Sorry for my misunderstanding, but... you want to use multiple SQL servers for use with cluster IDM?
The proces of creating a clustered vIDM proces for 2.9.1 is the same for 2.8.1, but in 2.8.1. there is an issue with clustering
I would suggest to ask VMware for interoperability with Horizon 7!