On Monday, September 12, 2016 at 8:53:47 PM UTC+2, Sean Beckett wrote:
> Backups are documented here:
> http://docs.influxdata.com/influxdb/v1.0/administration/backup_and_restore/
>
>
> They are always full backups, so there's nothing more complex to the backup
> strategy than what you describe. Backups can be run against a live instance.
>
>
> > Also what stops me from doing rsync on the directories used by InfluxDB?
>
>
> Race conditions. Memory and files are changing all the time. Rsync doesn't
> grab a cohesive snapshot of the full directory, it merely grabs the latest
> version of each file serially. There is very little chance that grabbing
> files serially will produce a consistent backup unless the cluster is under
> extremely low load. Even then, I think it's unlikely restoring an rsync'd
> copy would work more than half the time.
>
>
> On Mon, Sep 12, 2016 at 12:41 PM, <[email protected]> wrote:
> Hey, I am interested using InfluxDB in production but cant afford the
> Enterprise/Cloud products.
>
>
>
> So I am interested in ways to ensure I wont lose data when going live.
>
>
>
> What are you doing regarding backups? Care to share your scripts?
>
>
>
>
>
> Is it as basic as this?
>
>
>
> S1: influxd backup /path/to/metadata
>
> S1: influxd backup -database mydatabase /path/to/backup
>
> S2: influxd restore /tmp/backup
>
> S2: influxd restore -database mydatabase /tmp/backup
>
>
>
>
>
> Also what stops me from doing rsync on the directories used by InfluxDB? I
> could keep a second server in sync (without the process running) and if
> something happens to master I could simply do "service start influxdb" on the
> second server to get up and running without doing any backup restores.
>
>
>
> Thanks
>
>
>
> --
>
> 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 [email protected].
>
> To post to this group, send email to [email protected].
>
> 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/f4e45893-3a7a-4a19-85ff-26096a9ed706%40googlegroups.com.
>
> For more options, visit https://groups.google.com/d/optout.
>
>
>
>
>
> --
>
>
> Sean Beckett
> Director of Support and Professional Services
> InfluxDB
Hey Sean, thanks for the answer.
I know about the backup docs but they are not clear enough for me. I come from
MySQL backups so its a bit confusing for me.
Scenario: My dedicated server burns down, I only have backups and I am planning
to restore them on a new server.
1. Does metastore backup continues queries as well? Or I will need to
re-create them?
2. Lets say it took me 1 hour to setup the new server. After restoring I
insert all the missing data for the 1 hour the DB was down. Will CQ process the
data correctly since its technically from the past?
3. In the above scenario do I need to do anything else to get a new server
with 1:1 data as the old one except from the commands below?
S1: influxd backup /path/to/metadata
S1: influxd backup -database mydatabase /path/to/backup
S2: influxd restore /tmp/backup
S2: influxd restore -database mydatabase /tmp/backup
Thanks
--
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 [email protected].
To post to this group, send email to [email protected].
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/7d7be83e-4b99-4e48-b561-bae1e764eb36%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
