there may be others, but in particular, i'm thinking of the data stores behind our datashare instance and our linkurious instance.
for linkurious, that'd be our neo4j database.
for datashare, that'd be its postgres instance, its internal elastic search instance, maybe other stuff?
this will likely spawn one or more ops tasks tickets when it gets picked up, but this ticket can go on the KSR project board for better visibility across the KSR team.
datashare was being backed up, but has been decommissioned. linkurious backups are working (we've successfully loaded them into local neo4j instances for exploration, for example).
there may be others, but in particular, i'm thinking of the data stores behind our datashare instance and our linkurious instance.
for linkurious, that'd be our neo4j database.
for datashare, that'd be its postgres instance, its internal elastic search instance, maybe other stuff?
this will likely spawn one or more ops tasks tickets when it gets picked up, but this ticket can go on the KSR project board for better visibility across the KSR team.