How to Restore a Backup with HostGator's Built-In Backup Tool
HostGator takes snapshots of customer websites on a rolling schedule, and many site owners in Australia only discover this feature after a plugin update goes sideways or a malicious script wipes out a folder. The built-in restore tool sits inside cPanel and pulls from those snapshots, so you do not have to keep your own copies on a local machine. For anyone running a small business site, a portfolio, or a WooCommerce shop from Sydney or Brisbane, the difference between a 15-minute recovery and a multi-day scramble often comes down to knowing where the restore option actually lives.
The HostGator interface has shifted over the years, and the current build runs on JetBackup, which gives you daily, weekly, and monthly restore points stretching back roughly 30 days on most shared plans. If you have never used it before, the first restore can feel confusing because the screens look similar to the file manager but behave quite differently. This walkthrough covers what the tool does, how to run it safely on a typical Australian NBN connection, and what to do if the restore stalls or returns errors partway through.
Understanding HostGator's Backup and Restore Options
The backup tool inside your HostGator account works in two directions. It writes copies of your home directory, MySQL databases, and email forwarders to a hidden server-side vault, and it lets you pull those copies back into your live account through a dedicated restore interface. You will find the vault under the JetBackup icon inside cPanel, while the older Backup icon, often labelled Legacy Backups, still appears on accounts created before 2020. If you are weighing up HostGator against other Australian-friendly providers, reading recent HostGator reviews gives a realistic picture of how the backup system holds up under real load.
Most shared and reseller plans include 7-day or 30-day retention. Managed WordPress and VPS customers get longer windows, sometimes up to 90 days for weekly snapshots, and the daily quota is usually capped at a few hundred gigabytes of compressed data. If your site sits on a starter Hatchling plan and regularly exceeds 5 GB, expect only daily snapshots to survive beyond a week. The retention policy is not negotiable through the dashboard; you negotiate it indirectly by upgrading or by maintaining your own off-server copies.
One thing many Australian customers miss is that the backups are stored in HostGator's US-based data centres, which affects how long a large download takes to complete. A 4 GB archive being pulled over a 50/20 Mbps NBN connection in Perth can take 10-15 minutes of solid throughput, and any throttling on your local link will push that window longer. Plan to start a restore when you can leave the browser tab open and the connection idle.
Preparing for the Restore Before You Click Anything
Before you touch the restore button, take a few minutes to capture the current state of the site. A restore overwrites files and databases in place, so anything that exists now but did not exist in the snapshot will be lost. The simplest safety net is to download a fresh copy of what is live today, using either cPanel's file manager or an FTP client, and to export your current databases through phpMyAdmin.
Next, decide which restore point you actually need. JetBackup lists snapshots in reverse chronological order, with a timestamp in your local browser timezone. From Adelaide to Hobart, that usually means ACDT, AEST, or AEDT depending on the time of year. Pick the newest snapshot that predates whatever broke the site. If a botched theme update happened at 9 pm on a Tuesday, a Wednesday morning snapshot is the cleanest target.
You should also clear your browser cache and confirm that no cron jobs or scheduled posts are about to fire during the restore window. WordPress sites in particular will keep running wp-cron.php in the background, and a half-restored database can produce very strange behaviour if a cron fires mid-process. If you cannot pause cron, at least put the site into maintenance mode using a plugin, or rename .htaccess to .htaccess.bak before kicking off the restore.
Running the Restore Through JetBackup in cPanel
Open cPanel and scroll to the Files section. Click the JetBackup icon, then choose Full Account Backups or File Manager Backups depending on whether you want to bring everything back at once or just a single folder. For most recovery jobs, the File Manager restore is the safer choice because it lets you pick exactly which paths to overwrite, rather than nuking the entire home directory.
Select a restore point from the calendar view on the left. The icons next to each date show which items are available: full backups, database-only, email-only, or partial. Click the date you prepared earlier, then choose Restore Files and a destination. Tick the directories you want brought back, for example public_html/wp-content, and untick anything you want to keep untouched. Confirm the selection, and the restore will queue.
For database restores, switch to the Database Backups tab inside JetBackup. Pick the snapshot date, select the database name, and click Restore. The tool drops the existing tables, imports the SQL file, and returns a success or failure message. Database restores are usually faster than file restores, but they trigger a brief window where the site will return an Error establishing a database connection message. Schedule this for low-traffic hours, ideally between 1 am and 5 am AEST, to minimise the impact on Australian visitors.
After the restore completes, re-check file permissions on key directories. HostGator's defaults put folders at 755 and files at 644, and a restore can occasionally leave uploaded images at 700 if they came from a custom upload script. Run a quick spot check on the wp-content/uploads folder, then flush any caching plugin you have running, and clear your CDN edge cache if you use Cloudflare or a similar service.
What Goes Wrong on Australian Connections
A restore that runs cleanly on a Dallas data centre can stumble when the user sits behind a flaky NBN connection in regional Queensland. The most common complaint is the restore spinning forever without an error message. This is almost always a session timeout on the cPanel side rather than a server problem. cPanel logs you out after roughly 15 minutes of inactivity, and a multi-gigabyte restore can easily exceed that window if you have a slow upstream link.
To work around this, restore in smaller chunks. Instead of bringing back the whole public_html directory, restore one folder at a time, for example public_html/wp-content/plugins first, then public_html/wp-content/themes. Each chunk finishes in under 10 minutes on most Australian NBN plans, and you can leave the browser alone without being kicked out.
Another frequent issue is timezone confusion. JetBackup lists snapshots in server time, which is US Central, so a snapshot dated 2024-03-15 may have been taken at 2 am on the 16th in Sydney. Always cross-reference with your own activity log before picking a date. Restoring the wrong snapshot is the most common reason customers end up with a site that is technically up but missing the last few hours of content.
If the restore keeps failing outright, the cause is corrupted archive files rather than a network problem. JetBackup will still queue the request, but the import will halt partway through. In that situation, open a ticket with HostGator support through your client portal and ask them to verify the integrity of the snapshot on their end. Mention the snapshot date and the directory you tried to restore, and they will either confirm the file is healthy or point you to a different restore point that is.
Choosing Between Self-Service Restore and a Support Ticket Restore
The self-service restore through JetBackup is the fastest route for most situations, but there are cases where a support ticket restore is the better call. The comparison below breaks down the two approaches on the factors that matter most for Australian customers managing their own accounts.
| Factor | Self-Service JetBackup Restore | Support Ticket Restore |
|---|---|---|
| Typical turnaround | 5 to 30 minutes | 4 to 24 hours |
| Best for | Single folders, databases, recent breakage | Full account wipe, corrupted archives, VPS |
| User control over which files to restore | Yes, granular selection | No, broad request |
| Risk of accidental overwrite | Moderate (user picks the wrong date) | Lower (handled by engineer) |
| Cost on shared plans | Included | Included |
| Cost on VPS or dedicated | Included | Often billable hourly |
| Works during peak AEST hours | Yes, but risky on slow links | Queue position may delay it |
| Need to leave browser tab open | Yes | No |
For most everyday recoveries, the self-service path is the right choice. For a full account migration, a site that has been defaced, or any restore that involves restoring email, opening a ticket is usually quicker than fighting through the cPanel interface for an hour.
Once your site is back up and behaving the way it did before the breakage, take twenty minutes to set up an off-site backup routine. The free version of UpdraftPlus, or a simple cron job that pushes a daily archive to an Australian-based object store such as Wasabi's Sydney endpoint or a Backblaze B2 bucket, closes the loop and means you never have to rely solely on HostGator's snapshot retention again. If, after getting your data back, you decide that HostGator is no longer the right home for the project, the step-by-step walkthrough on cancelling a HostGator account covers the close-out process in plain English, starting with the exact menu path inside the billing portal. Schedule that first daily off-site archive job tonight so the snapshot is sitting safely in your bucket before you go to bed.