Error adding second VMware Identity Manager node to external SQL database

[saravm2010]

Hello all,

I am new to VMware Aria Automation. I am trying to deploy three VMware Identity Manager (vIDM) 8.18 appliances and connect them to an external Microsoft SQL server database.

My database is SQL Server 2016 running on Windows Server 2016 (as VMware support list) The first vIDM appliance connects to the external database successfully and completes the setup. However, when I deploy the second vIDM appliance, the database connection test is successful, but during configuration I receive the following error:

"Error during initialization"

This prevents the setup from completing. 

Good to mention after the mentioned error I tested the scenario with two SQL servers always on enabled but the same error.

Has anyone experienced this issue before? How should I properly join additional vIDM appliances to the same external SQL database cluster?

Thank you for your guidance.

-------------------------------------------

[Shen88]

@saravm2010,

1. Verify First Node Setup

   - Confirm the first node completed setup and is operational.

   - Check that the database schema is intact and accessible.

2. Use the Cluster Join Option

   - When deploying the second and third appliances, choose the option to _join an existing cluster_.

   - Do not re-enter database initialization parameters.

3. Configure Load Balancer

   - Set up a load balancer (e.g., HAProxy) with the VIP.

   - Ensure health checks and routing are properly configured.

4. Delegate IP Setup

   - Assign a delegate IP on the same subnet as the appliances.

   - This is used internally by vIDM even if SQL Server is external.

5. Check Logs

   - Review `/var/log/bootstrap/firstboot.log` and `/opt/vmware/var/log/vmware/` for detailed error messages.

   - Look for schema conflicts, connectivity issues, or permission errors.

Also, this guide walks through clustered vIDM deployment with load balancer and IP planning: [Aria Suite Lifecycle and vIDM Cluster Setup]

(https://www.aaronrombaut.com/vmware-aria-suite-lifecycle-vmware-identity-manager-vidm/)

(https://techdocs.broadcom.com/us/en/vmware-cis/other/vmware-identity-manager/3-3/idm-windows-installation-map-3-3/about-installing-and-configuring-vmware-identity-manager-windows.html) 

------------------------------
If you find this answer right, please 'Recommend' this post.

Thank you!

Regards,
Shen
------------------------------

[saravm2010]

Thank you Shen88

Step 1 is done and everything is ok. But I can not find any cluster join option while setting up the second node! The only available option while connecting to the external DB is as below screen. Can you guide me where is join cluster option?

Thanks in advance

-------------------------------------------

[Jens Albrecht]

Hello, 

unfortunate a vIDM cluster can only be used with the embedded vPostgres database. If you really require to use an external database server then you'll need to use a single instance.

I would however recommend to use the embedded vPostgres database either single node or cluster deployment.

I do also recommend to use Aria Suite Lifecyle Manager to deploy your vIDM instance: Install VMware Workspace ONE Access in VMware Aria Suite Lifecycle

[saravm2010]

Thanks Jens Alrecht

But in VMware Identity guide 3.3 in broadcom there is a part named "Database Options with Directories Management". in this part it was mentioned that:

Set up Directories Management with an external Microsoft SQL database to store and organize server data. An internal PostgreSQL database is embedded in the appliance but it is not recommended for use with production deployments.

I am eager to know why do you recommend Aria Suite Lifecyle Manager for embedded vPostgres database?

Thank you

-------------------------------------------

[Jens Albrecht]

Hello,

yes the documentation version 3.3.x for the Windows installation does mention that the internal PostgreSQL database is not recommended, we've  kept that part available for older versions. However only version 3.3.7 is currently supported and can only be deployed as an Appliance.

Which you may have noticed the VMware Identity Manager documentation does not mention anything about the Appliance installation, only the Upgrade is documented. 

For deploying a clustered vIDM instance it is much simpler to use the deployment from Aria Suite Lifecyle Manager, as this will take care of the configuration of the cluster and also provides additional features for Postgres clustering, like the health check and auto-recovery:

Scheduled health checks

What's VMware Identity Manager Cluster Auto-Recovery in VMware Aria Suite Lifecycle 8.14

As your VCF license is bundled for both products I would see no reason not to use Aria Suite Lifecyle Manager for the deployment.

Regards,
Jens

-------------------------------------------

[saravm2010]

Hello,

Thanks a lot for the detailed clarification and explanation, it was very helpful. I just want to make sure I understood you correctly.

1-You mentioned "we've  kept that part available for older versions" you mean the recommendation for not using internal PostgreSQL database was for older VMware Identity Manager versions ? And Current IDM 3.3.7 is only available via OVA file ?

2- I read IDM Help again. It is true that it refers to windows installation, but there is a section on the page 250 for Linux installation as well and the recommendation is just mentioned here. As far as I knew this part and recommendation is for older IDM versions with OVA appliances format. Am I right?

Thanks in advance

-------------------------------------------