synchronize but keep original source ae title
I have setup 2 Pacsone. One on site, and another offsite. I have the offsite setup to synchronize with the on site Pacsone. Is there a way to make the offsite pacsone to keep the original source ae titles of the on site pacs?
If you to have the backup PacsOne to have the same AE Title of the primary PacsOne, then it seems you want a redundant setup with a primary and backup PacsOne Server sharing the same AE Title, and only one of them will be used at any time.
If this is the case, there is a simpler and more efficient configuration for redundancy:
1. Setup identical version of PacsOne and MySQL on the primary and backup servers.
2. Use a shared network storage (e.g., NAS, SAN, etc.) as the Archive Directory for storing received images on both primary and backup PacsOne Servers. This way, the storage paths for received images are identical for both the primary and backup PacsOne Server, and there is no need to move any images from one server to the other.
3. Enable MySQL Replication feature so that the backup PacsOne Server automatically replicates with the primary PacsOne Server.
This configuration provides a full redundancy with a primary and backup PacsOne Server, and it's also more efficient than the Dicom synchronization because only the MySQL databases need to be synchronized but there is no need to move any images, as they are stored in shared network storage which contain the same paths for both the primary and backup PacsOne Servers.
If this is the case, there is a simpler and more efficient configuration for redundancy:
1. Setup identical version of PacsOne and MySQL on the primary and backup servers.
2. Use a shared network storage (e.g., NAS, SAN, etc.) as the Archive Directory for storing received images on both primary and backup PacsOne Servers. This way, the storage paths for received images are identical for both the primary and backup PacsOne Server, and there is no need to move any images from one server to the other.
3. Enable MySQL Replication feature so that the backup PacsOne Server automatically replicates with the primary PacsOne Server.
This configuration provides a full redundancy with a primary and backup PacsOne Server, and it's also more efficient than the Dicom synchronization because only the MySQL databases need to be synchronized but there is no need to move any images, as they are stored in shared network storage which contain the same paths for both the primary and backup PacsOne Servers.
Yes, your assumption is correct as if the NAS dies neither the primary nor the backup PacsOne Server would be able to store any more images into the NAS. To reduce the risk of NAS failures, you can use RAID to make it more fault tolerant.
If you use local storage for the primary and backup PacsOne Servers, then there will be 2 copies for each image stored, one on the primary and the other on the backup PacsOne Server. You'll need to use either the Auto-Route or the Synchronization feature of PacsOne to synchronize the Dicom images on the backup with the primary PacsOne Server. In this case, you need to define an AE with the same AE Title on both the primary and backup PacsOne Server, but it should be configured with the hostname/IP address of the server where other PacsOne resides. As far as the external Dicom world is concerned, there is only a single AE with the AE Title of the PacsOne Server, and they don't need to know that it's actually a redundant setup consists of both a primary and backup PacsOne Server.
If you use local storage for the primary and backup PacsOne Servers, then there will be 2 copies for each image stored, one on the primary and the other on the backup PacsOne Server. You'll need to use either the Auto-Route or the Synchronization feature of PacsOne to synchronize the Dicom images on the backup with the primary PacsOne Server. In this case, you need to define an AE with the same AE Title on both the primary and backup PacsOne Server, but it should be configured with the hostname/IP address of the server where other PacsOne resides. As far as the external Dicom world is concerned, there is only a single AE with the AE Title of the PacsOne Server, and they don't need to know that it's actually a redundant setup consists of both a primary and backup PacsOne Server.
If you setup the MySQL Replication for the primary and backup PacsOne Server, then the Application Entity table will be replicated on both servers, so you will not be able to define an AE on one PacsOne Server for the other PacsOne (because the database is replicated), so you will not be able to have the backup PacsOne synchronize with the primary PacsOne as the AE table will be overwritten by the MySQL replication.
So the best way to use MySQL Replication is to use a shared storage for both the primary and backup PacsOne Server, and use MySQL Replication to synchronize the 2 databases.
If you don't want to use shared storage for the 2 servers and want to keep 2 copies of each received images on both the primary and backup PacsOne Server, then you should not use MySQL Replication, but instead use the Automatic Synchronization feature of PacsOne to have the backup PacsOne synchronize with the primary PacsOne (you can call this PacsOne Replication).
So the best way to use MySQL Replication is to use a shared storage for both the primary and backup PacsOne Server, and use MySQL Replication to synchronize the 2 databases.
If you don't want to use shared storage for the 2 servers and want to keep 2 copies of each received images on both the primary and backup PacsOne Server, then you should not use MySQL Replication, but instead use the Automatic Synchronization feature of PacsOne to have the backup PacsOne synchronize with the primary PacsOne (you can call this PacsOne Replication).