...
- Domain Pattern - Enter source device name, source domain pattern and target device pattern.
All the source domains matching the pattern will be synced to domains with the same names on the target device(s)
For example:
Source Device = QA1, Source Domain = Domain*, Target Device = QA2, QA3
Results - the domain QA1/Domain1 will be synced to QA2/Domain1 and QA3/Domain1
the domain QA1/Domain2 will be synced to QA2/Domain2 and to QA3/Domain3 - Single Domain - Enter source device and domain names (no patterns) and the target device pattern and target domain name
This will sync a single domain from the source to the same or different domain name on the target device(s)
For example:
Source Device = QA1, Source Domain = Domain1, Target Device = QA2, QA3, Target Domain = CopyDomain1
Results - The domain QA1/Domain1 will be synced to QA2/CopyDomain1 and to QA3/CopyDomain1 - Device - Enter source device name and a target device pattern, all the domains from the source device will be synced to the target device(s)
For Example:
Source Device = PROD1, Target Device = DRP*
Results - All the domains from device PROD1 will be synced to devices DRP_Active and DRP_Inactive
| Attribute | Is Mandatory? | Description |
|---|---|---|
| Sync Type | Yes | Domain Pattern, Single Domain or Device as explained above |
| Pre Validation - Skip Major Version Check | Yes | Check this option 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 Options | Yes | Check this options Select to allow Syncing configuration between devices with unidentical 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 Check | Yes | Check this option Select 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 Device | Yes | When 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 your approval to create a temporary object in the source device |
| Pre-Action Script | No | A user defined script to run before the task is executed. See user defined scripts for more information |
| Pre-Action Quiesce | No | Should the device(s) be quiesced before the sync is executed. |
| Deployment Policy | No | An 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 Variables | No | An 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 Unquiesce | No | This 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 parameters for more information) |
| Post-Action Script | No | A user defined script to run after the task is executed. |
| Error Policy | Yes | Select how this backup activity handles errors. |
| Stop on Objects Deletion Error in Target Device | Yes | Before 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 |
...