Backups exist for the day something goes wrong: a bad plugin update, a deleted page, a corrupted database, or a security incident. Knowing how they work before that day is the point of this article.
What is backed up
A complete backup of a website has two halves, and both are required for a working restore:
- Files. Themes, plugins, uploaded images and documents, and application code.
- Database. Pages, posts, products, orders, users, settings and form entries. Almost everything you think of as "the content" lives here.
Schedule and retention
Backups run automatically on the schedule stated on your hosting plan, and copies are retained for the period stated there. Retention is finite, which matters: a fault you only notice three months later may fall outside the window. Check things after major changes rather than assuming you can always roll back.
Requesting a restore
Raise a ticket at crm.zylax.com.my and include:
- The date and, if you know it, the time you want restored to. Pick a point you are confident was healthy.
- Whether you want files, database or both.
- Whether you want a full restore over the live site, or the backup placed in a staging copy so you can extract one item.
Restores overwrite things
A full database restore removes everything created after the backup point. On an e-commerce site that means orders. On a site with a contact form it means enquiries. Always tell us if the site has taken transactions since the backup point, and we will take a fresh backup first and plan the merge instead of blindly overwriting.
Keep your own copy
For anything critical, keep an independent copy outside our infrastructure. We can provide a downloadable archive on request. Storing a copy of your own is good practice regardless of who your host is.
To request a restore or a downloadable backup, reply to your email thread or contact [email protected].
