Please enable JavaScript.
Coggle requires JavaScript to display documents.
DB2_logo
hFL DB2
Migration Options, Research :question:, Risk :warning:…
hFL DB2
Migration Options
Reduce data footprint
ClearWater Project
- Garry Belsham confirmed 27/1/21 that the scope is to remove the GIAD schema only, which is around 175GB in PD (according to Suresh).
- Decommission not planned until Q1 2022
FPIL Separation
- GIAD Decomm: Emerged during discussions about FPIL separation who confirmed they no longer require GIAD data after Q1 2021.
- Linked somehow to a move to ClearWater which may provide further data decomm options (Bloomberg, Morningstar) - comment from Sam 11/11/20.
-
Migrate to S3 Data Lake
OLAB Project
- Scope includes copying following DB2 datasets to S3: Galahad, UK/Intl BaNCS RDS/ IBM ULL/ULP, Compass Armarta, Apollo, Climate, Pegasus, WLUK.
- Not all tables from above systems are in scope for storing in S3.
Identify other datasets that suit being stored in S3
Migrate to another RDBS
hFL Oracle on EC2
- Need to understand volume of data to migrate before this can be investigated further.
- DB2 to Oracle is a supported migration path.
Postgres RDS or Aurora Postgres RDS
- Risks raised under Technical Assessment require review and acceptance before considering using Postgres.
Oracle RDS
- If technically feasible and performance is acceptable.
Redshift
- Seeking approval from Lewis Longman-Jones to PoC Redshift as a possible target.
-
-
-