Procedure components and concepts - assure_mimix - 10.0

Assure MIMIX Administrator Reference

Product type
Product family
Assure MIMIX™ Software
Product name
Assure MIMIX
Assure MIMIX Administrator Reference
First publish date

Each procedure is associated with an application group or a node. A set of default procedures is shipped with MIMIX for frequently used operations. For example, when an application group is created, copies of the shipped default procedures for that application group are also created to provide the ability to start, end, perform pre-check activity for switching, and switch the application group. For node procedures, the shipped defaults provide the ability to automatically run data protection reports to help you ensure your environment is protected the way you want.

Each operation is performed by a procedure that consists of a sequence of steps. Each step calls a predetermined step program to perform a specific subtask of the larger operation. Steps also identify runtime attributes for handling before and after the program call within the context of the procedure.

Each step program is a reusable configuration element that identifies a task performing program and its attributes which determine where it runs and what type of work it performs. A step program can perform work on an application group, its data resource groups, their respective data groups, or on specified nodes. A set of shipped step programs provides functionality for the default procedures created for application groups and nodes.

In addition, you can copy or create your own procedures and step programs to perform custom activity, change which procedure is the default of its type for an application group, and change attributes of steps within a procedure.

You can also optionally create step messages. These are configuration elements that define the error action to be taken for a specific error message identifier. A step message provides the ability to determine the error action taken by a step based on attributes defined in the error message identifier. Each step message is defined for an installation so it can be used by multiple steps or by steps in multiple procedures.