JetBackup: Restore One File or Table (Not the Whole Site)

Someone deleted a page, a table got mangled by a bad plugin update, or an import overwrote three months of orders — and your only backup tool is JetBackup. Good news: you almost never need to restore the whole account for problems like this. Here's how to pull back just the one file or table you actually need.

Symptom: you need one thing back, not everything

If your host runs JetBackup 5 (most cPanel servers do these days, since it replaced the older cPanel Backup and R1Soft/Acronis setups on a lot of shared and reseller boxes), you've probably seen the icon under Files → JetBackup or Backup in cPanel. The trouble starts when something breaks and the instinct is to hit the biggest, scariest "Restore" button available — the one that reverts the entire home directory or database to last night's snapshot.

That's the wrong move when the damage is small. A full restore rolls back everything in that snapshot, including the good changes made since then — new orders, fresh media uploads, that config fix from this morning. You want a scalpel, not the reset button.

Cause: JetBackup's granular tools are easy to miss

Unlike the old cPanel Backup Wizard, which mostly deals in full .tar.gz archives, JetBackup stores backups as a series of snapshots and lets you browse into them at the file, folder, or table level. The catch is that this lives in a separate manager from the "one-click restore whole account" button, and it's not always obvious it's there. If your host disabled some feature-manager icons for your account, you might not see JetBackup at all in cPanel — in that case the account-level restore has to be requested from support instead.

The other common cause of confusion: incremental snapshots. JetBackup doesn't necessarily keep a full standalone copy for every restore point. Recent snapshots are often built from a base copy plus incremental changes, so restoring from a point three weeks back can take noticeably longer than restoring from last night, even though the interface looks the same either way.

Fix: restore just the file, folder, or table you need

1. Restoring a single file or folder

In cPanel, open Files → JetBackup (or just "Backups", depending on how your host branded it) and go to Home Directory Restoration Manager.

1. Pick a snapshot from the list — each one is timestamped, so choose the point right before things went wrong.
2. Browse into the file tree the same way you would in File Manager. You can drill straight into public_html/wp-content/themes/ or wherever the broken file lives.
3. Select the specific file or folder (not the parent directory, unless you actually need the whole thing back).
4. Choose Restore. You'll usually get two options: restore it back to its original location, or download it as a .zip so you can inspect it first before overwriting anything live.

Downloading first is the safer habit, especially if you're not 100% sure which snapshot has the good version. Unzip it locally, diff it against the current file, then copy it back over SFTP once you've confirmed it's right.

2. Restoring a single database or table

For MySQL/MariaDB, use MySQL Restoration Manager instead. This is the one that saves you when a plugin update mangles the wp_options table or an import script truncates wp_posts.

1. Select the database from the snapshot list.
2. JetBackup will show the individual tables inside that backup — pick just the one you need.
3. Restore in place, or download the .sql dump if you want to review it in phpMyAdmin first.

If you're not sure which table is actually broken, download the whole database dump instead of restoring blind, then open it locally (or in phpMyAdmin's "Import" preview) to compare row counts and timestamps against the live site.

3. When you genuinely need the full account back

Full restores make sense after a hack, a botched migration, or when the account itself is corrupted — not for "I deleted one image." If you do need it, JetBackup's full restore still gives you a choice between restoring files, databases, email, and DNS zones independently, so you can, for example, restore the home directory without touching email accounts that are working fine. Check those boxes deliberately instead of accepting every option by default.

4. If the restore button is missing or greyed out

A few things cause this on shared or reseller accounts:

• Your plan's feature list doesn't include JetBackup's restoration manager — ask your host to enable it or pull the file for you.
• The snapshot destination is a remote location (S3, an FTP server, Backblaze B2) that's temporarily unreachable — check WHM → JetBackup 5 → Destinations if you have root, or ask your host to verify connectivity.
• The backup job is still mid-run. JetBackup won't let you restore from a snapshot that hasn't finished writing yet.

Prevention: make the next restore boring

A few settings turn "panicked 2am restore" into a five-minute task:

If you're on Getwebup hosting and don't see JetBackup's granular restore options in your cPanel, open a ticket — we can either enable the feature on your account or pull the specific file or table for you from the server-side snapshot directly.