• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Resolved Backup With Cron

karam

Basic Pleskian
Hello pleskians,

So, am running the following command :
/usr/local/psa/bin/pleskbackup --server -backup-password MYPASS -incremental -description 'Cron Backup' -s -output-file ext://xxxxxxx/

and I got several questions :

1- MYPASS isn't wrapped by quotes, is that okay for pleskbackup command ?
2- MYPASS is the same as the one I have set in the Plesk UI settings, and it's incrementing backups above the initiated scheduled ones, is it stable ?

My concerns are the inconsistencies with backups, as I have scheduled backup running daily 1 time and that command running each X hours, (They don't overlap though) but my concern is specifically to the backup password.. to make my question simple.... Does setting MYPASS value in the command line as equal to the password in Plesk UI for scheduled backups IS CONSISTANT ?

Thank you.
 
1. Yes, as long as you don't have any special characters, ie, spaces or !
2. Yes, that's fine.

As far as backup integrity goes, you should regularly test your backups either way.
 
Back
Top