“The host makes backups” is a good starting point, but ask for details. You need to know which date you can restore the website to, what the backup contains and who starts restoration. Establish this before an update or a change of developer.
You do not need to operate every tool yourself. You should know where the information is and who is responsible for doing the work.
Files and the database belong together
On a typical WordPress website, files include the theme, plugins and uploaded images. Content and settings are also stored in the database. Downloading the website directory does not automatically back up that database. WordPress documentation explains that both parts are needed to fully restore a typical website. WordPress on backups.
When checking a backup, ask about coverage, not just the service name. Establish the business email arrangements separately. Do not assume a website backup includes mailboxes at another provider.
Ask the provider specific questions
Keep a short note of the answers:
- Does the backup include the correct website’s files and database?
- How often is it made and how long do earlier versions remain available?
- Where is it stored and who can access it?
- How is restoration requested, and what is needed to perform it?
- Who in the business can approve the operation?
- Can restoration be tested safely away from the live website?
Retention means how long backups are kept. Compare that with when your business might notice a problem. If an error emerges later, the latest backup may already contain it.
Do not add a guaranteed repair time to your notes unless the provider has agreed one. Record the actual service terms and how to report a problem.
Make a backup before a significant change
Learn WordPress recommends backups before updates, migration and major changes. It also recommends storage away from the website’s server. Backup lesson.
Add to the work plan who is responsible for the backup and for deciding whether to reverse a change. Agree what happens to content added after the backup. This matters especially for websites accepting orders or other submissions.
Test restoration in an agreed environment
We suggest testing in a separate environment with an agreed responsible person. Checks should cover what matters to the business: content, images, editing and agreed features.
A backup may contain personal data and confidential settings. A test environment should not expose them publicly or send real notifications to customers. Agree access, sending and copy-deletion rules before the test.
After testing, record what was checked, the limitations and who approved the result. If no test was performed, the documentation should say so clearly.
When taking over and organising a website , CyberKlucz can include backups and a restoration plan within the agreed scope. Start with information about the provider and current backup terms.
