Activate Data Flow Dialog

Ops Center Protector User Guide

Version

7.9.x

Audience

anonymous

Part Number

MK-99PRT002-10

ft:lastEdition

2024-12-11

This dialog is displayed when one or more data flows are activated.

Rules files control the operation of the Ops Center Protector components on each node in the data flow definition. Rules files are generated by the Rules Compiler after policies have been created, the data flows have been defined and policies assigned to source and destination nodes.

CAUTION:

If you modify a policy or data flow that is currently active, then the data flow must be reactivated before your changes will take effect.

Figure. Activate Data Flow(s) Dialog (Compilation succeeded)

Figure. Activate Data Flow(s) Dialog (Compilation succeeded with warnings)

Figure. Activate Data Flow(s) Dialog (Compilation failed)

Control	Description
Compilation Details	This lists the output from the rules compiler and shows error, warning and information messages. If the compilation is successful, it includes a summary of what policies each node in the data flow will be implementing, forwarding or processing. The data flow can be activated. If the compilation is successful but contains warnings, then the information contained here will assist you in resolving potential issues with the data flow and/or policies. The data flow can be activated. If the rules fail to compile then the information contained here will assist you in resolving issues with the data flow and/or policies. You may need to iterate through several compilation cycles to remove all compilation errors. The data flow cannot be activated. CAUTION: Always inspect the compiler output. A successful compilation may contain warning messages which you should review. Successful compilation only indicates that the rules are valid, it does not imply that they are verified against your data protection requirements. Please regularly inspect the Default Dashboard and related status screens to ensure that your data is being protected in the manner you intended. Compiler errors are commonly caused by: incorrect or incomplete policies incomplete data flow definitions incorrect or incomplete data flow item attributes incomplete or ambiguous routes for policies missing parameters on destination nodes adding, editing or deleting policy classifications or operations without updating data flows
Compilation Outcome	Indicates one of the following: Blue - the rules are being compiled. Please wait. Green - the rules have been compiled successfully. The data flows and policies are valid (but not necessarily correct) and can be activated. Amber - the rules have been compiled successfully with warnings. The data flows and policies are valid (but not necessarily correct) and can be activated. The data flows and/or policies contain warnings that may need to be rectified. Red - the rules have not been compiled. The data flows and or policies contain errors that must be rectified before the data flows can be activated.
Activate	This button is only enabled once the rules have compiled successfully. Click to distribute the rules to the affected nodes and activate them. The policies will then take effect depending on the availability of affected nodes, operations, trigger conditions or schedules defined. The Logs Inventory can be used to watch and review the progress of data flow activation. Note: Rules activation methods depend on the type of policy: Host based: An initial 2 minute rules settlement period is applied after activation to allow rules to reach all participating nodes. If any operation is triggered within the settlement period it will be deferred until after it has expired. Block based: If the current rules are null or they predate the new rules, the ISM will wait up to 2 minutes for a new rule set to arrive. An information level log will be generated if this delay is invoked: `Storage proxy node does not have required rules, waiting up to <DELAY> seconds.` If, after waiting, the rules are still out of date, the ISM will attempt to use the rules it currently has. All: If a node in the data flow definition is unavailable, then the rules files cannot be sent to that node; activation continues for the available nodes. When the activation is complete, the new rules are activated on all available nodes. When the absent node becomes available and reconnects to the master, the new rules are sent automatically to that node and activated immediately after they are received. If any nodes are deleted from a previously activated data flow definition, then these nodes are deactivated when the new rules are activated. If any such node is not currently available, it is deactivated as soon as it reconnects to the master.

Control

Description

Compilation Details

This lists the output from the rules compiler and shows error, warning and information messages.

If the compilation is successful, it includes a summary of what policies each node in the data flow will be implementing, forwarding or processing. The data flow can be activated.

If the compilation is successful but contains warnings, then the information contained here will assist you in resolving potential issues with the data flow and/or policies. The data flow can be activated.

If the rules fail to compile then the information contained here will assist you in resolving issues with the data flow and/or policies. You may need to iterate through several compilation cycles to remove all compilation errors. The data flow cannot be activated.

CAUTION:

Always inspect the compiler output. A successful compilation may contain warning messages which you should review. Successful compilation only indicates that the rules are valid, it does not imply that they are verified against your data protection requirements. Please regularly inspect the Default Dashboard and related status screens to ensure that your data is being protected in the manner you intended.

Compiler errors are commonly caused by:

incorrect or incomplete policies
incomplete data flow definitions
incorrect or incomplete data flow item attributes
incomplete or ambiguous routes for policies
missing parameters on destination nodes
adding, editing or deleting policy classifications or operations without updating data flows

Compilation Outcome

Indicates one of the following:

Blue - the rules are being compiled. Please wait.
Green - the rules have been compiled successfully. The data flows and policies are valid (but not necessarily correct) and can be activated.
Amber - the rules have been compiled successfully with warnings. The data flows and policies are valid (but not necessarily correct) and can be activated. The data flows and/or policies contain warnings that may need to be rectified.
Red - the rules have not been compiled. The data flows and or policies contain errors that must be rectified before the data flows can be activated.

Activate

This button is only enabled once the rules have compiled successfully. Click to distribute the rules to the affected nodes and activate them. The policies will then take effect depending on the availability of affected nodes, operations, trigger conditions or schedules defined. The Logs Inventory can be used to watch and review the progress of data flow activation.

Note:

Rules activation methods depend on the type of policy:

Host based:
An initial 2 minute rules settlement period is applied after activation to allow rules to reach all participating nodes. If any operation is triggered within the settlement period it will be deferred until after it has expired.
Block based:
If the current rules are null or they predate the new rules, the ISM will wait up to 2 minutes for a new rule set to arrive. An information level log will be generated if this delay is invoked:

Storage proxy node does not have required rules, waiting up to <DELAY> seconds.

If, after waiting, the rules are still out of date, the ISM will attempt to use the rules it currently has.
All:
If a node in the data flow definition is unavailable, then the rules files cannot be sent to that node; activation continues for the available nodes. When the activation is complete, the new rules are activated on all available nodes. When the absent node becomes available and reconnects to the master, the new rules are sent automatically to that node and activated immediately after they are received.

If any nodes are deleted from a previously activated data flow definition, then these nodes are deactivated when the new rules are activated. If any such node is not currently available, it is deactivated as soon as it reconnects to the master.