Skip to main content
P
Paitoon1-Visitor
1-Visitor
May 31, 2021
Solved

Can I put one stream data into two persistence provider as replica?

  • May 31, 2021
  • 2 replies
  • 1050 views

Can I put one stream data into two persistence provider as replica?

i would like to stream data into two persistence data storage (one for master, one for backup or testing)

Can I ?

Best answer by mnarang

If you create a new Stream then it will be associated with one persistence provider only. So ideally you will be able to insert data into one DB. Alternatively, if you want stream data replication into another DB, you can consider another approach like maybe using a scheduler that runs every day and picks up everyday data from your main Stream(DB) and then put it into another DB(using DB thing). Or else if you have another ThingWorx test server where you want to bring this Stream then you can use ThingWorx Data export/import functionality to have another replication in a separate server. One more way could be to have this procedure (to replicate the data into another schema/DB) in DB itself and you can trigger that from DB thing. There can be different approaches according to the use case.

2 replies

M
mnarang5-Regular MemberAnswer
5-Regular Member
May 31, 2021

If you create a new Stream then it will be associated with one persistence provider only. So ideally you will be able to insert data into one DB. Alternatively, if you want stream data replication into another DB, you can consider another approach like maybe using a scheduler that runs every day and picks up everyday data from your main Stream(DB) and then put it into another DB(using DB thing). Or else if you have another ThingWorx test server where you want to bring this Stream then you can use ThingWorx Data export/import functionality to have another replication in a separate server. One more way could be to have this procedure (to replicate the data into another schema/DB) in DB itself and you can trigger that from DB thing. There can be different approaches according to the use case.

D
DmitryTsarev17-Peridot
17-Peridot
May 31, 2021

Just my 2 cents to add to @mnarang 's answer.

 

For making a copy of the stream for the testing purposes and for the purposes of backup in terms of recovering after an accidental / caused by malware change or deletion of the data in the production server, the approach @mnarang suggests fits great.

 

If you need a backup /replica to increase the system availability (i.e. for the case when the server with Thingworx malfunctions), you'd need to configure Thingworx and / or the database you're using to work in a High Availability environment.

Terms & ConditionsAccessibility statement