*** This version of Confluence is for testing only and contains a copy of content from June 29th 2026. No changes will be preserved. ***
...
Metadb2 = a separate Metadb reporting database that does not become Metadb Production until updates, synchronization, and testing processes are complete (2-3 weeks)
3 Cutover Scenarios to Consider
...
SCENARIO 1 (PREFERREDMETADB1 and METADB2) | |||
| Date | Cornell Production Reporting Database | Environment Changes | Activity |
|---|---|---|---|
| February 3 - 7, 2025 | LDP | LDP and Metadb1 | Reporting Team sets up dashboards, automated reports, and other processes to use Metadb1 as data source during cutover period |
| February 7, 2025 | Metadb1 | FOLIO Production | FOLIO Production is upgraded from PostgreSQL version 12 to 16. FOLIO Production is set up as source for continued streaming data to Metadb1. LDP is saved, but "frozen" without data updates. |
start February 7, 2025 | Metadb1 | FOLIO Production Metadb2 | Metadb2 is upgraded from PostgreSQL version 12 to 16. Start data resynchronization process between FOLIO Production and Metadb2. |
for one week following | Metadb1 | Metadb2 | Reporting and Automation Teams test data accuracy and performance on updated and resynchronized Metadb2. |
March 1 | Metadb2 or Metadb1, depending on "Go/No Go" decision | Metadb2 | If decision is a "Go," Metadb2 becomes the production reporting database, and Metadb1 and LDP are retired. Reporting and Automation Teams set up dashboards, automated reports, and other processes to use Metadb2, or Hosting Team makes a seamless switch from Metadb1 to Metadb2 host addresses such that no host address changes are needed. If decision is "No Go" Metadb1 continues running as the production reporting database until Metadb2 is working properly. |
OR
SCENARIO 2 (BACKUPLDP KEEPS RUNNING) | |||
| Date | Cornell Production Reporting Database | Environment Changes | Activity |
|---|---|---|---|
| February 3 - 7, 2025 | LDP | LDP | Reporting and Automation Teams set up dashboards, automated reports, and other processes to use LDP as data source during cutover period. |
| February 7, 2025 | LDP | LDP | FOLIO Production is upgraded from PostgreSQL version 12 to 16. FOLIO Production is set up as source for continued nightly LDP data transfers. |
start February 7, 2025 | LDP | Metadb1 | Start data resynchronization process between FOLIO Production and Metadb1. |
for one week following | LDP | Metadb1 | Reporting and Automation Teams test data accuracy and performance on updated and resynchronized Metadb1. Based on results of testing, Cornell makes "Go/No Go" decision to continue using LDP or to start using Metadb1 as production reporting database. |
March 1 | LDP or Metadb1, depending on "Go/No Go" decision | LDP | If "Go," Reporting and Automation Teams set up dashboards, automated reports, and other automation processes to use Metadb1. If "No Go," LDP continues to serve as production reporting database until Metadb1 is working properly. |
OR
SCENARIO 3 (REPORTING DATABASE SNAPSHOT SYNC) | |||
| Date | Cornell Production Reporting Database | Environment Changes | Activity |
|---|---|---|---|
| February 3 - 7, 2025 | Metadb1 | Metadb1 | Reporting and Automation Teams set up dashboards, automated reports, and other processes to use Metadb1 as data source during cutover period. |
| February 7, 2025 | LDP | Metadb1temp Metadb1original | Snapshot of Metadb1 reporting database is taken (e.g., pg_dump) and restored to a temporary PostgreSQL instance that is still on version 12 (Metadb1temp). Pause Debezium connector. FOLIO Production is upgraded from PostgreSQL version 12 to 16. Reconnect the upgraded FOLIO Production server to Metadb1temp and start Debezium to continue data streaming. Use Metadb1temp for reporting during the upgrade and resynchronization of Metadb1original. |
start February 7, 2025 | Metadb1temp | Metadb1original | Metadb1original is upgraded from PostgreSQL version 12 to 16. Use Debezium Connector between Metadb1temp and Metadb1original to capture changes that took place during the upgrade process (resynchronize). Once the upgrade and resychronization processes are complete on Metadb1original, switch the connection to the FOLIO Production server from Metadb1temp to Metadb1original. |
for one week following | Metadb1temp | Metadb1original Metadb1temp | Reporting and Automation Teams test data accuracy and performance on updated and resynchronized Metadb1original. Based on results of testing, Cornell makes "Go/No Go" decision to continue using Metadb1temp or to start using Metadb1original as production reporting database. |
March 1 | Metadb1original or Metadb1temp, depending on "Go/No Go" decision | Metadb1original Metadb1temp | If "Go," Reporting and Automation Teams set up dashboards, automated reports, and other automation processes to use Metadb1original, or Hosting Team makes a seamless switch from Metadb1temp to Metadb1original host addresses such that no host address changes are needed. If "No Go," Metadb1temp continues to serve as production reporting database until Metadb1original is working properly. |
NOTES:
-Would using snapshots help?
...