Discuss the ways you are managing system interruptions, recovering from outages, or scaling for increasing transactional volumes with Rocket iCluster. Share your tips & tricks, stay up to date on the latest announcements and engage with other iCluster users.

Rocket iCluster provides high-availability/disaster recovery (HA/DR) solutions help ensure uninterrupted operation for your IBM i applications, offering continuous access by monitoring, identifying and self-correcting replication problems.
To learn more about how to limit downtimes and maximize IBM i application and data availability, visit the iCluster home page.

#iCluster #IBMi​​

Latest Discussion Posts

  • Posted in: Rocket iCluster

    In this post we are going to discuss ways to both increase the fidelity of your HA/DR deployment and reduce the administrative overhead required to maintain that reliable state. There are two primary modes to run sync checks in iCluster and the two can ...

  • Posted in: Rocket iCluster

    It is critically important to conduct periodic failover planning and testing, and execute node switching as part of your DevOps practices. There's a lot of risk associated with not doing both, whether it comes in the form of lost revenue, clients or employee ...

  • Posted in: Rocket iCluster

    Once iCluster nodes are configured using a specific IP address, they will continue to use this IP address, however what if your network changes? How do you change the IP address used by iCluster? Luckily there is a TechNote on how to perform this procedure: ...

  • Posted in: Rocket iCluster

    Instead of the steps required to get into iCluster: CHGCURLIB ICLUSTER GO DMCLUSTER You can create a simple CL (QCLSRC) named IC with the two commands: and a simple 1-line CMD (QCMDSRC) named IC with just the command prompt and no parameters: ...

  • Posted in: Rocket iCluster

    Before we discuss the command, let's discuss what an 'out of sync' (OOS) condition is. An OOS is the result of a Synchronization Check run that resulted in a list of exceptions. A Synchronization Check (SC) is a special process that compares attributes ...

    1 person recommends this.
  • Posted in: Rocket iCluster

    If you are having communications issues, you can see some of the internal communication messages that are generated by iCluster behind the scenes to assist in problem resolution. Just create a new message queue on the node that appears to be having the ...

  • Posted in: Rocket iCluster

    There are a variety of factors that can crop up and cripple IT environments. However, many issues, such as a lack of testing, deployment, or on-prem primary source replication or protection, can be avoided with a shift in you disaster recovery and high ...

  • Posted in: Rocket iCluster

    Rocket iCluster includes a configuration 'fast start' command to perform some of the configuration steps based on a typical installation. This command, DMAUTOCFG, can assist in defining a node pair, some replication groups, selections of objects for ...

    1 person recommends this.


  • Now available | iCluster version 8.3

    We're excited to announce that iCluster 8.3 is now available to customers on the Rocket Customer Portal.

    Highlights of this release include:

    Replication enhancements
    • Faster synchronization of source physical files (PF-SRC) by using a record-by-record refreshing method.
    • Support for replication of logical files such as SQL views that are not based on physical files.
    • No numerical limit on Byte Stream File (BSF) specifiers; a longer maximum path name extension to support more types of BSF objects.

    Sync Check enhancements
    New options:
    • A user sync check can now be initiated for a specific file from the backup monitor.
    • Ability to run sync checks sequentially when starting a sync check for a group.
    • New auto-repair options for database files and native objects.
    New detection features:
    • Files with journals that are not being scraped will be reported with reason code JNS.
    • Files that are not journaled will be suspended with reason code EJF.
    • Missing replication information for journaled objects will be reported with reason code RIM.
    • Improved performance when activating out-of-sync objects and byte stream files.

    Status Monitor
    • The collection of performance data for all replication groups has been optimized.
    • E-mail alerts now include the system name in the title.

    Other Changes
    • iCluster has new defaults for sync check type and maximum record level errors for optimal performance.

    Detailed release notes can be found at https://docs.rocketsoftware.com
Current Members
18 Members
Hidden Member
forum Moderator
forum Moderator