How to Take a Backup of Your Website (All Methods)

What a complete backup includes

In cPanel, the Backup screen does it in one archive:

1. Open cPanel → Files → Backup (or Backup Wizard for a guided version).
2. Click 'Download a Full Account Backup' — files, databases, email configs in one tarball.
3. Choose the destination (home directory is fine) and your email for the completion notice.
4. Wait for the generation to finish, then download the archive off the server — a backup that only lives on the server it protects is half a backup.
5. Repeat on a schedule: weekly for quiet sites, daily for busy ones.

Partial backups (home directory, one database) exist for lighter needs. For WordPress, UpdraftPlus automates the same cycle to cloud storage; JetBackup, on hosts that layer it, restores from the panel in clicks. The server backup solutions page covers managed automation, and the full backup guide the strategy — 3-2-1 included.

Method 1: cPanel Backup Wizard

cPanel Backup Wizard. A backup you have never restored is a hope, not a backup. Keep a copy off the same server that hosts the site, and restore files and the database together so they match. On WebJi®, free migration of an existing site is available subject to terms and approval — open a ticket before the old host deletes the account.

Method 2: UpdraftPlus to cloud storage

UpdraftPlus to cloud storage. Use SFTP (port 22) when the host offers it; plain FTP (port 21) sends the password in the clear. The username and the path come from the hosting panel, and the remote folder for the site is usually public_html. A successful login to the wrong directory is why files upload and the site does not change.

Method 3: hosting-level JetBackup restores

How this plays out with JetBackup restores: settings that look cosmetic usually decide page speed and uptime under real traffic. The defaults WebJi® ships are tuned for Indian network conditions, and support can review your setup on request.

Scheduling and the 3-2-1 habit

Two practical notes on UpdraftPlus offsite backups: it interacts directly with caching and database response, and misconfiguration is the most common cause of 'hosting is slow' tickets. WebJi® support checks it as part of standard migrations.

Restoring step by step

How this plays out with scheduled backup cron: settings that look cosmetic usually decide page speed and uptime under real traffic. The defaults WebJi® ships are tuned for Indian network conditions, and support can review your setup on request.

Common backup mistakes

Two practical notes on 3-2-1 backup practice: it interacts directly with caching and database response, and misconfiguration is the most common cause of 'hosting is slow' tickets. WebJi® support checks it as part of standard migrations.