Nifi Registry Backup and deployment

[#1]

Hello everyone. I am looking to get advice on deploying and maintaining the registry client. I like how I can switch between versions and let NiFi work its magic under the hood to manage that switch.

I understand that the registry client acts as version control for the flows but how do you go about backing up the versioned files? I am using docker with kubernetes to deploy nifi and the registry client. There could be a situation where the registry client nodes fails and looses data. Should I also be storing the versioned flows on github and packaging it in a docker build?

If anyone has a good flow on deploying and maintaining the nifi registry so I can ensure I won't loose the flows

[#2]

https://community.hortonworks.com/articles/177301/big-data-devops-apache-nifi-flow-versioning-and-au... this will show you how

[#3]

Hi @Chris Dan

Please keep in mind that Flow Registry is the beginning of FDLC in NiFi and an important building block on which several services will come.

If you want to export a flow from the registry to backup it somewhere you can either use:

• NiFi Toolkit: part of NiFi project. https://issues.apache.org/jira/browse/NIFI-4839
• Nipyapi: a community feature. As Tim suggested, you case this tool also and follow his excellent article.

Today, the flow registry has a file storage provider. Flow registry supports plugins and new storage providers such as Git will follow in my opinion.

Thanks

[#4]

Hello,

Anyone have an idea about nifi registry databases, how to backup that database ?

you can locate that database by the "nifi.registry.db.directory" proporities