Hi It's possible to backup everything using the API with several queries.
Mathieu Le 13 juin 2015 22:31, "Arie" <[email protected]> a écrit : > Hi Chuck, > > Did you copy the node-id file to the new server? Some things in the > configuration are > related to that. I am curious what the effect of that would be. > > Arie. > > ps > To the guys at Graylog,, > > Maybe an idea to use or extend the export function so that it can be used > as a backup/restore > system for complete configurations. > > > > Op zaterdag 13 juni 2015 20:29:05 UTC+2 schreef Chuck Musser: >> >> I use the functionality of importing and exporting contend-packs for this >>> kind of functionality. >>> I use that for making backup of my configs to. >>> >>> Arie, >> >> That might get us part of the way there, but I was looking for a solution >> that completely transferred information from an existing Graylog server to >> a new one. My first attempt was a low-level copy of the MongoDB (in the >> hopes that would get everything) but that hasn't worked yet. Maybe another >> approach would be to set up a new Graylog server as a non-master in the >> same cluster and then somehow "promote" it to master. Not sure if the >> system works that way, though. So, still looking for tips on how others >> have migrated from a test all-in-one setup to a production one, on >> different (and separate hardware). >> >> Chuck >> > -- > You received this message because you are subscribed to the Google Groups > "graylog2" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "graylog2" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
