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

Recovery plan

balechaparka

Basic Pleskian
I wanted know some details about diaster recovery of my website.
As recovery plan i have ftp backup and i do backup of my important website files and sql database files.
But in case my server gets any problem with failure then i want a recovery plan so that my website continue to work.So i do have another server which is similar to the server i am already having.
So if at any time this server gets any problem then i can switch to another server.That server already has the files needed for the website etc.
But i think changing the DNS requires about 4 hours.So shifting from this server to another server will require some hours.
So is there any method for instant changing of DNS? Or is there any method by which i can recover my website as soon as possible without a downtime?
 
You could use a cloud-based fail-over service. This way, your DNS remains the same and all traffic is routed to the primary server. In the event of a failure, traffic would be sent to the secondary server. The challenge is, keeping your database in sync.
 
Back
Top