Backup and Restore FAQ

You can import all of your user accounts from another InterWorx-CP server or a cPanel 10, Plesk 7.5 or Ensim 4 server. This is an import of all SiteWorx accounts and does NOT include NodeWorx data such as packages, and bandwidth history.

Not precisely, but you will have the best results if the versions of all of your services (especially MySQL) are the same.

No, you will encounter problems with restoring your databases if you do this. Or, to put it simply, “things will break.”

For example your old host has MySQL 4.1 and the InterWorx box has 3.3 (the default for CentOS 3.x), it will not work correctly because MySQL 4 has some differences in the table format that 3.x won’t understand.

If this is the case you should locate and install updated RPM‘s before trying to import your site.

Yes, going from MySQL 3 to MySQL 4 and higher should be fine.

Yes, the restore script uses the same SiteWorx user name as the original account.

If the old box did not have the Jailed Shells installed/enabled and the new one does then the actual path to your files will change from /home/<siteworxuser> to /chroot/home/<siteworxuser> but since /home is symlinked to /chroot/home you will not have any problems.

One possible problem is that the unique SiteWorx user name (e.g. /home/<siteworxuser> ) from the old box is not available on the new one. Since the SiteWorx importer/restore is dependent on using the original name, this issue must be resolved before you proceed..

Another problem could be your MySQL version. If your old server was running MySQL 4 and the new one only has MySQL 3, your databases and/or users will probably not be imported.

Yes, any backup files stored in /home/<siteworxuser>/backup are deleted when an account is deleted.

The difference between a backup containing all three types of partial backups and a complete backup is that the partial archive only contains your web data, databases, and email, and a way to restore them. A Complete backup contains enough data to restore ALL of the settings on your account. The partial backup can only be used from within an existing SiteWorx account. A Complete backup can be used from NodeWorx to re-create the entire SiteWorx account.

No, the Complete backup can ONLY be used by the NodeWorx user (Administrator or Reseller) to re-create a complete SiteWorx account.

No. Only a Complete backup contains enough data to restore ALL of the settings on your account. The partial backup can only be used from within an existing SiteWorx account. A Complete backup must be used from NodeWorx to re-create the entire SiteWorx account.

Any data in the existing SiteWorx account is destroyed. Make sure to make backups of anything you want to keep.

Your backup files are stored in the

  /home/siteworxuser/backup

directory by default. InterWorx 2.x also allows you to specify an alternative backup location at the time of backup creation/scheduling.

Yes, since the files are owned by the <siteworxuser> group, they count toward your quota whether they are created from SiteWorx or NodeWorx.

Yes, since the files are owned by the <siteworxuser> group, they count toward your quota whether they are created from SiteWorx or NodeWorx.

The only way around this is for the NodeWorx user to move the file and change it’s permissions OR to store them on a different physical disk partition.

The backup files are .tar.gz files (as opposed to .zip files) because the .tar compression format preserves file permissions. This is necessary if you want the backup to work when it is restored. Tar is a packaging format, not really a compression, so GZip (.gz) is used to shrink the file even further.

If for some reason you need to decompress the archive manually use the following command set

  gunzip <filename>

  tar -xf <filename>

If the backup file is too big for your internet connection to handle through http, try loging into ftp and downloading it that way. The backup files are stored in

  /home/<siteworxuser>/<domain>/iworx-backup

by default.

If you have a local backup file on your hard drive that is very large, InterWorx won’t let you upload it via the browser due to file size restrictions and PHP or Apache timeouts. If you try to upload it, you will get an error message indicating you should upload the file with another method (for example, FTP or SCP) and use the remote backup file option instead.

You can upload it anywhere in the file system but it is best to upload it to the default location of

  /home/<siteworxuser>/<domain>/iworx-backup

Each website owner will need to find a backup plan that works for them.

Don’t forget to go in and manually remove older backup files unless you have a lot of space to burn. Currently InterWorx does not do this for you.

No, you must go in and delete backup files manually or or write a ssh script to do it for you.

You can do this either from the Backup Management screen in NodeWorx

NodeWorx => SiteWorx => Backup/Restore => Manage (link next to the correct domain) => Check the box(es) next to the backup(s) you want to delete => Select Delete from the “With Selected” pull down menu under the backup list

Or SiteWorx

SiteWorx => Backup/Restore => Restore => Check the box(es) next to the backup(s) you want to delete => Select Delete from the “With Selected” pull down menu under the backup list

or from ssh. You will need to navigate to

  /home/<siteworxuser>/<domain>/iworx-backup

and use the command rm <filename>

For more specific instructions, please view the official Backup/Restore docs.

Yes, InterWorx-CP 2.1 and later has a mass importer for InterWorx-CP and cPanel. Mass importers for the other panels supported by the single account importer script are also planned for a future release. The software connects to the other server, directs it to make a backup of every account, transfers the native backup files to the new box and imports them.

The software connects to the other server, directs it to make a backup of every account, transfers the account to the new box and imports it.

For more specific information, please view the official Backup/Restore docs.

  Archive file : /mysite.com_aug.24.2005-00.44.29.tar.gz
  » Working directory : /tmp/siteworximport9DF59D
  » Archive extracted successfully
  » Could not extract data archive. Wrong backup type? : /tmp/siteworximport9DF59D/mysite.com_aug.24.2005-00.44.29.data.tar.gz

First make sure you selected the correct backup type on the import page. Double check to make sure.

If that’s not it, how big is the archive file? How big does the .tar.gz expand do.

How big is the /tmp partition on your server?

You need enough free /tmp space for roughly twice the size of the SiteWorx account in order for the import to be successful.

Here’s the problem I had:

My data center put the /tmp directory in it’s own partition and only made it 500 MB

The .tar.gz backup I was working with was 390mb and expanded to 580mb. That caused the errors above.

The workaround was

  mkdir /home/tmp

  chmod 776 /home/tmp

because /home tends to be in the largest partition

then

  vi /home/interworx/iworx.ini

locate

  [dir]
  cron="/var/spool/cron"
  mysql_base="/var/lib/mysql"
  skel="/etc/skel"
  sysconf="/etc"
  tmp="/tmp"

change tmp=”/tmp” to tmp=”/home/tmp”

save the file

  service iworx restart

just in case, but it should work without it.

  no cron for myuser

You are getting this message because you are backing up a SiteWorx account that has been given access to cron but the backup script is not finding cron files for that user. Most likely this is just because the user has never actually used cron before. Unless you know that the user has set a cron before you can safely ignore this message.

First run a quota check

  quotacheck -cugvmf -F vfsv0 /  [ If your home directory is in your root partition ]

  quotacheck -cugvmf -F vfsv0 /home [ if the /home directory is also a partition ]

  quotacheck -cugvmf -F vfsv0 /chroot [ if you are set up for jailed shells and the /chroot directory is also a disk partition ]

Then run:

  ~iworx/cron/storage.pex

Your quotas should be correct now

No, you can do a restore of databases, web data, email, or any combination of the three, but a full restore is ONLY possible from NodeWorx.

No, you can use the shell backup command below to back up a coma separated list of domains but you can not just tell it to skip certain ones. You need to specify the ones you want backed up and that list can be as long as you need.

/home/interworx/bin/backup.pex --domains=domain1,domain2,domain4,etc --file-path=”/home/backups”

For more info on creating a SiteWorx backups from the shell, please visit visit this How-To.