This message was deleted.
# troubleshooting
s
This message was deleted.
d
If you have backups on your metadata storage, just restore from backup.
b
No backups available.
b
No good way, it's important to have backups or HA for metadata DB so it's not a single point of failure. There was a deprecated tool, but it's deprecated because it's not 100% reliable. And it won't work at all after 0.15, iiuc.
d
is this on AWS RDS? You may be able to restore using AWS tools.
g
It may be possible (albeit difficult) to recover even if you're missing a metadata store backup. The segments on deep storage have all the data but you have a couple of issues if you're missing the metadata store: • You can't easily tell if some segments were marked unused (manually or by drop rules). However, you can tell what's the newest version for each time chunk, and just load all of them. • The descriptors (
payload
in metadata store) are missing, so you'd need to generate those and re-insert them into a new metadata store. You may be able to find enough info based on the directory structure in deep storage. The interval, version, datasource should be embedded in there. You may need to set additional fields based on your knowledge of what's supposed to be there
I hope you can find a backup, but if not, the I hope the above clues are helpful!