The replicator with 3.0 and on works significantly different than before. The biggest change is that it works only for onePOS software and does so in a pre-defined manner. You can no longer mirror a g: drive, have it run at 4am, etc...
The replicator software is now built into the onePOS Server Service. It will send modified files over to TTL02's onePOS Server Service (that normally just idles waiting for a system failure) from TTL01. The directories that are monitored are Data, Exes, Images, Images-Dining, Images-ScrSaver, Journals, Tabs, and Batches. Subdirectories are not included in the replication.
The changes are "scrubbed" at the start of every hour or 15 minutes after TTL01 comes up... the files on TTL01 are physically compared to those on TTL02 via a checksum or size, and if different they are copied over. During normal operation, files that are changed on TTL01 are synchronized almost real time to TTL02... with the caveat that you are not making changes through File Sharing. If you are making changes through File Sharing, the replication will be done every 15 minutes.
We are continuing to use the StopRepl.txt flag on TTL02 to indicate that redundancy is active, however it has moved to the \onePOS folder from the root of G:.
In order for the onePOS Server to launch the Payment Server, Replicator Server, Monitor Server, or Data Server the value IsPOSServer in HKEY_LOCAL_MACHINE-Software-onePOS must be set to 1. If you just run the onePOSServer.exe application it will idle as if it is TTL02 without that registry key set.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment