To see this working, head to your live site.

Clustering multiple VarAC instances over network

It is often more practical to have multiple instances of VarAC, each running on different PCs, with all the PCs connected to the same local area network, but possibly not even in the same room. In the same way as the existing clustering works runs multiple instances of VarAC on the same PC, it would be great to share the VarAC database and environment between multiple PCs over a local area network, with each PC running a unique VarAC instance. In this scenario there may be multiple instances of VarAC on different HF beands, and/or multiple VARA FM instances connected to different radios and antennas, but not necessarily co-located, but linked via the same local area network.

Will this be considered as a further development of the existing clustering mode?

4 comments

4 Comments

NC3Z Gary

May 28

Been a feature for a good while. Take a look at this https://www.varac-hamradio.com/forum/manuals-troubleshooting/varac-cluster-multiple-instances-quick-configuration-guide

zs2ok Alister

May 29

Replying to

The quoted solution requires the cluster to run on a single PC. That will work for specific scenarios. However, my requirement is a "networked cluster" running across a local area network with each instance of VarAC running on different PCs. These PCs may be in different rooms in a facility, connected via a local area network. Using different PCs and different locations within a facility may be necessitated due to various operational and physical requirements, e.g. VHF Yagi antennas which cannot be co-located.

NC3Z Gary

May 29

Replying to

I am the one that actually wrote that up, my cluster is indeed running across 3 PC's networked. You will see in one of the screenshots that the exe shortcut is set to a "mapped" drive. This is how the db will work.

zs2ok Alister

May 30

Replying to

Thanks for that clarification!

To clarify my understanding, and referring to the image below taken from your write up, both the VarAC application and the database resides on Drive V (on the "central" PC). Therefore from the "remote" PC's perspective it runs another VarAC instance locally from the "central" PC and shares the database via a local area network with the "central PC. That's creative!

Edited