Policies¶
The file should be structured as follows.
conflict-resolution-rulesRequired, document root element.policy- Required, contains the policies descriptions. Children, if present,
must be placed in the order shown on the scheme.
timingOptional, contains description of policy on resolving timing conflicts. See the structure below. Must be present in the document if a timing policy should be used during the restore. May not be present in the document if no policy required for timing conflicts.resource-usageOptional, contains description of policy on resolving resource usage conflicts. See the structure below. Must be present in the document if a resource usage policy should be used during the restore. May not be present in the document if no policy required for resource usage conflicts.configurationOptional, contains description of policy on resolving configuration conflicts. See the structure below. Must be present in the document if a configuration policy should be used during the restore. May not be present in the document if no policy required for configuration conflicts.
ruleOptional, contains the rule descriptions. For details on the node structure, refer to the Resolutions Description Format: Rules section.
The policy elements have the same structure:
The resolution element must not be empty, it is required that it
contains one, and only one of its children elements:
do-not-restoreSets the Do Not Restore resolution, empty value.proceed-with-currentSets the Proceed With Current resolution, empty value.automaticSets the Automatic resolution, empty value.overuseSets the Overuse resolution, empty value.overwriteSets the Overwrite resolution, empty value.renameSets the Rename resolution, empty value.new-nameRequired, makes sense only if defined for configuration conflicts. Specifies a name of new configuration that should be assigned to all conflict objects. The value must be a string.




