Versions Compared

Old Version 13

changes.mady.by.user Sharon Helen Markus

Saved on

compared with

New Version 14

changes.mady.by.user Sharon Helen Markus

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

SCENARIO 1 (PREFERRED)

DateCornell Production 
Reporting Database		Environment ChangesActivity
February 3 - 7, 2025LDPLDP and Metadb1Reporting Team sets up dashboards, automated reports, and other processes to use Metadb1 as data source during cutover period
February 7, 2025


Metadb1

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. LDP is saved, but "frozen" without data updates.

start February 7, 2025
end Feb 14 - 21, 2025

Metadb1FOLIO Production
Metadb2		Metadb2 is upgraded from PostgreSQL version 12 to 16. Start data resynchronization process between FOLIO Production and Metadb2.

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

Metadb1Metadb2 

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 Metadb1 or to start using Metadb1 Metadb2 as production reporting database. 

March 1

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

Metadb2
Metadb1
Metadb2LDP


If decision is a "Go," Metadb2 becomes the production reporting database, and Metadb1 is and LDP are retired.  Reporting 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.

...