• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • 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.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Cannot restore, unknown error code from backup_sign utility

S

stoilis

Guest
Hi,

I am using Plesk 8.2.1 on Debian etch, using the latest updates on anything.

While trying to create a map file on a new server for restoration, I get the following error:

# pleskrestore --create-map backupfile -map map
Can't check backup file: unknown error code from backup_sign utility: 255
#

The error appears only after a while, about an hour of processing the backup file.

What is probably useful to mention, is that my backup is split at 2GB chunks. So, backupfile is just the first one, the whole list being:
-rw-r--r-- 1 root root 2146435072 2007-10-23 14:04 backupfile
-rw-r--r-- 1 root root 2146435072 2007-10-23 14:09 backupfile.001
-rw-r--r-- 1 root root 2146435072 2007-10-23 14:14 backupfile.002
-rw-r--r-- 1 root root 2146435072 2007-10-23 14:19 backupfile.003
-rw-r--r-- 1 root root 2146435072 2007-10-23 14:24 backupfile.004
-rw-r--r-- 1 root root 1173101133 2007-10-23 14:26 backupfile.005

Any hint on how to proceed to restoration?

Thank you in advance.
 
You should consider this as per SWSoft Knowledgebase article:

http://kb.swsoft.com/en/2279

RESOLUTION
Such error can be caused by missing certificate for backup signing. Try to generate the certificate with the command:

# $PRODUCT_ROOT_D/admin/sbin/backup_sign generate

Our symptoms were different. We got:

backup_sign: Can't find private key in database:
backup_sign: Can't get server's private key
23:17:23 ERROR Failed to create MIME message

Our backups were still completed, and the normal sizes were there, and even looking at the file it seemed intact, but every time we tried to create a map or restore something we got a backup corrupted message. The above Knowledgebase article sorted us out!
 
I solved the problem by generating the map file on the original server. There, it could be generated without a problem.
 
Back
Top