Backups & Restore (JetBackup)

How to Restore cPanel Incremental Backups on Another Server

By the Domain India teamPublished 7 min read
Knowledge base article
Contents (7 sections)

cPanel's incremental backups are handy until you need one on a different server: they are folders, not the single archive file that restore tools expect. This guide shows how to turn an incremental account backup into a restorable archive, copy it to a new cPanel server and restore it with WHM or restorepkg, then check the result before you switch DNS.

Key takeaways

You need root on both cPanel servers. Package the account's incremental folder as USER.tar.gz (the same layout as a compressed cPanel backup), copy it to the new server, and restore it with WHM's Transfer or Restore a cPanel Account or /scripts/restorepkg. Don't create the account first: the restore creates it. On Domain India shared hosting this doesn't apply: cPanel's own backups are switched off, and your backups are made weekly by JetBackup 5, which you restore from inside cPanel.

This is for your own cPanel/WHM server

These steps need root SSH access to both servers. Domain India shared hosting customers don't have root and don't need it: use JetBackup 5 in cPanel instead, as described in Backup and restore with JetBackup.

1. What an incremental backup looks like

In WHM › Backup Configuration you choose a backup type: compressed, uncompressed or incremental.

TypeStored asMoves easily?
CompressedOne USER.tar.gz file per accountYes, restore tools read it directly
UncompressedOne USER.tar file per accountYes
IncrementalOne folder per account, updated in place, unchanged files hard-linked between runsNot directly; package it first

An incremental account folder is usually at /backup/incremental/accounts/USER/, with weekly and monthly copies in similar incremental folders if you retain them. Check the backup directory set in Backup Configuration if yours differs. Inside the folder you will find the same parts as in a compressed backup: homedir/, mysql/, mail and DNS data, and the account's settings files.

2. Before you start

  • Root SSH access to both servers, and SSH open between them.
  • cPanel/WHM on the new server, at the same or a newer version than the old one.
  • Free disk space on both servers of at least the account's size, for the archive.
  • Compatible software. Check that the PHP versions and database server the site uses are available on the new server.
  • A free username. The account username must not already exist on the new server.

3. Package the incremental folder

On the old server (or wherever the backup is stored):

bash
mkdir -p /root/migrate
cd /backup/incremental/accounts
tar -czf /root/migrate/USER.tar.gz USER
ls -lh /root/migrate/USER.tar.gz

Replace USER with the cPanel username. Running tar from the accounts folder keeps USER/ as the top-level folder inside the archive, which is what a compressed cPanel backup looks like and what the restore tools expect.

4. Copy the archive to the new server

bash
rsync -av --progress /root/migrate/USER.tar.gz root@NEW-SERVER-IP:/home/

scp works too. If you prefer to copy the folder itself instead of an archive, use rsync -aH so the hard links in the incremental folder are kept, and package it on the new server as in section 3.

5. Restore the account

You can use WHM or the command line. Both create the cPanel account from the backup, so do not create the account beforehand: the restore stops if the username already exists.

  1. WHM route.
    Log in to WHM on the new server, open Transfers › Transfer or Restore a cPanel Account, choose the archive you placed in /home (or upload it), and start the restore. WHM shows progress and any warnings.
  2. Command-line route.
    Run /scripts/restorepkg /home/USER.tar.gz. Check /scripts/restorepkg --help on your server for options such as restoring onto a specific IP address.
  3. Read the output.
    Warnings about a missing PHP version, a database collation or a DNS cluster point to exactly what needs fixing.
  4. Remove the archive
    from /home when you are done, because it contains the account's data and passwords.

If the old server is still online, WHM's Transfer Tool is often simpler: it connects to the old server over SSH and copies accounts directly, with no archive handling.

6. Check the account before switching DNS

Test the restored site on the new server before visitors reach it.

  • Preview with a hosts file entry. Point the domain at the new server's IP in your computer's hosts file and browse the site.
  • Databases. Confirm each database and database user exists and the site connects.
  • Email. Log in to webmail and check that mailboxes and forwarders came across.
  • PHP version. Check the domain's PHP version in the new server's MultiPHP Manager.
  • SSL. Let AutoSSL issue a new certificate once DNS points at the new server.
  • Cron jobs. Review them; paths may differ on the new server.

When everything works, update the domain's nameservers or A records to the new server.

7. On Domain India hosting

cPanel's own backups are off on Domain India shared hosting

On our cPanel servers, cPanel's Backup and Backup Wizard are switched off, so there are no incremental cPanel backups to restore. Backups are taken by JetBackup 5, weekly on Sunday, with the last 5 copies kept.

  • Restore on Domain India: open JetBackup 5 in cPanel and restore the whole account or just files, a database or email. See Backup and restore with JetBackup.
  • Take a copy with you: download a full account backup from JetBackup 5; see how can I download a backup of my site. Ask your new host whether they can import it, or give them your files and database exports.
  • VPS: a Domain India VPS is self-managed, and cPanel is not offered on it, so the WHM steps above apply to cPanel servers you run elsewhere.

The card shows cPanel hosting with JetBackup 5 backups included, at its live price excluding 18% GST.

cPanel Starter
₹125/mo + GST
  • 25 GB NVMe SSD Storage
  • 50 GB Monthly Bandwidth
  • 1 Website
  • 10 Email Accounts
See plan details
Can I restore a cPanel incremental backup on a different server?

Yes, with root access to both servers. Package the account's incremental folder as USER.tar.gz from inside the accounts folder, copy it to the new server, and restore it with WHM's Transfer or Restore a cPanel Account or with /scripts/restorepkg.

Where are cPanel incremental backups stored?

Usually in /backup/incremental/accounts/USER/, with weekly and monthly copies in similar incremental folders if retention is on. The exact backup directory is set in WHM under Backup Configuration.

Should I create the cPanel account on the new server before restoring?

No. The restore creates the account from the backup, and it stops if the username already exists on the new server.

Why use rsync -aH for incremental folders?

Incremental backups use hard links to avoid storing unchanged files twice. The -H option keeps those links, so the copy doesn't grow larger than necessary.

Does Domain India shared hosting use cPanel incremental backups?

No. cPanel's own Backup and Backup Wizard are switched off on Domain India cPanel servers. JetBackup 5 takes weekly backups every Sunday and keeps the last 5, which you restore or download yourself from cPanel.

Can I run restorepkg on Domain India shared hosting?

No. restorepkg needs root access to the server, which shared hosting accounts do not have. Use JetBackup 5 in cPanel to restore, or open a ticket if a restore does not work.

Ready to restore or move a site? Use JetBackup 5 in cPanel from your hosting services, read Backup and restore with JetBackup, or open a ticket if you need help.

Need help with a restore?

Tell us the domain, what you need restored and the date it last worked, and we will help you pick the right backup.

Open a support ticket

Ready when you are

Get cPanel hosting from ₹125/mo + GST

See plans

Was this article helpful?

Your answer helps us decide what to improve next.

Still need help? Open a support ticket and our team will reply.

Prefer an app? Add this site to your home screen.Get the app
Restore cPanel Incremental Backups on Another Server