Installation guide

Different methods exist of transitioning the legacy IMPAX cluster to the new archiving method.
Tools are available to aid in the effort.
Parallel migration and DAA consolidation overview
(Topic number: 123508)
The following diagram depicts a parallel migration with DAA consolidation scenario that does not
require a traveling server. Using this method, the downtime of the production system is reduced to
the time required to do a cold backup. The two IMPAX systems in this scenario can function as
parallel clinical systems, allowing users to slowly transition to IMPAX 6.5.3.
IMPAX 6.5.3 parallel systemPrevious-version IMPAX production system
After the new IMPAX 6.5.3 cluster is installed, the following high-level tasks are performed:
1. Restore a cold backup from the previous-version production system to the new IMPAX 6.5.3
system.
2. Upgrade Oracle and the database schema on the IMPAX 6.5.3 system.
3. Convert the DAA entries to PACS Store and Remember on the IMPAX 6.5.3 cluster and confirm
that DAA studies are accessible.
4. Perform de-referencing tasks (remove reference to DAA locations) on the IMPAX 6.5.3 and
previous IMPAX clusters.
5. Attach an HSM server to the IMPAX 6.5.3 cluster and use Volume Migration Tool to migrate
archive data from DAA to HSM.
This is the upgrade method documented for IMPAX AS300 4.5, 5.2, or 5.3 clusters that use DAA
and for IMPAX AS3000 5.2 or 5.3 clusters that use DAA.
Details are available in the AS300 Upgrade and DAA Consolidation Guide—IMPAX 5.2 or 5.3 to
IMPAX 6.5.3 or the AS3000 Upgrade and DAA Consolidation Guide—IMPAX 5.2 or 5.3 to IMPAX
6.5.3.
AS300 Upgrade and DAA Consolidation Guide—IMPAX 6.2 or 6.3 to IMPAX 6.5.3 11
Agfa Company Confidential—Subject to Non-Disclosure Obligation