HI there,
Does anyone mounted a solution with this technology ?
Is it possible to have it ?
NLB on Pacsone
Hi there
Is there anyone with some solution
I have used the same AE title for both machines used different ips but with NLB used only one ip address (althout) I get in trouble to sent some studies to the pacsone
as an example
Pacsone A
192.168.0.1
port
3511
PAcsone B
192.168.0.2
port
3511
Common IP
192.168.0.3
port
3511
AE Tiltle (on 2 servers)
Pacsone
Database (on 2 servers)
Pacsone
I could tlenet 192.168.0.3 at port 3511 but could not sent images.
Any help ?
I have used the same AE title for both machines used different ips but with NLB used only one ip address (althout) I get in trouble to sent some studies to the pacsone
as an example
Pacsone A
192.168.0.1
port
3511
PAcsone B
192.168.0.2
port
3511
Common IP
192.168.0.3
port
3511
AE Tiltle (on 2 servers)
Pacsone
Database (on 2 servers)
Pacsone
I could tlenet 192.168.0.3 at port 3511 but could not sent images.
Any help ?
Did you add the AE Title of the client Dicom application from which you were trying to send images to PacsOne via NLB?
It should be pretty straight-forward to setup NLB with PacsOne Server running on each node of the NLB cluster, but the difficult part is how to replicate the database among all nodes within the NLB cluster, so that all nodes within the NLB cluster can share a single/common database.
Currently you can configure a master and slave setup of 2 PacsOne Server instances, and use MySQL Replication to synchronize the 2 databases between the master and the slave. But for a NLB configuration, it requires a back-end database serving all nodes within the NLB cluster, and the back-end database may be a cluster itself consisting of a master and slave node with the slave replicating the master node. This configuration requires PacsOne Server to interface with a remote MySQL server, which is not yet supported by the current version of PacsOne since this kind of feature is usually targeted for the high-end market with very high imaging volume and high-availability (HA) requirements.
In any case, adding the ability to interface with a remote database server seems to be a nice feature suggestion, so we'll add it to our To-do list just in case our targeted market segment ever changes.
It should be pretty straight-forward to setup NLB with PacsOne Server running on each node of the NLB cluster, but the difficult part is how to replicate the database among all nodes within the NLB cluster, so that all nodes within the NLB cluster can share a single/common database.
Currently you can configure a master and slave setup of 2 PacsOne Server instances, and use MySQL Replication to synchronize the 2 databases between the master and the slave. But for a NLB configuration, it requires a back-end database serving all nodes within the NLB cluster, and the back-end database may be a cluster itself consisting of a master and slave node with the slave replicating the master node. This configuration requires PacsOne Server to interface with a remote MySQL server, which is not yet supported by the current version of PacsOne since this kind of feature is usually targeted for the high-end market with very high imaging volume and high-availability (HA) requirements.
In any case, adding the ability to interface with a remote database server seems to be a nice feature suggestion, so we'll add it to our To-do list just in case our targeted market segment ever changes.