Open the website's Backups section and check the provider-supported website backup actions. Review any Automatic backups supplied by an available JetBackup 5 integration separately. A full hosting account backup is another distinct archive and does not have a universal restore button in the module's account tools.

Document whether the plan protects WordPress files, the database, email, DNS settings or the entire hosting account. Do not infer full account protection from the presence of a website backup control.

1. Open the correct website and confirm its domain and installation path.
2. Check available disk space and the supported backup destination before starting a backup.
3. Create the backup through the supported website action. Wait for a completed result and refresh the list if necessary.
4. Record the backup time and scope. A list entry or task submission alone should not be your only restore assurance.
5. Test restoration on a safe test website or through a controlled recovery exercise that cannot overwrite production unexpectedly.
6. Verify the restored files, database, login and important application functions.

The website automation workflow supports a configurable automatic backup retention count. That retention applies to its automatic website backups, not every manual or server-managed backup. Check the server backup system's own retention and off-server storage policy separately.

Backups kept only inside the same hosting account can be affected by account loss, quota problems or a wider server incident. Match your actual storage and recovery arrangements to the service you advertise.

Identify what has changed since the selected recovery point. Restoring an older database can remove newer orders, users, form entries or other records. Take a fresh copy of the current state when practical and obtain the appropriate operational authorisation for the specific restore.

After restoration, test the public site and administrative access, then check integrations and scheduled activity. Explain any expected loss of recent data to the customer.

Check the product tools, server integration, package permissions and the selected website. Optional server backup software must be installed and accessible. Escalate a missing or failed backup with its safe job details; do not describe an unverified backup as usable simply because the hosting plan includes a backup feature.

• Configure scheduled WordPress maintenance and verify its history
• Set a WordPress update policy and validate changes in staging
• Enable optional website insights, malware and performance tools
• Set safe operating expectations for AI changes and Undo

• cPanel: manage WordPress with WP Toolkit