Dump is not valid Dump didn't pass sign verification Identify Plesk object which is a user of the resource Identify Plesk object, owner of the resource Identifier of a Plesk object with the same GUID as conflict object Identifiers of Plesk objects which require the resource Structure of XML Transform Specification for a node search Dump filename without path. Can be used for showing in UI Dump full name, should be used for dump-specification composing Initial incremental backup base timestamp. Actually migration-dump/dump-info/description content GUID of the user which made the dump Status of a dump. Default value is "OK". Should be used in cases when file is not Plesk Backup file or info.xml did not pass xsd validation Should be used in cases sign check did not passed Some content files are corrupted Some parts of incremental backup were not found Status of a backup process. Default value is "OK". Number of files, which were detected as non-dumps The same as dump-list/dump/@fullname The same as dump-list/dump/@name The same as backup-task-description/misc/@backup-profile-name Mail task result and log to this email Dump transformer option name. 'convert-mailnames-to-users': Create user accounts based on imported mail accounts, 'import-anti-spam-training': Import Anti-Spam training from the specified mail account 'migrated-users-role': Role name which will be assigned to created users List of corrupted content files. Should be used with dump-status=CONTENT-ERRORS. Absense of element means objects not selected for migration Task-id should be used for mixed children for ability to determine task-id for children tasks Specification of object who want to see list of backups Specification of object who want to delete backup Type of Plesk Object specified. The absence of attribute means "all types of Plesk Objects" or "any Plesk Object type" Database ID of object Name of object. Used in case when there are no top .discovered directory. For admin: not required, for reseller and client: login for domain: ASCII-name Custom backup marker GUID of the user which perform the operation GUID of the person who start backup task Verbose level for backup process, number means amount of -v option Database ID of object selected to backup login for reseller and client, domain name for domain Set this attribute to "true" to backup all objects specified type Type of object selected to backup Identify initial dump for incremental backup Make incremental backup. Base will be founded automatically or full dump will be created instead Split size in bytes Suspend objects during backup, default=false If present - send log of backup task from this email If present - send log of backup task to this email Use native MSSQL backup format for database backup Dump description, text Suspend objects during backup, default=false If this element presents, pmm.cli should try to execute Conflict Resolver with specified conflict resolution rules; if after resolution conflicts still here, DumpOverview should be based on RestoreSpecs after conflicts resolution Define what process is performed: migration or restore Delete dumps when restoration process is finished is they were downloaded from personal FTP repository XML Transform Specification The element specify types of errors which should be ignored if appears. Start restore task even if conflicts found Start restore task even if sign validation failed Structure of XML Transform Specification for a node search Should be used with @type="file"; may be used with @type="foreign-ftp" Backup should be placed into internal local repository according to backup format Backup should be placed on external (custom) FTP as file (not as directory) Backup should be exported as file (UI will use this option for case when backup should be downloaded to user workstation). Backup should be placed on external backup FTP node as directory Absense means "any"