Task #8566
closed
"Rehearsal" of Production Jackrabbit Migration from Derby to PostgreSQL
100%
Updated by Massimiliano Assante almost 8 years ago
This ticket track the "Rehearsal" of Production Jackrabbit Migration from Derby to PostgreSQL related to the steps listed in #8562
Updated by Massimiliano Assante almost 8 years ago
- Status changed from New to In Progress
Updated by Massimiliano Assante almost 8 years ago
- % Done changed from 0 to 50
The production copy of yesterday did not work out as only the folder containing the DERBY DB was copied. Today @tommaso.piccioli@isti.cnr.it copied the whole /home/gcube folder of production and the migration process started without exceptions at 17.13 CEST. It should last about 7 hours.
Updated by Massimiliano Assante almost 8 years ago
the migration process is now working with no exception but we have some issues in starting up the repo after the migration is completed...
Updated by Massimiliano Assante almost 8 years ago
the issues in starting up the repo after the migration is completed have been fixed by running a consistency check
Updated by Costantino Perciante almost 8 years ago
Just to be sure that everything is provisioned, both machines workspace-repository-prod1.d4science.org and workspace-repository-prod.d4science.org are going to be recreated with ansible from scratch. Look at the sub-ticket with the details of the configurations. @tommaso.piccioli@isti.cnr.it already created a snapshot this morning which will be used for the latest (we hope) test, before the real migration scheduled for next week.
Updated by Andrea Dell'Amico almost 8 years ago
- Due date changed from May 18, 2017 to Jun 23, 2017
due to changes in a related task
Updated by Costantino Perciante almost 8 years ago
migration test has restarted at 15:50 23/06/17
Updated by Costantino Perciante almost 8 years ago
migration ended at 22:39 23/06/17
consistency check/fix start running at 8:37 24/06/17
Updated by Costantino Perciante almost 8 years ago
jackrabbit restarted at 15:50 (24/06/17) after consistency check and fix (it seems ok)
Updated by Massimiliano Assante almost 8 years ago
the overall time to complete the procedure is much higher than before, about 7 h for the migration and about 6h for the consistency check? I'm guessing the DB isn't local right? @costantino.perciante@isti.cnr.it
Updated by Costantino Perciante almost 8 years ago
it has been still used a local db. Perhaps both VMs have less RAM/CPU than before @andrea.dellamico@isti.cnr.it ?
Updated by Andrea Dell'Amico almost 8 years ago
Costantino Perciante wrote:
it has been still used a local db. Perhaps both VMs have less RAM/CPU than before @andrea.dellamico@isti.cnr.it ?
Nope. The VM is the same, I only (re)installed smartgears and the home library webapp.
Updated by Andrea Dell'Amico almost 8 years ago
Massimiliano Assante wrote:
the overall time to complete the procedure is much higher than before, about 7 h for the migration and about 6h for the consistency check? I'm guessing the DB isn't local right?
The DB was local. It will moved to the remote server after the real migration.
I still don't know why a remote DB should be slower than a local one, btw.
Updated by Massimiliano Assante almost 8 years ago
- Status changed from In Progress to Closed
"Rehearsal" of Production Jackrabbit Migration from Derby to PostgreSQL went fine
