graphite-dev team mailing list archive
-
graphite-dev team
-
Mailing list archive
-
Message #02967
Re: [Question #203668]: Backing up Whisper files: Best Practices
Question #203668 on Graphite changed:
https://answers.launchpad.net/graphite/+question/203668
Francois Mikus proposed the following answer:
The way I see it you have two ways to do it:
Full copy, nicing the process and disk-access using rsync.
Or :
Have two servers with raids, and simply send your metrics to both servers.
Have a script that periodically(or after an outage) goes through the list of metrics
The script does two things:
1 - On server A checks if the file exists on server B and does an rsync if missing
2 - if not run a whisper-merge to fill in ay missing values from A to B
3 - Do some type of QA and remove the backup file (or edit whisper-merge to not do a backup).
This backs up from A to B.
You can also do the same from B to A, but you have to really trust
whisper-merge...
This is simple, and covers most a large number of use cases.
Synchronisation is time delayed, but you have redundancy. Graphite
sprays requests to both sets of databases.
If anyone else has suggestions, I am also interested in earing the
answer.
--
You received this question notification because you are a member of
graphite-dev, which is an answer contact for Graphite.