Personally, it sounds like you’re overengineering your setup. If it’s to learn then have fun! However, if its ‘prod’ and you care about the data then you should stick to prod tested architecture. You won’t find many people (if any at all) using inode notify to rsync a database on change.

So, AI?

I think the inode rsync is a bad idea. The 2nd DB would be on the NAS but its not being used by the app, so as long as it’s asynchronous writes, you should be okay.

In either case, I hope you have backups, not just the copy

I know it has been 3 days since you posted buy why not set up replication in the database it self? Sounds like you’re over complicating replication.

I run in k8s but I have a database with local disk, and I have another cronjob that takes a backup into the first database docker init folder. Older backups end with -date so they won’t get picked up by the init script. You can do similar with just docker.

I’ll echo everyone else. Database need local disk. I speak from experience of doing it over NFS. Even containers that have a hidden sqlite3 database should get local disk.