Replication Verification Improvements in iCluster 7.1 TR1
Rocket iCluster 7.1 TR1 is now available for all customers on the Rocket Customer Portal. TR1 has enhancements based around four key areas – ease of administration, replication verification, error handling and currency. In this post, the Replication Verification Enhancements are highlighted.
Replication Verification addresses sync check and how iCluster can ensure that the data is identical on both primary and backup nodes.
- One question that always gets asked is how do I know if my group is ready for a switchover? Now you can easily have this answered either online or through a batch CL variable using the DMSWTCHRDY command (formerly ICTOOLS ICSWORDY). If the group has no suspended objects, no latency exceeding user defined thresholds, no OOS objects and no open commit cycles – it’s ready!
- How many times have you thought, switching the product is easy but it’s all the other stuff that you need to do as part of a switch that causes confusion like ending the application subsystems, varying off the primary IP interface etc. Now there is a full switch wizard that handles this for you (formerly ICSWITCH in ICTOOLS) so you have a switch so simple, even the CEO could do it!
- If you never test your switch, how do you know that everything that your application needs to run on the backup is being replicated? You can now use the Roleswitch Simulator (formerly ICTOOLS ICVRSWAP) to test your switch any time of the day including updating files and objects on the backup node, and have all of those changes rolled back after the test.
- We have also modified the sync check to alert you of any orphaned or obsolete objects (objects that exist on the backup but not on the primary) and to automatically repair any journal mismatches (files that are journaled to a different journal on the backup than on the primary.
[box type=”info”]Learn more about iCluster’s replication capabilities[/box]