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

Implement backup sequence #57

Closed
lewismc opened this issue Jan 25, 2019 · 4 comments
Closed

Implement backup sequence #57

lewismc opened this issue Jan 25, 2019 · 4 comments
Assignees
Labels

Comments

@lewismc
Copy link
Member

lewismc commented Jan 25, 2019

It is essential that any data stored in the system is backed up.
@carueda are there any other data sources we need to back up other than Mongo and AGraph?

@lewismc lewismc added help wanted ops operations labels Jan 25, 2019
@lewismc lewismc self-assigned this Jan 25, 2019
@carueda
Copy link
Member

carueda commented Jan 25, 2019

/home/cor-admin1/COR/ is the critical location (in particular the subdirs orr_data/ and mongo_data/ there). AGraph data is not critical at all as the triple store can be repopulated at any time from the actual registered ontologies (there's an admin operation for that in the UI).

@lewismc
Copy link
Member Author

lewismc commented Jan 25, 2019

@abburgess OK can you please check that /home/cor-admin1/COR/ is backed-up? If it is, then please post the location of the backup here and we can close this issue. Thank you

@esip-lab
Copy link
Member

screen shot 2019-01-25 at 11 15 51 am

The backup is of the EBS volume holding the EC2 COR instance on AWS. That will include COR.

@lewismc
Copy link
Member Author

lewismc commented Jan 28, 2019

Thanks folks,

@lewismc lewismc closed this as completed Jan 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants