Create a recoverable checkpoint before an AI website deployment Print

Quick answer

Keep the previous files, relevant database backup, configuration, and a record of the target before a deployment. A Git commit protects tracked source, but it does not automatically protect uploaded media, secrets, live orders, or database changes.

Apply this guidance to your website task

• Understand Nova history and hosting backup limits
• Plan selective WordPress recovery

Before you start

Identify what the task can affect and how the website is currently backed up. Check available storage and access to the recovery copy. Keep sensitive archives outside the public document root.

What to do

1. Capture the current live version immediately before release and record the domain, document root, database, timestamp, and source version.
2. Back up the relevant files and database using the supported account tools or backup service. Record whether the backup includes media, configuration, mail, or only part of the application.
3. Verify that the archive is readable and complete enough to restore the change. Store a copy independently of the site when practical.
4. Write the selective rollback steps and decide how newer live data would be preserved. For a code-only release, prefer restoring changed files over replacing the whole database.

Check the result

The checkpoint should have an inventory, byte sizes or hashes, and a known restore path. A completed backup notification alone is weaker evidence than a tested recovery process.

If something does not work

If a backup fails or the destination is full, do not continue with an irreversible deployment. Ask support for the appropriate recovery option and avoid creating large public downloads containing credentials.

Related help

• Check that a WordPress backup includes files and database
• Test a website restore without replacing the live site
• Store website backups outside public web access

Official references

• cPanel Backup
• Git documentation

Reviewed October 31, 2026. Interfaces, vendor availability, and account features can change. Check your current account before making changes.

AI editing guidance and linked workflow documentation reviewed November 2, 2026. Existing video and earlier review history retained.