Symptoms
When trying to restore a package with an Add-on domain as a primary domain that is parked under a sub-domain, you get a restore error.
Description
When restoring a package with a user's primary domain parked under a subdomain, the following may occur in the restore log:
[ 24340][RESTORE:1 ][A:myuser ]: Warning (“Homedir::restricted_restore”, line 130): This account archive contains no home directory files to restore.
[ 24340][RESTORE:1 ][A:myuser ]: Warning (“Domains::restricted_restore”, line 130): (XID hh94kv) The domain “myprimary.local” does not exist in the userdata for the user “myuser”.
[ 24340][RESTORE:1 ][A:myuser ]: Warning (“Domains::restricted_restore”, line 130): Restoration of “submyaddon.local” will be skipped because it requires that “submyaddon.sub.myprimary.local” be created before it can be restored.
[ 24340][RESTORE:1 ][A:myuser ]: Warning (“Domains::restricted_restore”, line 130): Prerequisite domain, “submyaddon.sub.myprimary.local” is not referenced in the restore file and does not preexist.
[ 24340][RESTORE:1 ][A:myuser ]: Skipped item (“Domains::restricted_restore”, line 130): Failed to restore the domain “submyaddon.local”: Restoration of “submyaddon.local” will be skipped because it requires that “submyaddon.sub.myprimary.local” be created before it can be restored.
[ 24340][RESTORE:1 ][A:myuser ]: Skipped item (“Domains::restricted_restore”, line 130): Failed to restore the domain “submyaddon.sub.myprimary.local”: (XID hh94kv) The domain “myprimary.local” does not exist in the userdata for the user “myuser”.
Answer
Because the primary domain was not restored first, this error message is produced. To work around this, you can use /scripts/restorepkg --force /path/to/backup, or if the account already exists, you can use /scripts/restorepkg --skipaccount /path/to/backup