Best approach to backup data from an on-premise application to cloud
Hey all, We've currently got 2 types of apps running for a customer. One app that's in the cloud which stores master data and retrieves analytical and operational data from the second app. This second app is running on-premise on multiple plants. Each of these plants use some parts of the master data and also have their own operational data and personal (default) settings. The master data app in the cloud is using the a regular backup method. For the ones in the plants (on-premise) this is not an option. We would like to make an event that makes a backup of all operational data of all of these plants every day, and uploads this to the central master data app. After backing up this data, it should then be possible (in case of a loss of data) for another service to then retrieve this data from the central app and re-install it into the on-premise on that's lost it's data. The re-installment of this data would then not only include the data itself, but also all of the associations these records once had. In order to make this happen, we thought it would be nice to have one table that records all GUID's of the owner and the child of all relationships . This way, we can use these GUID codes to re-install them when we get all the data back into the o-premise database. However, we've never done something like this before and would really appreciate some thoughts or even perhaps some examples from people who've already faced a certain case before. All questions and/or feedback would be great! Thanks in advance.
If I where to build this I would create webservices that syncs the relevant data into shadow tables on both sides. This way you can control the proces of (re) creating the data on both sides.
You need to be aware of a couple of things. Do note that you never can recreate autonumber fields again. So never use those type of fields even though this would be handy to uniquely identify objects. I have my doubts about GUID because I am not sure but do wonder if you could recrate those.if for some reason they do not exist anymore. I have my doubts there but a small test would give you the answer. I would just create unique ID's for the referenced objects so that the webservice when doing the import and sync can use those to set the references.