Import

How-To:

• Import a Single Account
  • via NodeWorx
  • via CLI
• Import Multiple Accounts From a Remote Server

If you prefer to use the web interface, follow the steps below.

1. Click the SiteWorx menu item if it is not already open.
2. Click the Import menu item.
3. Click the radio button next to Local Backup File or the radio button next to Remote Backup File.
   1. Choose Local Backup File if you have a backup file saved on your computer's hard drive. Click the Browse button and choose the backup file.
   2. Choose Remote Backup File if you have a backup file saved on the server. You will need to type in the fully-qualified path to the file. For example, if you have a backup file named testaccount.tar.gz in /tmp/backups/, you would enter: /tmp/backups/testaccount.tar.gz
4. Choose the control panel from which this backup was created from the dropdown labeled Control Panel Type. For example, choose InterWorx Control Panel (all) if this backup was created by InterWorx Control Panel.
5. Choose from the list of available resellers in the dropdown labeled Reseller
6. Choose from the list of available IP addresses in the dropdown labeled IP Address.
7. Click the Import button.
8. If there is already an existing SiteWorx account with the same domain name you will be asked to confirm. Click the Import button to finish.

The command line backup interface is less user-friendly, but you have a lot more options at your disposal. Using the command line interface is most useful when you want to automate (e.g., via CRON) the creation of SiteWorx account backups.

1. SSH into the server
2. su to the iworx system user. You may need to switch to the root user first (if you're not already logged in as the root user) and then switch to the iworx user.

The command you will be running is, as the iworx user:

[iworx@test-box ~]$ /home/interworx/bin/import.pex

import.pex has several command line parameters:

The usage of the import command can be reviewed by running import.pex without parameters.

To restore SiteWorx backup file /tmp/backup.tar.gz with a prompt to confirm deletion of the existing SiteWorx account:

[iworx@test-box ~]$ /home/interworx/bin/import.pex \
                    --archive=/tmp/backup.tar.gz \
                    --control-panel=siteworx \
                    --ip-address=inifile

To restore SiteWorx backup file /tmp/backup.tar.gz without a prompt to confirm deletion of the existing SiteWorx account:

[iworx@test-box ~]$ /home/interworx/bin/import.pex \
                    --archive=/tmp/backup.tar.gz \
                    --control-panel=siteworx \
                    --ip-address=inifile \
                    --force

1. Click the SiteWorx menu item if it is not already open.
2. Click the Import menu item.
3. Click the Import Mass Transfer button
4. In the Hostname: field, enter the hostname of the remote server from which you want to migrate.
5. In the Root User: field, enter the root user of the remote server from which you want to migrate.
6. In the Password: field, enter the password for the root user you entered above.
7. Click the Query Accounts button.
8. You will now see a list of accounts on the remote server, with a checkbox next to each account.
   
   Note: If the remote server also has InterWorx 3.0 installed, the list of accounts will be grouped by resellers.
9. Mark the checkboxes next to accounts you would like to migrate.
10. Select the destination Reseller you want to use for each migrated account from the Reseller column. If the remote server also has InterWorx 3.0 installed, and the remote reseller doesn't already exist on the destination server, you will have the option to import the remote reseller. If the reseller in the backup file already exists, the account will automatically be imported under this reseller.
11. Select the IP Address you want to use for each migrated account from the IP Address column.
12. There are also "Advanced Options" dropdowns at the top of each group of accounts, allowing you to quickly and easily set options for all the accounts in the list. For example, choosing an IP Address in the Advanced Options section will select that IP for all accounts.
13. If the remote server also has InterWorx 3.0 installed, there will be a few more options available.
    1. A Storage Used column will appear, indicating the approximate amount of disk space the account is using on the remote server.
    2. A Type option will appear for each account, allowing you to choose either a "Full Import" or "Structure-Only Import". Structure-only imports are much smaller and faster than full imports, but only import SiteWorx account related information (such as quotas, usernames, passwords, etc) and not actual data (such as website data files, database data, and email files). Structure-only is especially useful when mass-transferring large accounts, since large accounts can take a considerable amount of time to mass-transfer.
14. Select Import … from the drop-down list at the bottom of the table.
15. You will now see a list of the accounts you chose to mass transfer, along with a status for each account under the Import Status column.
    1. In Progress - Account is currently being backed up, transferred over from the remote server, and imported into InterWorx Control Panel.
    2. Pending - Account is waiting for import process to begin.
    3. Success - Import of account succeeded.
    4. Failure - Import of account failed. A message that indicates possible reasons for failure will appear beneath the Failure box.
16. The page will automatically reload after a certain interval to update the import status of each account.
17. When the mass transfer process is complete, all accounts will either have a Success or Failure status in the Import Status column.

If you get a Permission Denied error after clicking the Query Accounts button on the first Mass Account Transfer page, check the following:

1. You have entered the correct root password.
2. You have entered the correct root username.
3. Double check that the remote server allows the root user to SSH in. You can verify this by trying to SSH into the remote server as the root user.