60 likes | 199 Views
Overview of CUNY Aleph migration 18 -> 21. Aleph v21 Upgrade Phase 1- 3 Create v21 Environments. P h a s e 1 : M a r c h/ A p r i l 2 0 1 4. Config / DB. Config / DB. U-Tree. Config / DB. TEST Aleph 21 . PROD Aleph 18 . Config / DB. Phase 2: July 10 -25, 2014. STAGE
E N D
Aleph v21 Upgrade Phase 1- 3Create v21 Environments Phase 1: March/April 2014 Config / DB Config / DB U-Tree Config / DB TEST Aleph 21 PROD Aleph 18 Config / DB Phase 2: July 10 -25, 2014 STAGE Aleph 21 Config / DB Config / DB PROD Aleph 21 Phase 3: July 10 -25, 2014
Aleph v21 Upgrade Phase 1Copy v18 PROD Config / DB -> v21 STAGE Environment Config STAGE Aleph 21 Config / DB Phase 1: March/April, 2014 PROD Aleph 18 DB OLS deploys Aleph v21 STAGEGUI clients for CUNY-wide testing / training late April, 2014 STAGE Aleph 21
Aleph v21 Upgrade Phase 2Copy v21 STAGE Config -> v21 PROD/TEST Environments Config PROD Aleph 21 Config STAGE Aleph 21 Config Phase 2: July 10 -21, 2014 TEST Aleph 21
Aleph v21 Upgrade Phase 3Copy Aleph v18 PROD DB -> v21 PROD DB -> v21 TEST Phase 1 U-Tree DB STAGE Aleph 21 PROD Aleph 18 DB Phase 3: July 10 - 25 2014 PROD Aleph 21 OLS deploys Aleph v21 PROD GUI clients for testing, July 11-18, 2014. Cutover to v21 production July 21 DB TEST Aleph 21
Cutover to CUNY Aleph v21July 10 - 21 X PROD Database Aleph v18 PROD Aleph v18 • Aleph v18 database is READ ONLY • No transactions whatsoever: ACQ, CAT, CIRC, CAT, CR, ILL, data loads - ZIPPO • Circulation is offline only • OPAC is available for searching