Re: Replicating Store DB

Thnks Karsten, for the quick response.
The automatic replication sounds promising however 'keeping an eye' will be
a difficult thing to do for us.

Since the repository is handling tens of thousands of classes, the time
taken for replication at store level may get unpredictable.
So the actual time to get a publish updated on a replica db , might make
the replica unreliable.
Can we do a replica at 'My_SQL' level, and get the publishes reflect both
main db and replicas at the same time ?

Thanks and Regards,
Mani

On Tue, Jun 6, 2023 at 10:05 AM Karsten Kusche <[email protected]> wrote:

> Hi Mani,
>
>
>
> There’s StoreForGlorpReplication and StoreForGlorpReplicationUI. If you
> just want to replicate something manually, you’ll use the app provided in
> the Store menu if you want replication to be done automatically you’ll use
> auto replication.
>
> Once the both packages are loaded, you can go to the VisualWorks Settings
> and under Store you’ll find “Replication” and “Auto Replication”. You need
> to have at least two Store profiles saved (source and target). You can then
> use these profiles in the auto-replication settings by defining rules like:
>
> B,%,source,target
>
> P,%,source,target
>
> Typically you’d only need these two rules as it’ll just replicate
> everything.
>
> You can then activate auto replication from the launcher’s Store menu.
> It’ll take some time, even if both repositories are in sync to test all
> pundles and versions and their blessing levels. We’ve configured our
> replicators to run every 15 minutes, but I can’t tell how long each runs.
> As we’ve got multiple Store Databases, we have multiple replicator images
> running to keep them all in sync.
>
> You may need to have these images running on a computer with display and
> someone needs to keep an eye on the images as occasionally something goes
> wrong and a debugger halts an image. Closing the debugger is usually the
> easiest fix, but in rare cases someone needs to take a closer look.
>
>
>
> Kind Regards
>
> Karsten
>
>
>
> [image: cid:[email protected]] <https://urldefense.com/v3/__https://www.heeg.de/__;!!DZ3fjg!-nkgYbIISl-ZoMzvB9vLJZ9srE6bjD8bY001t7zZ3QQHUQj4-CEvats3sTTGp585v6fuiFZ3kLSbRlGbrWARHRClZj3-$ >
>
> Georg Heeg eK | Amtsgericht Dortmund HR A 12812
> Wallstr. 22 | D-06366 Köthen
> Tel.: +49-3496-214328
> Web: https://urldefense.com/v3/__http://www.heeg.de__;!!DZ3fjg!-nkgYbIISl-ZoMzvB9vLJZ9srE6bjD8bY001t7zZ3QQHUQj4-CEvats3sTTGp585v6fuiFZ3kLSbRlGbrWARHYZK0sOF$ 
>
>
>
>
>
> *Von:* [email protected] <
> [email protected]> *Im Auftrag von *mani kartha
> *Gesendet:* Dienstag, 6. Juni 2023 06:18
> *An:* [email protected]
> *Betreff:* [vwnc] Replicating Store DB
>
>
>
> We are facing large latency issues when connecting to a remote Store [vw
> 7.4].
>
> Can we replicate a Store DB (My_SQL) ? How difficult is it  to manage it?
> What are the challenges involved (technical/administration
> level)considering more than 100 users from multiple geographic locations?
>
> Can we ensure that the published versions  are sync-ed without delay in
> all replicas?
>
> The sync-ing is the responsibility of the DB admin or Store will handle it
> ?
>
> Limiting replicas for read operation only, will it have any advantages in
> managing ?
>
> Technologies like 'ExpressRoute' can be used to setup a store connection
> with less latency ?
>
>
>
> Thanks in advance for your comments and suggestions.
>
>
>
> Mani
>
>
>