Discussion:
[influxdb] Regenerating meta.db
r***@gmail.com
2016-03-30 20:18:25 UTC
Permalink
We've recently upgraded our 0.10.3 single node to 0.11.0 and followed the directions for upgrading to tsm1 shards. In the process we erroneously removed the existing meta directory. We replaced the meta directory from a snapshot that was a few weeks old and have "lost" all the data inbetween. I am thinking that the data is still on disk but the meta.db has no idea how or where to locate thed data??? If that is the case, is there anyway to rebuild/regenerate a fresh meta.db from the data that is available on disk? Thanks.

- Rob
--
Remember to include the InfluxDB version number with all issue reports
---
You received this message because you are subscribed to the Google Groups "InfluxDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email to influxdb+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/influxdb.
To view this discussion on the web visit https://groups.google.com/d/msgid/influxdb/3944ecd6-4c77-489e-9b6b-47554ec49def%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
r***@gmail.com
2016-04-01 03:20:04 UTC
Permalink
Post by r***@gmail.com
We've recently upgraded our 0.10.3 single node to 0.11.0 and followed the directions for upgrading to tsm1 shards. In the process we erroneously removed the existing meta directory. We replaced the meta directory from a snapshot that was a few weeks old and have "lost" all the data inbetween. I am thinking that the data is still on disk but the meta.db has no idea how or where to locate thed data??? If that is the case, is there anyway to rebuild/regenerate a fresh meta.db from the data that is available on disk? Thanks.
- Rob
Ill take anything suggestions.. even if i have to manually map a couple dozen shards
--
Remember to include the InfluxDB version number with all issue reports
---
You received this message because you are subscribed to the Google Groups "InfluxDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email to influxdb+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/influxdb.
To view this discussion on the web visit https://groups.google.com/d/msgid/influxdb/3926eaf5-fc25-408e-8126-37a8c3081f11%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
r***@gmail.com
2016-04-01 03:20:38 UTC
Permalink
I'll take any suggestions.. even if that means manually mapping the shards
--
Remember to include the InfluxDB version number with all issue reports
---
You received this message because you are subscribed to the Google Groups "InfluxDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email to influxdb+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/influxdb.
To view this discussion on the web visit https://groups.google.com/d/msgid/influxdb/db060358-68a7-4389-a1ba-12af91ba5b8c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
r***@gmail.com
2016-04-04 19:29:22 UTC
Permalink
Sean,

If there is a way to do it via the source I am happy doing it that way. Just point me in the right direction. No hand-holding tools required.

- Rob
Rob,
With the current architecture, if the metastore is gone there is no way to rebuild the database. It might be possible to export it from the files and re-import. I don't know if we have a tool that can read the shards and dump out line protocol or some other format. I'll ask.
I'll take any suggestions.. even if that means manually mapping the shards
--
Remember to include the InfluxDB version number with all issue reports
---
You received this message because you are subscribed to the Google Groups "InfluxDB" group.
Visit this group at https://groups.google.com/group/influxdb.
To view this discussion on the web visit https://groups.google.com/d/msgid/influxdb/db060358-68a7-4389-a1ba-12af91ba5b8c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Sean Beckett
Director of Support and Professional Services
InfluxDB
--
Remember to include the InfluxDB version number with all issue reports
---
You received this message because you are subscribed to the Google Groups "InfluxDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email to influxdb+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/influxdb.
To view this discussion on the web visit https://groups.google.com/d/msgid/influxdb/f0fe9476-d641-4db1-af4e-787bd635a726%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
b***@gmail.com
2017-08-11 12:26:24 UTC
Permalink
Command for exporting data from influxdb tsm file is

$influx_inspect export -database dbname -datadir path -waldir path -out exportfile

For importing back to influxdb

$influx -import -path=exportfile
--
Remember to include the version number!
---
You received this message because you are subscribed to the Google Groups "InfluxData" group.
To unsubscribe from this group and stop receiving emails from it, send an email to influxdb+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/influxdb.
To view this discussion on the web visit https://groups.google.com/d/msgid/influxdb/7f9af956-7e91-4e9b-833c-e612e26f6cab%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Loading...