Failed cpanel transfer refuses to resume

farooq

Member
Dec 22, 2011
20
0
51
cPanel Access Level
Root Administrator
My previous transfer failed for some reason, so i terminated all accounts which were incomplete to start a new transfer. Now when i try to start the new transfer, i get these errors and i cannot start the transfer :

TRANSFER: 6 completed, 0 had warnings, and 0 failed.
RESTORE: 0 completed, 0 had warnings, and 6 failed.

RESTORE: Account “xxx1”: Account Restore Failed: “Account failure: Failed to create the account: (XID z8bp3r) The domain “xxxxx.com” already exists in the userdata.”
The “Account” restore module failed because of an error: Failed to create the account: (XID z8bp3r) The domain “xxxx.com” already exists in the userdata.
RESTORE: Account “xxxx2”: Account Restore Failed: “Account failure: Failed to create the account: (XID f2q42d) The domain “1xxxxx.ws” already exists in the userdata.”
The “Account” restore module failed because of an error: Failed to create the account: (XID f2q42d) The domain “xxxx.ws” already exists in the userdata.
RESTORE: Account “anxx”: Account Restore Failed: “Account failure: Failed to create the account: (XID 7pr399) The domain “xxxxx-xxx.com” already exists in the userdata.”
The “Account” restore module failed because of an error: Failed to create the account: (XID 7pr399) The domain “xxxx-xxx.com” already exists in the userdata.
RESTORE: Account “xxx3”: Account Restore Failed: “Account failure: Failed to create the account: (XID ktyhhq) The domain “xxxxxx.biz” already exists in the userdata.”
The “Account” restore module failed because of an error: Failed to create the account: (XID ktyhhq) The domain “xxxx.biz” already exists in the userdata.
RESTORE: Account “xxx5”: Account Restore Failed: “Account failure: Failed to create the account: (XID trj3x7) The domain “xxxxx.com” already exists in the userdata.”
The “Account” restore module failed because of an error: Failed to create the account: (XID trj3x7) The domain “xxxx.com” already exists in the userdata.
RESTORE: Account “xxx6”: Account Restore Failed: “Account failure: Failed to create the account: (XID zzuw34) The domain “xxxxx.co” already exists in the userdata.”
The “Account” restore module failed because of an error: Failed to create the account: (XID zzuw34) The domain “xxxxx.co” already exists in the userdata.
expanded error :

Starting “RESTORE” for “Account” “xxxxx”.
Restore File: /home/cpmove-xxxxx.tar.gz.part00001
Restore Reseller Privs: no
Restricted mode: no
Live transfer: yes
Target “/home” on host “server.xxxxxx.top” has 3.2 TB free and requires at least 29.07 GB free, which includes space for temporary files.
Target “/home” on host “server.xxxxxx.top” has 236,444,111 inodes free and requires at least 677,332 inodes free, which includes space for temporary files.
The “BandwidthData” restore module has the following areas disabled by request: “all”
The “Reseller” restore module has the following areas disabled by request: “all”
ArchiveManager
Preparing archive for restoration …
Calculating disk space needed …
Done.
Target “/home/cpanelpkgrestore.TMP.work.b2af349b/unsafe_to_read_archive” on host “server.xxxxx.top” has 3.2 TB free and requires at least 610.47 KB free, which includes space for temporary files.
This archive’s payload appears to be in the archive’s “cpmove-xxxx” directory.
ArchiveManager
The system successfully prepared the archive for restoration.
PreRestoreActions

PreRestoreActions

Account
Force Mode: no
Dedicated IP Address: yes
Account
Failed to create the account: (XID z8bp3r) The domain “cccc.com” already exists in the userdata.
Removing copied archive “/home/cpmove-xxxx.tar.gz.part00001” from the local server …
Failed: Account Restore Failed: “Account failure: Failed to create the account: (XID z8bp3r) The domain “ccccc.com” already exists in the userdata.”
 

cPRex

Jurassic Moderator
Staff member
Oct 19, 2014
16,597
2,617
363
cPanel Access Level
Root Administrator
Hey there! It looks like the partially-failed restores did create some data on the server already. The only way to workaround this would be to either create a new Destination server, or manually remove the data from the cPanel userdata files.

That manual work can be a bit tricky, so feel free to submit a ticket to our team so we can take a look at the system for you.