High Availability with Pulse

Pulse App Server takes a couple of minutes to start, so you don’t really need to set up High Availability (HA) for Pulse.
However, if HA is required for your environment, here are the key points:

✅ Database High Availability

Pulse stores its data in a relational database (H2, Postgres or MSSQL Server). You can configure the database in a clustered or replicated setup to ensure HA, as long as the connection string points to the HA cluster.

✅ Pulse Application Server High Availability

Pulse does not have built-in clustering, but you can achieve HA by:

• Deploying multiple Pulse App Servers behind a load balancer.

• Connecting all Pulse servers to the same Pulse database.

• Synchronizing configuration files (e.g., Pulse.cfg) across servers.

⚠️ Considerations

• Each Pulse App Server should monitor no more than 100 TM1 servers.

• HA adds complexity: more maintenance during upgrades and harder data comparison if multiple Pulse instances are used.

• Updates must be applied to all Pulse servers in the HA setup.