• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • 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.

plesk recovery

  1. Superbutler

    Issue Testing Disaster Recovery - Windows: Stored Procedures missing after full backup restoration on another server.

    Hi, We are testing disaster recovery on Windows Server. We performed a full backup of Plesk, including databases and subscriptions, with the database located on the same Plesk server. The backup was successfully generated. We then restored this backup on another server with the same version of...
  2. E

    Question Full server restore, if I have another Plesk server operational

    Hello, Suppose this use case: 1. Plesk server (#server-1) on a certain location, with a few hundreds subscriptions / domains. It goes down and is not recoverable. 2. Full backups, that is the whole content of var/lib/psa/dumps/ - obtained with rsync on another machine (#backup-machine). 3...
  3. S

    Resolved Website Backup Plesk recovery New Server not working

    Hello, tried to recover Full Domain Backup from old to new Server. Get the following error message: [root@ /]# /usr/local/psa/bin/pleskrestore --restore /tmp/backup_info_1902221014.xml.tar -level domains -ignore-sign <?xml version="1.0"?> <conflicts-description> <conflict id="1"...
Back
Top