• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Question backup manager fails when remote sftp got an dir/permission error. (local and remote set)

hardbrasil

Regular Pleskian
Server operating system version
Almalinux 8 latest
Plesk version and microupdate number
PLesk latest
Hi fellas,
i set my backup manager to store the backp files into local (Plesk server) and remote trough SFTP.
untill here everthing was fine.

when i access the backup list today i saw many erros into backup process:

Unable to create the remote backup: Transport error: Extension transport: ext://sftp-backup/server/: Failed to transfer the remote file: permission denied

plesk2.jpg
the backup file was not created.
so i adjust the folder permition, and i will wait if will works tomorow.

the point is, i choose the option to save local AND remotelly, so for a matter o logical, if remote fails the backup still need to be performed and save locally, ate least this is my expectation, make sense?

plesk-issue.png

so i would like to suggest this for the Plesk team.

maintaing the backup locally even the remote fails.

thanks
 
after change the chmod of folder to 777, even after this, PLesk backup was not able to send backup files to there.
i think this is an bug of plesk.
 
Could you please check the backup logs in /var/log/plesk/PMM/<your backup>?
There you can find out more about the reason why the backup failed.
 
This does not seem like a bug, but rather some limitation of mis configuration on the target server.

I second the suggestion from @Maarten. to look at the backup for more details.
 
Back
Top