New U2 Replication Scripts for Microsoft Windows

Starting at 1.6.3 on Microsoft Windows the console program has been dropped and rewritten completely in Windows Power Shell

U2 Replication is a very powerful, very configurable but very complex part of both UniData and UniVerse.

Many customers have historically become very adept at deploying there U2 Applications into environments where the people responsible for those environments have little or no specific U2 Administration knowledge. This has been one of the many positives of deploying U2 over a long period time and wed like that to continue.

To administer and maintain U2 Replication, specific U2 Administration skills and knowledge need to be acquired. The Replication Exception Script and Monitoring Phantoms are designed to reduce this requirement. These Scripts and Phantoms have been discussed in a three-part blog series around Replication Best Practices and webinar. They are designed to act as proactive notifications of any problems, which may have otherwise gone unnoticed and then become a larger problem. The use of an Exception Script when correctly designed can be used to automatically re-establish Replication after events such as network interruptions.

The Scripts and Phantoms are distributed and updated with each point release of UniVerse (12.1 onwards) and UniData (8.2.1 onwards).

Prior to version 1.6.3 the Windows exception handling was done via a .NET console-based executable rather than a script (shell script) as in the UNIX version. Starting at 1.6.3 on Windows the console program has been dropped and rewritten completely in Windows Power Shell. This will give Windows users the same flexibility offered to UNIX users in terms of being able to fully examine and modify the scripts easily if required.

The Replication Exception Script and Monitoring Phantoms are documented in detail in the Rocket knowledge base under an article entitled 'U2 Replication Exception Script and Monitoring Phantoms' in a pdf attached to the article.