*** This version of Confluence is for testing only and contains a copy of content from June 29th 2026. No changes will be preserved. ***
Environment Definitions
FOLIO Production = the FOLIO Production application server, which is the data source for reporting databases
LDP = our current LDP production reporting database
Metadb1 = our current Metadb Production production reporting database
Metadb2 = a separate Metadb reporting database that does not become Metadb Production until updates, synchronization, and testing processes are complete (2-3 weeks)
Cutover Scenarios to Consider - Scenario 1 and Scenario 2
SCENARIO 1 (PREFERRED) | |||
| 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 application server is upgraded from PostgreSQL version 12 to |
16 |
. LDP is retired. FOLIO Production is set up as source for continued streaming data to Metadb1. |
start February 7, 2025 |
| Metadb1 | FOLIO Production Metadb2 |
| Metadb2 is upgraded from PostgreSQL version 12 to 16. Start data resynchronization process between FOLIO Production application server and |
| Metadb2 reporting database. |
for one week following |
| Metadb1 |
| Metadb2 | Reporting Team tests data accuracy and performance on updated and resynchronized Metadb2 reporting database. | ||
March 1 | Metadb2 or Metadb1, depending on "Go/No Go" decision | Metadb1 | If decision is a "Go," Metadb2 becomes the production reporting database and Metadb1 is retired. Reporting Team sets 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 address changes are needed on the reporting user end. If decision is "No Go" Metadb1 continues running as the production reporting database until Metadb2 is working properly. |
OR
SCENARIO 2 (BACKUP) | |||
| Date | Cornell Production Reporting Database | Environment Changes | Activity |
|---|---|---|---|
| February 3 - 7, 2025 | LDP | LDP | Reporting |
Reporting
| Team sets up dashboards, automated reports, and other |
| processes to use |
| LDP as data source during cutover period | |||
| February 7, 2025 | LDP | LDP | FOLIO Production application server 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 application server and Metadb1 reporting database |
for one week following |
24-28 | LDP |
depends on
| Metadb1 | Reporting Team tests data accuracy and performance on updated and resynchronized Metadb1 reporting database. | |
March 1 | LDP |
or Metadb1, depending on "Go/No Go" decision | If decision is a "Go," LDP is retired. If decision is "No Go" LDP continues running until |
Metadb1 is working properly. | If "Go |
," Reporting Team sets 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. |
NOTES: