Page History

...

Prerequisites

1. A minimum of 12.8TB 0TB free space on the extract destination drive. You don't need a full database footprint as the extract files are compressed.
2. Solid State Drives are recommended due to required for better performance. 
3. Network connectivity between the two PostgreSQL databases is required. It is also possible to use a separate server either as an intermediary or to share the extract destination drive, e.g., via NFS between the current and new instance.

...

Stop apgupd before proceeding (See apgupd for instructions.)

Extract the data from both the xml and cdws all applicable schema to the storage location.

First, the script:

cd-extract -h

Usage: cd-extract.sh OPTIONS

  Option        Description                     Default
  --------------------------------------------------------
  -H|--host     specify host                    localhost
  -P|--port     specify port                    5432
  -d|--database specify database                alexandria
  -u|--user     specify database username       alexandria
  -h|--help     print this usage and exit

Examples:

cd-extract -h 10.10.10.2 -p 5432 -d alexandria -u alexandria
cd-extract -h localhost -d alexandria -u alexandria

...

1. A new CLAIMS Direct instance. Please see the PostgreSQL Installation Instructions for step-by-step instructions.
2. Access to the extract directory which contains the data directory of the files created above. This could be via the older local CLAIMS Direct instance, an intermediate server, or a shared drive.
3. Installation of supplementary streams, e.g., litigation, entities etc., see installation instructions.

Process

Loading the data is accomplished in much the same way you loaded the original CLAIMS Direct instance: cd-load.sh or load.sh for earlier installs.

...