Both BioStar 1 & BioStar 2 do not officially support failover server feature. However this may be achieved with third party applications.
For BioStar 1, the failover feature can be implemented using 3rd party server application.
For example, Windows Server 2012 (or 2008) has the failover functionality like the following:In the scenario below, all the devices are connected to BioStar Server via the Server mode. When you do clustering, you will get a virtual IP address and the server IP address of the devices should set to the virtual IP address (10.10.10.3).The actual IP addresses are hidden and managed by the clustering system.Let’s say the server IP address of the devices is “10.10.10.3” and the devices have 10.10.10.3 as its server IP address. But the devices are actually connected to the active server (Server A in the example below).When Server A is down, Server A becomes stand-by and Server B becomes active. Then, even though all the devices have “10.10.10.3” as its server IP address, they will be connected to Server B(10.10.10.5).Since both servers are connected to the same database (the database server should be separated), we don’t have to worry about the data synchronization. If you want to use virtual servers, you also need to utilize third-party virtual machine software like VMWare or Hyper-V.
Refer to the attachment for different methods and scenarios.
The attached document was originally written based on the SQLite database of BioStar 2 which was provided up to BioStar Version 2.2.1.
Now BioStar 2 features MariaDB as the default database. The backup process will be different and you will be able to use the replication feature of Maria DB.
Please refer to the following external article: Setting Up Maria DB Replication