SCENARIO 1 (PREFERRED)

FOLIO Production 
LDP
Metadb1
Metadb2

FOLIO Production

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
end Feb 14 - 21, 2025

for one week following
synchronization end:
February 17-21
OR
February 24-28

Reporting Team tests data accuracy and performance on updated and resynchronized Metadb2

. 
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

Metadb2 or Metadb1, depending on "Go/No Go" decision

Metadb1
Metadb2

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.

SCENARIO 2 (BACKUP)

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
end Feb 14 - 21, 2025

for one week following
synchronization end:
February 17-21
OR
February 24-28

Reporting Team tests 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

Metadb1

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.