Either of those options work, and its up to you to decide whether or not keeping your different database environments in-sync is worth the effort. As for backing up between Prod and Test, yes you absolutely can. All you need is a shared file system that both environments have access to where you can put the backup in the interim. Depending on what version of Elasticsearch your running setting up the connection to the SFS will either require more work or less, the most recent version of ELS having by far the simplest method to connect. Personally I use s3 to back up my critical Elasticsearch indices daily. For other indices I have backups on sql server. So it really depends, but I would think if you had a UAT environment as well with a current set of the data then you should be able to keep the product table just on Elasticsearch. Good luck, and option 2 is just as reliable/redundant as your database/system architecture. I like the idea of having the data on two places in ELS to enable blue-green deployment if anything happens to your production ELS cluster. @Hooman_Bahreini
1 Like