Restoring backup archive
....and if the backup was generated by cPanel's fullbackup generator and there still are problems importing the account ?
Neither account transfer tool didn't work.
and account transfer:
Starting "RESTORE" for Account "************"
Restore File: "/home/backup-9.30.2014_11-01-20_******.tar.gz"
Restore Reseller Privs: "yes"
Restricted mode: "no"
Express mode: "no"
ArchiveManager
Preparing archive for restoration "
ArchiveManager
Failed to extract the archive at "/home/backup-9.30.2014_11-01-20_*******r.tar.gz": The tar archive extraction failed because of an error: The "/bin/gtar" command (process 870978) reported the "ENOENT" (2) error when it ended.: "/bin/gtar: Unexpected EOF in archive /bin/gtar: Unexpected EOF in archive /bin/gtar: Error is not recoverable: exiting now ".
Failed: Account Restore Failed: "Failed to extract the archive at "/home/backup-9.30.2014_11-01-20_****.tar.gz": The tar archive extraction failed because of an error: The "/bin/gtar" command (process 870978) reported the "ENOENT" (2) error when it ended.: "/bin/gtar: Unexpected EOF in archive /bin/gtar: Unexpected EOF in archive /bin/gtar: Error is not recoverable: exiting now "."
and account transfer:
Starting "RESTORE" for Account "***********"
Failed: Error while executing "/usr/local/cpanel/scripts/getremotecpmove": The "/usr/local/cpanel/scripts/getremotecpmove" command (process 863276) reported the "EPERM" (1) error when it ended.
-
Hello :) I moved this post into it's own thread because it's not related to the original question. The error message you provided indicates the archive is corrupted. Are you able to generate a new backup for the account? Thank you. 0 -
I've run into this exact same problem. Regenerating a new backup had no effect. 0 -
]I've run into this exact same problem. Regenerating a new backup had no effect.
What method are you using to restore the account that was generated through cPanel? Have you verified the backup generates successfully? Thank you.0 -
I found the issue. The backup was silently choking on a large 7gb log file. (Yes, that's nuts. It was caused by a WordPress backup plugin. It's been removed.) Once that was deleted, it backed up fine. :) 0 -
I am happy to see you were able to address the issue. Thank you for updating us with the outcome. 0
Please sign in to leave a comment.
Comments
5 comments