• 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.

backup of vital plesk settings

balechaparka

Basic Pleskian
In my server there is a scheduled task which was automatically added by plesk panel software.The scheduled task is backup of vital plesk settings. (There is a manual backup option in plesk panel for domain and server)But this scheduled task creates a backup in this path C:\Program Files (x86)\Parallels\Plesk\MySQL\Backup
What this backup contain? Should i copy this backup to other locations so that it maybe useful in future? can i use this backup for restoring of plesk settings?
 
This is a backup of internal Plesk database. As long as you do proper backup of your Plesk, you probably don't need to care for these files, all settings anyway will be in a regular Plesk server backup.

These files could help if (for example) you try to change plesk database manually and break some tables. Database backup could help you restoring broken DB without rollback the whole Plesk to previously backed up state.
 
So backup of vital settings does backup of internal database of plesk . Is it necessary that it should run in scheduled task(as it added automatically in my server)? Does it backup used by plesk in anyway?
 
Back
Top