Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create and Manage Plan to Restore Lost EarthCODE Data #55

Open
GarinSmith opened this issue Jan 7, 2025 · 2 comments
Open

Create and Manage Plan to Restore Lost EarthCODE Data #55

GarinSmith opened this issue Jan 7, 2025 · 2 comments
Assignees

Comments

@GarinSmith
Copy link

GarinSmith commented Jan 7, 2025

EarthCODE Data Restore Plan

Data (S3 Object Store) - Ewelina to Lead
Assets and Catalogs

  1. What is backed up?
    This is stored in Local drive, VM, External sources. We are hopeful we have most of the lost data.
  2. What is the priority?
    Probably references from any external sources
  3. What is not backed up?
    We will confirm this as part of 1)

MetaData - Garin to Lead
GitHub/EarthCODE Catalogue

  1. Confirm no metadata is lost and we can re-use this?
    This is currently no reason to suspect this is an issue.
  2. This does assume that we use the same data location at CloudFerro?
    We have asked CloudFerro if they can provide the same S3 instance location.

Scripts/Process - Ewelina to Lead

  1. Do we have scripts to move data to S3 or is this done manually?
    Yes, we have scripts with some manual effort
  2. Confirm that we can just move data again without changing the existing metadata?
    Yes we think so if CloudFerro can help above.
  3. Assume that PPR script will be used later?
    Yes, we have suggested some PPR scenarios to support this.

Environment - Garin to Lead

  1. Can we use CloudFerro?
    Assumes yes subject to clarification of operational procedures.
  2. Can we use PRR?
    Yes in parallel to S3. We have more info from Salvatore.
    One possible bonus is that we can deploy the above products to PRR when the new script is ready.
  3. CloudFerro alternate S3.
    Not currently planned unless there are problems with 1)

Operational Stability - Garin to Lead

  1. Review/Confirm CloudFerro Operational Procedures
    See Meta Data point 2)
  2. ESA PRR
    When is PRR prototype app package available?
    When is PRR production environment available?
    What is the PRR SLA?
@GarinSmith
Copy link
Author

Hi @edobrowolska,
I assigned this task to both of us, because it seemed easier and more flexible.
I used the core plan we worked on together earlier and I suggested the tasks that we each lead on.
I will arrange a catch-up on Thursday.

@edobrowolska
Copy link

I created a simple excel file with the datasets to be resotred (attached here). Column F indicates the priority of the data to be restored. In two cases we are missing backup for the data itself - I will contact data providers to update us on the access to that assets. In the next step the catalog.json collection files will need to be restored-re-created. This will be next step on me to be checked. Missing-data-list.xlsx

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants