What’s new in Assure MIMIX 10

Easier Configuration

The new Journal driven Data Group support dramatically simplifies configuration management – especially when complex journaling scenarios exist – eliminating exclude/include selection rules. Users will now be able to protect libraries, using a minimal number of Data Group selection rules while leave existing journaling intact. This new capability represents a paradigm shift from traditional MIMIX replication design. By using Journal Centric replication design concepts, a complete configuration which protects many libraries with many journals can be created with much less effort than in previous MIMIX versions.

• Data Groups can now be optionally configured to automatically start or stop object replication (*LIB, *FILE, *DTAARA, *DTAQ, *IFS) based upon the object’s journaling status. When journaling is started on an object, MIMIX automatically begins replicating it, and stops replicating it if journaling for the object is stopped.
• To enable precise control of replication, individual objects within a library that is included in a Journal Centric Data Group may be individually excluded from the Journal Centric automation.
• Data Groups may alternatively be configured to replicate specific objects within a library which cannot be journaled (i.e. *PGM) regardless of whether any journaled objects within the same library are included in the Data Group or are instead protected by a different Journal Centric Data Group.
• MIMIX can be configured to automatically create and delete Journal Centric Data Groups as IBM i journals are created and deleted. This ensures immediate, automated protection for application-generated journals and provides enhanced support for the creation of Schemas/SQL Collections.

Faster, more intelligent Synchronization

HA users have simple, yet demanding requirements: synchronize a production and backup system, keep them in sync in real-time, and don’t impact the applications which are serving the business. Emerging in the IBM i marketplace today is the requirement to synchronize large, rapidly changing production databases from one site to another without a tape restore operation to create the initial copy of the data on the backup system. IBM i shops are adding Hosted, or Cloud based availability solutions for their on-premises systems. Replication from/to/within and between Cloud environments, is becoming the norm. Physical tape devices are scarce. Shops may need to migrate LPARs across political boundaries. Shipping of tape media is no longer practical.

To better serve this new cloud-centric ecosystem, Assure MIMIX 10 brings improvements to overall Object Synchronization. Objects may be synchronized for many reasons: Initial sync for migrations and new backup systems, Audit recoveries, Virtual Switch Recoveries, Target Journal Inspection Recoveries and apply job exception handling are all actions that may result in a synchronization action. Assure MIMIX 10 now provides a synchronization processing queue and manager which will result in more orderly and complete synchronization actions, with minimal user interaction all while limiting the impact to the production system. These improvements will enable Assure MIMIX users to efficiently synchronize an LPAR wherever they need it.

New 5250 panel for Recoveries

Users will no longer be limited to only using the Assure Unified Interface (GUI) to perform recovery operations. Information about Recoveries is now also available using the 5250 (green-screen) interface. The Work with Recoveries display (WRKRCY command) has a new view that allows users to see in-progress and failed recoveries that were submitted to the replication Manager for processing.