gctools-outilsgc / gcconnex

A social network based on Elgg
Other
49 stars 44 forks source link

GCCollab - Managed Service - Restore Collab backup into new MariaDB instance #2534

Closed LecCory closed 1 year ago

LecCory commented 1 year ago

Depends on : gctools-outilsgc/gcconnex#2533 Depends on: gctools-outilsgc/gcconnex#2538

LecCory commented 1 year ago

Copy of schema and data from dev has been moved into the cypher instance of collab. Will need to write scripts to change all instances of gcconnex.local in the DB to the new web app url

LecCory commented 1 year ago

Had to make 1 update to the URL column in: elgg_sites_entity. The site is now accessible, but using dev data. @Phanoix @piet0024 we will need a dump of the prod db I have a Storage account named devdatastorageacc with a container called sqlbkp where the dump can be uploaded, @Phanoix you're an owner on the resource, but I went ahead and gave you blob contributor to avoid any issues.

in the same SA I have a fileshare called data where we can point the copy task that's being worked on to. When we're ready I can generate SAS keys and relay that privately.

Phanoix commented 1 year ago

besides the main sites_entity one, there are probably a bunch of incidental URLs in private_settings that are things like mod config that were generated based on the original site url, those are mostly links to pages or services / endpoints and shouldn't be that important for a quick check of the infra working.

LecCory commented 1 year ago

I used Workbench to query all the tables and find any URLS. The only one that came up was in the elgg_sites_entities table. Once I switched it to the container's URL the site came up. The only URL in private_settings was for the support site. Keep in mind, I grabbed a copy of the schema from dev, I'd imagine we'll see things break once we try to import the prod db into this env.

LecCory commented 1 year ago

I'm not sure if we want to move the prod data into the cypher instance, or if we'd prefer to move it into the current production instance on the current cloud tenant once the resources have been deployed. My preference would be to move the data to the prod instance and keep Cypher running the basic development data and simply use the development instance for load tests and such. With that said, if we agree on where the data should be migrated to then we'll be able to complete the migration after #56 is resolved

LecCory commented 1 year ago

Infra has been deployed to seankibbee tenant. #56

Because there's no data, the site is currently non responsive. We can work on copying over the data.

LecCory commented 1 year ago

Cleaned up the *_old tables by importing the data into a temp server and exporting a clean backup. Re-running the import into cypher. Should be complete before EoD

LecCory commented 1 year ago

Import completed.