The most important to keep is the data in the database. As for the OpenMRS platform war file and metadatasharing module with its dependent modules, we can easily re-download them.
1 Like
I had an issue with my system on Friday, but Iām back up and picking this up today.
Iāll try this out, but not sure exactly how it is supposed to work. Remember that I am not a developerā¦just a superuser and some of this goes beyond my natural expertise 
@akanter, thereās no need for you to experiment on that. Iāll follow up with you on how to do it later next week. Iāve actually worked around that issue by importing the latest CIEL before upgrading to platform 2.0.x so it is not blocking the release of Reference Applicaiton 2.5.
@taremwatadeo, Iām working on getting the concepts included in Ref App right now. Once Iām done with that Iāll let you know so you can proceed with the release.
Thanks, but I now canāt build the next release for the old versionsā¦ Need to fix that ASAP.
@taremwatadeo, Iāve updated concepts in referencemetadata to the latest CIEL and released the referencemetadata module. You can proceed with RA 2.5 release.
1 Like
Per this post: Clarification regarding update Metadata Sharing packages to the latest versions of CIEL concepts
ā¦ it looks like the MDS packages may have been lost again on this server?
@mogoodrich , it seems like this is indeed the case.
Since I have ssh access to this server, if anyone ( @cintiadr maybe?) could point me to the instructions on restoring the packages, I can go ahead and do the needful(especially since I am currently blocked due to this and we are already out of time with reference to the Ref App release)
Not that I have any idea what is those packages you are talking about, or how they are included.
That said, you shouldnāt run anything other than SQL imports on that machine. It will be lost and rebuilt.
If you give me the instructions (when you find it), send me the link so we can make sure thatās not lost when I restart the containers, run ansible or recreate the machine.
Iām not 100% up to speed on what is happening here, so Iām hesitant to weigh in, but Iāll tryā¦
The MDS packages are bundled groups of concept and other OpenMRS metadata created by the Metadata Sharing module.
These would be stored in the metadatasharing_exported_package table in the OpenMRS database.
From reading earlier in the thread I believe mdsbuilder is meant to be āplace of truthā where we store these packages, which are then bundled with the reference application.
Not sure how the mdsbuilder server is managed, or if this was ever properly documented/conveyed to the infrastructure team, but because of this, when we recreate the machine itās important to not lose the existing database. Not sure if this is what happened?
Take care, Mark
Donāt blame you for not knowing @cintiadr and @mogoodrich . This server is like a black box and I havenāt found much documentation about it on wiki either. I just know that the current output is not what is expected but I have no clue on how to fix it.
I know a lot more about the server (not really the OpenMRS service).
So, here you can find the docker compose and its initial database. You can see the only things we are keeping as ādataā/volumes are the database folder and .OpenMRS folder. There are backups for those folders.
I documented this image in wiki
The ticket that did the migration to the new server is ITSM-4054.
I donāt really understand what was migrated (database-wise), because I donāt really understand how the service is being used at all.
Iāve moved all packages to the new mdsbuilder server when migrating the serverā¦ I even recall us creating packages for a Reference Application release from that server a few months back. I donāt know when/how those packages were deleted. We should have backups of the database taken daily so itās a matter of tracking down, which one to recover. I can look into that before the end of this week.
Unfortunately the oldest backup we have from May 31, 2018 does not contain any packagesā¦ We must have lost packages prior to that.
The one way to recover I can think of right now is import RefApp metadata from the latest release of Reference Metadata module into mdsbuilderā¦ I can try to do that tomorrow. @burke or @dkayiwa could you please create an account for me on https://mdsbuilder.openmrs.org/openmrs/ ? I donāt have one anymore.
Itās the second time we lost data on mdsbuilder. This time backups didnāt help as it was spotted too late (we keep backups only for a certain amount of time). It would be good to have some checks in place to discover such a loss earlier. At least we should keep a backup taken with the last release of RA and not expire it.
1 Like
Meet me on skype, Rafal. Happy to set up a user account for you.
Thatās unfortunate. Nonetheless, I have messaged you with the admin details which I got from @cintiadr for the server.
If you add to the manual backups S3 bucket, itās not going to be deleted.
But I domino understand how that happened.