Installation guide

Understanding parallel migration
(Topic number: 123301)
With a serial migration, upgrades from one version of IMPAX to another have two distinct phases:
1. A preparing to upgrade period, which can last weeks, during which initial installations are
performed, some data is migrated in advance, and users are trained on the new system.
2. An upgrade period, typically performed over a weekend, during which the IMPAX software
and database are upgraded from the previous to the new version.
After the upgrade period, users switch over to using the new version exclusively.
With a parallel migration, by contrast, both the previous and the upgraded versions of IMPAX run
simultaneously for a period of time, which could last weeks or months. Cluster linking is deployed
to keep the two clusters in synchronicity with each other. Parallel migrations require that a new
Database Server be deployed (rather than upgrading the existing one). Downtime is greatly reduced,
and users transition more gradually from the previous system to the new version.
When using direct attached archives, it can take a long time to move the archive data from that
system to a new HSM archive. Therefore, it becomes necessary to use a parallel migration approach.
(Direct attached archives are not supported in IMPAX 6.5.3.)
DAA consolidation
(Topic number: 123304)
A Direct Attached Archive (DAA) is a non-networked long-term storage device directly connected
to a server. IMPAX 6.4 and later versions do not support DAA. Therefore, all legacy IMPAX systems
with DAA that upgrade to IMPAX 6.5.3 must migrate the obsolete DAA to a network-based archive;
that is, to DICOM PACS Store and Remember or to HSM archiving.
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
AS300 Upgrade and DAA Consolidation Guide—IMPAX 5.2 or 5.3 to IMPAX 6.5.3 13
Agfa Company Confidential—Subject to Non-Disclosure Obligation