Tom, I suspect some others might add some additional info here but to achieve the back-up of the configuration such that you could quickly restore you'd generally just need to save the conf directory content. The flow configuration should port well to another node including the sensitive property key. You would need to change things like hostnames in the properties files if you move to another box. If you simply are going to restore the configuration on the same box that had the issue you can restore the conf directory and just delete the various repository directories.
As a general rule you can safely get rid of the archive folders any time because those are just holding items which are no longer actively reachable in the flow but we keep around so you can click-to-content from provenance data or initiate replay. Thanks Joe On Mon, Jun 6, 2016 at 10:45 PM, Tom Stewart <stewartthom...@yahoo.com> wrote: > I am curious as to what others are using to automate backups of the NiFi > flow? Specifically,I am looking for steps on what file(s) to copy out of the > NiFi cluster such that I can rebuild/restore if necessary. > > In NiFi 0.61 (cluster), I set this: > nifi.properties:nifi.flow.configuration.archive.dir=/opt/nifi/archive/ > nifi.properties:nifi.content.repository.archive.max.retention.period=12 > hours > nifi.properties:nifi.content.repository.archive.max.usage.percentage=50% > nifi.properties:nifi.content.repository.archive.enabled=true > > When I go into NiFi Flow Settings and use Back-Up Flow, it writes to > /opt/nifi/archive on the cluster nodes (not the NCM). Is there any way to > automate this on a periodic basis? Wondering if anyone has constructed, for > example, a NiFi flow to back itself up that could create this file and > subsequently copy it off the Nifi cluster to another system (like Hadoop, > S3, or some random backup server). Also curious on recommendation if I can > drive any of that from automation on the NCM. If we just grab the active > flow.tar file from the NCM, is that a sufficient point in time backup? > > I also don't really see anything in the documentation regarding restore > procedures. At a minimum, even if we lose in-flight data we'd like to be > able to quickly rebuild and restore the basic flow configuration of a NiFi > cluster. I think I know we'd maybe need to re-enter some of the sensitive > data value fields. But I am looking for how and where to put the flow.tar or > flow.xml.gz file when restoring a cluster. > > Thanks, > Tom > > > > > >
