Versions Compared

Version Old Version 12 New Version Current
Changes made by

Former user

Amit Munwes

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

AttributeMandatory?Description
Sync TypeYesDomain Pattern, Single Domain or Device as explained above
Pre Validation - Skip Major Version CheckYes

Select to allow Syncing configuration from higher firmware major release (e.g. 7.5.2.0) to lower major release (e.g. 7.2.0.0)
Syncing from higher firmware major release to lower major release may cause features that were introduced in the later version not to work.

Pre Validations - Skip Gateway License Features and OptionsYesSelect to allow Syncing configuration between devices with non-identical licenses (e.g. the source device has B2B or SQL-ODBC license and the target device does not)
Pre Validations - Skip Device Type CheckYesSelect to allow Syncing configuration between higher device types to lower device types (e.g. IDG to XG-45 or XI-52 to XG-45)
Approve Object Creation in Source DeviceYesWhen both source and target devices firmware versions are 7.5.2.X+
In order to test that the password map alias in the source and target are identical - DPOD will need approval to create a temporary object in the source device
Pre-Action ScriptNo

A user defined script to run before the task is executed.
The task will not be executed If the script fails (the return code was greater than 0)

See user defined scriptsUser Defined Scripts for more information

Pre-Action QuiesceNo

Should the device(s) be quiesced before the sync is executed.
The timeout value that is passed to the quiesce SOMA is controlled by a system parameter (see maintenance configurable parametersMaintenance Configurable Parameters for more information)

Deployment PolicyNoAn optional deployment policy from the source or target device, if the object is not found on the device, the sync task will not execute
Deployment Policy VariablesNoAn optional deployment policy variables object on the target device, if the object is not found on the target device, the sync task will not execute
Post-Action UnquiesceNoThis option cannot be edited - it will be automatically set to the value of the Pre-Action Quiesce.
The user may set how long DPOD waits for the unquiesce operation to finish before cancelling the task via a system parameter (see maintenance configurable parametersMaintenance Configurable Parameters for more information)
Post-Action ScriptNo

A user defined script to run after the task is executed.
The user selects whether the script should run always when a task completes, or only when the task execution fails.

See user defined scriptsUser Defined Scripts for more information

Error PolicyYes

Select how this backup activity handles errors.
Plan's Default - Use the value that was set for the planSync Plan
Halt - When the task failed validation or execution, stop all other tasks from this plan that are waiting for execution
Ignore - When the task failed validation or execution, ignore and continue to run other tasks from this plan

Stop on Objects Deletion Error in Target DeviceYesBefore importing the object to the target domain, DPOD will first delete objects from the target domain - check this option to stop the import if deletion of those objects failed

...