• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Resolved backup plesk 12.5 to onyx 17.5 failed

dj ramc

Basic Pleskian
I tryed to restore a backup from Plesk 12.5 to Plesk Onyx 17.5 But it did not work.
i got this messsage from backup manager
This operation is taking too long. Check the results in a few minutes.
after this even plesk not accesible
i get now this message when try to open login page of plesk
ERROR: Plesk\Exception\Database: DB query failed: SQLSTATE[HY000]: General error: 1030 Got error 28 from storage engine, query was: DESCRIBE `sessions`

Additionally, an exception has occurred while trying to report this error: Zend_Exception
No entry is registered for key 'translate' (Mysql.php:53)

Search for related Knowledge Base articles
 
mount | grep data

/dev/root on / type ext3 (rw,relatime,errors=remount-ro,user_xattr,acl,barrier=1,data=writeback)
/dev/md3 on /var type ext4 (rw,relatime,quota,usrquota,grpquota,data=ordered)
/dev/root on /var/named/chroot/etc/named type ext3 (rw,relatime,errors=remount-ro,user_xattr,acl,barrier=1,data=writeback)
/dev/md3 on /var/named/chroot/var/named type ext4 (rw,relatime,quota,usrquota,grpquota,data=ordered)
/dev/root on /var/named/chroot/etc/named.rfc1912.zones type ext3 (rw,relatime,errors=remount-ro,user_xattr,acl,barrier=1,data=writeback)
/dev/root on /var/named/chroot/etc/rndc.key type ext3 (rw,relatime,errors=remount-ro,user_xattr,acl,barrier=1,data=writeback)
/dev/root on /var/named/chroot/usr/lib64/bind type ext3 (rw,relatime,errors=remount-ro,user_xattr,acl,barrier=1,data=writeback)
/dev/root on /var/named/chroot/etc/named.iscdlv.key type ext3 (rw,relatime,errors=remount-ro,user_xattr,acl,barrier=1,data=writeback)
/dev/root on /var/named/chroot/etc/named.root.key type ext3 (rw,relatime,errors=remount-ro,user_xattr,acl,barrier=1,data=writeback)
/dev/root on /var/named/chroot/etc/services type ext3 (rw,relatime,errors=remount-ro,user_xattr,acl,barrier=1,data=writeback)
/dev/root on /var/named/chroot/etc/protocols type ext3 (rw,relatime,errors=remount-ro,user_xattr,acl,barrier=1,data=writeback)
 
# pwd
/usr/local/psa
# mount --bind /var/PP/psa_tmp tmp

# pwd
/usr/local/psa/PMM
# mount --bind /var/PP/psa_pmm_tmp tmp

is this a good idea to mount on /var ??
 
i did like this post says it' s still not solved

now # mount | grep data
/dev/root on / type ext3 (rw,relatime,errors=remount-ro,user_xattr,acl,barrier=1,data=writeback)
/dev/md3 on /var type ext4 (rw,relatime,quota,usrquota,grpquota,data=ordered)
/dev/root on /var/named/chroot/etc/named type ext3 (rw,relatime,errors=remount-ro,user_xattr,acl,barrier=1,data=writeback)
/dev/md3 on /var/named/chroot/var/named type ext4 (rw,relatime,quota,usrquota,grpquota,data=ordered)
/dev/root on /var/named/chroot/etc/named.rfc1912.zones type ext3 (rw,relatime,errors=remount-ro,user_xattr,acl,barrier=1,data=writeback)
/dev/root on /var/named/chroot/etc/rndc.key type ext3 (rw,relatime,errors=remount-ro,user_xattr,acl,barrier=1,data=writeback)
/dev/root on /var/named/chroot/usr/lib64/bind type ext3 (rw,relatime,errors=remount-ro,user_xattr,acl,barrier=1,data=writeback)
/dev/root on /var/named/chroot/etc/named.iscdlv.key type ext3 (rw,relatime,errors=remount-ro,user_xattr,acl,barrier=1,data=writeback)
/dev/root on /var/named/chroot/etc/named.root.key type ext3 (rw,relatime,errors=remount-ro,user_xattr,acl,barrier=1,data=writeback)
/dev/root on /var/named/chroot/etc/services type ext3 (rw,relatime,errors=remount-ro,user_xattr,acl,barrier=1,data=writeback)
/dev/root on /var/named/chroot/etc/protocols type ext3 (rw,relatime,errors=remount-ro,user_xattr,acl,barrier=1,data=writeback)
/dev/md3 on /usr/local/psa/tmp type ext4 (rw,relatime,quota,usrquota,grpquota,data=ordered)
/dev/md3 on /usr/local/psa/PMM/tmp type ext4 (rw,relatime,quota,usrquota,grpquota,data=ordered)
 
i have done this with succes finally
i will put here my experience
after mariadb error i couldn't restore plesk but anyway it was new server i decide to reinstall os with plesk after this i logged in by shell and created a bash for downloading plesks backup files from ftp server after this is done just doing
# /usr/local/psa/bin/pleskrestore --restore backup_1707220502.tar -level server -ignore-sign

and tatatan 15GB 10-15 domains and tons of email and also mysql db's are back on new server.

thanks for any help

byee
 
Back
Top