• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

Pleskbackup (9.2.3) fails with

M

MaximillianU

Guest
Using plesk 9.2.3 (w/o possibility to upgrade which is one of the reasons for the backup)
on debian 64amd, lenny (due to reinstallation)

using

/opt/psa/bin/pleskbackup domains-name -vvz --output-file=/backup/target.bak

I get the error

ERROR The pmmcli STDERR:'the name `ate' is not a tty'
the name `ate' is not a tty
the name `ate' is not a tty
-------------- Start print backup log hire --------------
the name `ate' is not a tty
<?xml version="1.0" encoding="UTF-8"?>
<response>
<errcode>0</errcode>
<data>
<task-log>07:00:03 INFO ------------------------------------------------------------
07:00:03 INFO Migration status reporting initialized.
07:00:03 INFO Status file: /opt/psa/PMM/sessions/2010-11-21-080003.434/dump-status.xml
07:00:03 INFO ------------------------------------------------------------
</task-log>
</data>
</response>
-------------- End print backup log hire --------------

You can view additional information in the log file located in /opt/psa/PMM/sessions/2010-11-21-080003.434/migration.result directory. This directory will be removed automatically after 30 days

Runtime error: The backup failed with errors!

I looked around tryed some other servers with Plesk 9.5.2 and got the same message.
Looks to me like a problem of basic linux package installation below or - any other ideas ?
 
Back
Top