• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Forwarded to devs An error occurred during the scheduled backup

Brujo

Silver Pleskian
Plesk Guru
User name: Brujo

TITLE

An error occurred during the scheduled backup

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Plesk Obsidian, Version 18.0.24
Ubuntu 16.04.6 LTS‬

PROBLEM DESCRIPTION

I get for some domains which are daily scheduled backuped to Microsoft Onedrive the following email

The following error occurred during the scheduled backup process:

pmm-ras failed (Error code = 1):

STDOUT: Repository error: Failed to read backup backup_xyz.de_2002120547.tar: Transport error: Extension transport: ext://one-drive-backup/subscription/46/: The offset 0 exceeded file size 0
STDERR:

when i go to Plesk Panel > Domain > Backupmanager the Backup has its green checkmark and the normal size. I am also able to restore Selected objects.

I allready removed and established the remote storage settings and changed scheduled backup time

STEPS TO REPRODUCE

for a particular domain set up the Remote Storage Settings > Microsoft OneDrive Backup = ready for use
Schedule a daily fullbackup. But this is not happend for all schedued Backups.

ACTUAL RESULT

receive daily error mail

EXPECTED RESULT

figgure out why the daily mail is send

ANY ADDITIONAL INFORMATION

there are no warnings or error in the /var/log/plesk/PMM logfiles

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug
 
Last edited:
Try to enable verbose logging in /usr/local/psa/admin/conf/panel.ini
[debug]
enabled = on

[log]
filter.priority = 7
show.util_exec = on
show.util_exec_io = on
and in /usr/local/psa/admin/share/pmmcli/pmmcli-rc
FORCE_DEBUG_LOG 1
and try to find errors in
- /var/log/plesk/panel.log
- /var/log/plesk/PMM/migration.log
 
It looks like the file backup_xyz.de_2002120547.tar is empty and cannot be rotated automatically.
 
OK I changed the backup from daily full to incremental and now after a few days back to daily full. Obviously this was enough and the system healed itself.
 
Back
Top