Problems restoring cP 10 backup on cP 11 server

Xenon101

Well-Known Member
Mar 13, 2005
72
0
156
The client account on the old cP 10 server has already been removed, and all I have to show for it is the daily_1.tar.gz downloaded from client cpanel.

I am trying to restore this using the full backup/cpmove feature in cP 11 but getting the following error.

Extracting tarball...................
...............
...............
...............
...............
...............
Done
cpmove- prefix is missing, but non prefixed directory exists.. the cpmove- prefix discarded.
Extracting Domain....Done
Sorry, the copy failed. Unable to find the cpanel user file. Is the archive missing (cwd: /home/cprestore loaded afanfm/cp/afanfm)?
checked 14 files.....
Anyone else come across this and maybe knows a fix?? Really need this to work! :(
 

Xenon101

Well-Known Member
Mar 13, 2005
72
0
156
the file is named cpmove-clientsname.tar.gz however it appears that it isn't that way in the directory structure, rather than the tar filename as the tar is already extracted.

It's not actually a cpmove file generated from cPanel its a download of the daily backup. Could this be the problem?
 

FC5_Slut

Member
Sep 29, 2006
23
0
151
I've come across the same with a full generated cPanel backup.

Searching, Extracting, Done.

Extracting Domain....Done

Sorry, the copy failed. Unable to find the cpanel user file. Is the archive missing (cwd: /home/cprestore loaded <backupfile>

checked <x> files.....
 

lehels

Well-Known Member
Jul 10, 2006
91
0
156
Same here:


Restore for username

Searching /home....
Found username.tar.gz !
Moving Packge to /home/cprestore/username.tar.gz

Extracting tarball....Done

Extracting Domain....Done

Sorry, the copy failed. Unable to find the cpanel user file. Is the archive missing (cwd: /home/cprestore loaded username/cp/username)?
checked 5 files.....

I assume it's because of the folder: /userdata/ [?] which is really missig from the original backup.
 

nimon

Member
Oct 16, 2005
21
0
151
Is there any way to solve this problem?

I need to restore a backup , I'm using a win server by ftp for backup and I got same error for restore:
I moved the user.tar.gz from windows to cp server /home

Searching /home....
Found user.tar.gz !
Moving Packge to /home/cprestore/user.tar.gz

Extracting tarball...................
Done

Extracting Domain....Done

Sorry, the copy failed. Unable to find the cpanel user file. Is the archive missing (cwd: /home/cprestore loaded user/cp/user)?
checked 80 files.....
How to restore this user?
And how can I fix this problem on backup configuration?
 

aboleth

Well-Known Member
Sep 8, 2005
50
0
156
I'm having the same exact error, I've verified that the file does exist in the archive. anyone have an idea on this?

Thanks,
Nick
 

alex.lucas

Member
May 21, 2005
7
0
151
Same problem

I had the same problem with a daily backup. Weird, but with a weekly backup the problem didn't happen and I was able to restore it.
 

timw

Registered
May 27, 2008
1
0
51
Trailing Space

If the username for the account is copied and pasted from the old server's list accounts with a trailing space it seems that the transfer works but the restore doesn't because the "cpmove-someaccount .tar.gz" file cannot be read dueto the appended space in the file name.

A bit of form validation from WHM to prevent usernames with trailing spaces being entered would solve the problem.
 

cPanelDavidG

Technical Product Specialist
Nov 29, 2006
11,212
13
313
Houston, TX
cPanel Access Level
Root Administrator
If the username for the account is copied and pasted from the old server's list accounts with a trailing space it seems that the transfer works but the restore doesn't because the "cpmove-someaccount .tar.gz" file cannot be read dueto the appended space in the file name.

A bit of form validation from WHM to prevent usernames with trailing spaces being entered would solve the problem.
Testing on cPanel 11.24.7-E37011, when using the account creation screen in WHM, trailing spaces are truncated. On the account modification screen in WHM, usernames with a trailing space are treated as invalid. So it appears the form validation you are looking for is either already implemented or will propagate to your servers in the near term.
 

syrinx2112

Member
May 28, 2008
6
0
51
Is there a definitive answer as to how to resolve this?

I am getting this same response when I try to restore and no matter what I do I get that message.

I remember using this feature when I transferred from a smaller to a bigger server and it worked like a charm then.

What I did: I did terminate my user account so the restore will recreate it and the db and all that goes with it, again, it did this the last time.

So I ran this via WHM and command line and no luck... I get the same message..

1. I make sure my backup gz file is in /home [I have tried using backup gz and the cpmove gz]
2. I use WHM and specify my user. And I use /scripts/restorepkg --force 'username'
3. And that is when I get that pain the a-s message..

Please....is there a solution???

Thanks.:mad::confused::eek:
 

cPanelDavidG

Technical Product Specialist
Nov 29, 2006
11,212
13
313
Houston, TX
cPanel Access Level
Root Administrator
Is there a definitive answer as to how to resolve this?

I am getting this same response when I try to restore and no matter what I do I get that message.

I remember using this feature when I transferred from a smaller to a bigger server and it worked like a charm then.

What I did: I did terminate my user account so the restore will recreate it and the db and all that goes with it, again, it did this the last time.

So I ran this via WHM and command line and no luck... I get the same message..

1. I make sure my backup gz file is in /home [I have tried using backup gz and the cpmove gz]
2. I use WHM and specify my user. And I use /scripts/restorepkg --force 'username'
3. And that is when I get that pain the a-s message..

Please....is there a solution???

Thanks.:mad::confused::eek:
To anyone still experiencing this issue, I recommend letting our technical analysts take a look at this for you. This will allow us to trace what, exactly, is causing this error to appear.