Backup, Restore & Migration
Articles about FTP service, Backup & Restore and Migration processes.
- Backup via Plesk Google Drive fails: your computer or network may be sending automated queries
- Unable to migrate a subscription: Failed to perform action: Restart IIS for IDN domains
- Backup can not be created in Plesk: "Document is empty, line 1, column 1 (, line 1)" or "None (line 0)"
- Unable to create a backup in Plesk: Failed to exec backup_restore_helper: Exit code: 3: System user unavailable
- Plesk backup finishes with warning message: lscache/.cm.log: Permission denied
- Scheduled backups fails since update to Plesk Obsidian 18.0.47: expected str, bytes or os.PathLike object, not int
- Backups fail after the update to Plesk Obsidian 18.0.47: The backup process failed: can't concat str to bytes
- Migration from Plesk servers with MySQL<5.5 fails: Character set 'utf8mb4' is not a compiled character set
- Unable to start migration on Plesk server: Command execution failed on the local server with non-zero exit code.
- Plesk Backup restores with a warning: Unable to create FTP account: The user jdoe already exists.
- Migration to another Plesk server fails: Unable to restore DNS zone from a backup: Incorrect DNS record values were specified: example.com. IN <Record Type> *.example.com.: ('ttl' = '0')
- Unable to create the remote backup at Google Drive:
- Unable to restore Plesk backup on a different server: The archive is not valid Plesk backup or has been created in an unsupported Plesk version
- Backup process can be stuck since Plesk update to 18.0.41 spawning a lot of backupmng processes
- Unable to schedule domain's backups in Plesk: Certificate has expired
- Unable to start migration in Plesk: Failed to connect to the source server 'source' (203.0.113.2) by SSH: encountered RSA key, expected OPENSSH key
- Backup in Plesk is created with warning: Unable to back up database. Error: Unable to find row with id in data_bases table.
- Unable to start Plesk migration from DirectAdmin with AlmaLinux to Plesk server:'directadmin' (203.0.113.2) is not supported
- Mailboxes are not created during migration of a subscription with suspended owner/subscription/domain via Plesk Migrator
- How to extract files from a Plesk backup archive
- How to switch to the new tokens scheme after Dropbox Backup update?
- Plesk Backup manager screen takes too much time to load
- Leftovers remain in Plesk domain's backup manager that can not be removed
- Does Plesk support Amazon S3 compatible Backblaze B2 storage?
- Pre-migration warning when migrating from server with custom Apache modules: The following Apache modules are not installed
- Plesk Pre-Migration check shows warning: Web server settings. Not all data may be migrated
- Is it possible to restore a full domain backup on another domain?
- Migration of the domain in Plesk failed: Failed to allow applications in Classic to work in Integrated mode after migration in web.config files
- How to retain databases during Plesk migration when both servers share same remote database server?
- Plesk backup finished with warning: Failed to close volume: (5) Input/output error