Why the Database Deserves Special Attention
For most business websites the database is the most valuable part: orders, enquiries, user accounts and content all live there. Files change rarely, but the database changes every day, so it needs its own backup rhythm.
Taking a Manual Dump
- Open cPanel from your client portal and click phpMyAdmin.
- Select your database in the left panel.
- Click the Export tab, keep the Quick method and SQL format, and click Go.
- Save the downloaded .sql file with a clear name including the date, for example
shopdb-2026-07-16.sql.
Alternatively, the cPanel Backup icon offers one click download of each database.
Scheduling
Match backup frequency to how fast your data changes:
- E-commerce or booking sites: daily automated backups at minimum; hourly if order volume is high.
- Company brochure sites: weekly is usually enough, plus a manual dump before any change.
- Keep a rotation: seven daily copies, four weekly copies, and three monthly copies is a solid pattern for SMBs.
CodeGuard, available from the Store menu at app.techguru.co.in, automates daily database backups with retention handled for you.
Testing a Restore
A dump you have never restored is unproven. Every quarter:
- Create a temporary database in cPanel, for example
test_restore. - Import your latest dump into it through phpMyAdmin.
- Spot check a few tables: recent orders present, row counts sensible, no import errors.
- Drop the temporary database afterwards.
Common Pitfalls
- Backing up files but forgetting the database, or the reverse. A working site needs both from the same time.
- Storing dumps inside
public_html, where they are publicly downloadable. Keep them outside the web root or download them off the server. - Ignoring dump file size suddenly shrinking, which often signals a failed backup job.
