Why Backups Matter
Hardware fails. Updates go wrong. Accidental deletes happen. A LiteShoper store holds product catalog, customer orders, plugin configurations for shopee-sync and easyparcel, and theme customizations on obsidian or breeze. Without backups, recovery means rebuilding from scratch—lost revenue and trust.
What to Back Up
| Component | Contains | Priority |
|---|---|---|
| Database | Products, orders, customers, settings | Critical—daily |
| Uploaded files | Product images, downloads, media | Critical—daily |
| Plugin config | API keys, sync mappings, email templates | High—after changes |
| Theme customizations | Customizer settings, custom CSS | Medium—weekly |
| License records | Marketplace purchase proofs | Medium—export from account |
Backup Schedule Recommendations
- Daily automated: Database and uploads for active stores
- Before updates: Full snapshot before LiteShoper core or plugin updates
- Before theme switch: Customizer export and database
- Monthly offsite: Copy backups to different cloud provider or physical drive
- Peak season: Increase frequency during 11.11 and campaign weeks
Backup Methods
- Hosting panel: Many XAMPP/production hosts offer scheduled MySQL dumps and file archives.
- LiteShoper export tools: Use built-in product/order CSV export for partial redundancy—see docs.
- Plugin-assisted: Backup plugins if available on marketplace—verify restore tested.
- Manual mysqldump: Developers run scheduled cron jobs dumping database to secure storage.
- File sync: rsync or cloud sync for uploads directory—exclude cache folders.
- Document API keys separately: liteshop-api, seo-ai, payment gateways—encrypted password manager.
What Not to Rely On
Marketplace plugin licenses re-download from your account—but license alone does not restore product data. liteshop-dropship supplier mappings live in your database. Shopee connection tokens need re-auth even after restore—plan reconnection steps.
Restore Testing
Untested backups are hope, not strategy. Quarterly, restore to staging environment. Verify orders, images, and checkout with liteshop-stripe test mode work. Document restore procedure for team members.
Disaster Scenarios
| Event | Recovery Path |
|---|---|
| Corrupted database | Restore last clean nightly dump |
| Ransomware on server | Offsite backup from before infection |
| Bad plugin update | Restore pre-update snapshot; deactivate plugin |
| Accidental mass delete | Point-in-time backup or partial CSV reimport |
| Hosting provider loss | Deploy fresh LiteShoper plus latest offsite backup |
Security of Backups
Backups contain customer PII—encrypt at rest. Restrict access credentials. Comply with Malaysia PDPA for stored personal data. Do not leave unencrypted dumps on public S3 buckets.
Plugin-Specific Notes
After restore, revalidate: shopee-sync and tiktok-sync tokens, easyparcel API key, liteshop-bulk-email SMTP, liteshop-tawk property ID, liteshop-telegram bot webhook URL. These may need re-saving or OAuth refresh.
Terms and Support
Backup responsibility typically lies with store owner per hosting agreements. Review terms for platform-specific guidance.
Conclusion
Automate daily database and file backups, store copies offsite, test restores regularly. Your future self—recovering from one bad update—will thank you.