You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

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 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)

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.

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 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.

OR


SCENARIO 2 (BACKUP)

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


LDPLDP 

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

LDPMetadb1 Start data resynchronization process between FOLIO Production and Metadb1.

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

LDPMetadb1 

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.




NOTES:







  • No labels