What this guide helps you do
Learn what a complete website backup actually contains and how to avoid restoring only half of an application. A useful website backup must match the application architecture. A WordPress site typically needs files and a MySQL/MariaDB database; a custom application may also depend on environment values, cron schedules, mail routing, DNS and uploaded media outside the obvious web root. Downloading public_html alone is often not a complete recovery package. This guide is written for production-minded administrators and site owners: make a backup before material changes, keep credentials private, and prefer the controls supplied by your own hosting provider when its environment differs from a generic example.
Before you begin
Record the domain, server or station you are changing and the current working state. If the task touches DNS, SSH, firewall rules, databases, stream credentials or application configuration, make sure you have a recovery path first. Screens and menu names can vary between cPanel, AzuraCast, VDO Panel and Linux releases, so follow the purpose of each step rather than forcing an old screenshot onto a newer version.
Step 1: Identify the site document root in Domains and note any storage directories outside it. In File Manager, create or download an archive only if account resource limits allow it.
Identify the site document root in Domains and note any storage directories outside it. In File Manager, create or download an archive only if account resource limits allow it.
Step 2: Export the correct database using the provider-supported backup feature or phpMyAdmin. Record which database belongs to which application rather than naming files backup1.sql with no context.
Export the correct database using the provider-supported backup feature or phpMyAdmin. Record which database belongs to which application rather than naming files backup1.sql with no context.
Step 3: Document runtime dependencies: PHP version, required extensions, cron jobs, DNS records, email routing and any application configuration stored outside version control.
Document runtime dependencies: PHP version, required extensions, cron jobs, DNS records, email routing and any application configuration stored outside version control.
Step 4: Store at least one backup copy away from the same hosting account. An account compromise or storage failure should not be able to remove both production and every recovery copy.
Store at least one backup copy away from the same hosting account. An account compromise or storage failure should not be able to remove both production and every recovery copy.
Step 5: Test restoration on staging or a temporary environment when possible. A restore test catches missing files, wrong database credentials, encoding problems and forgotten dependencies before an emergency.
Test restoration on staging or a temporary environment when possible. A restore test catches missing files, wrong database credentials, encoding problems and forgotten dependencies before an emergency.
Verification checklist
A complete recovery set should identify the date, domain, file archive, database export, important runtime settings and restore instructions. Verify that archives open and database exports contain expected tables. Always test from the user side as well as the administrator side. A control panel saying “active” is useful evidence, but it is not the same as an external browser, player or SSH client proving that the full path works.
Troubleshooting method
When the result is not what you expected, avoid changing several unrelated settings at once. Identify the last known-good point, collect the exact error message and determine which layer is failing: DNS, network, authentication, service process, application configuration, web/stream delivery or browser/player. Check timestamps and logs around the failure. If you need to escalate to hosting support, include the affected hostname or station, the time of the test, what you expected, what happened instead and the checks you already completed. Do not include passwords, API keys or private stream keys in a public ticket or screenshot.
Keep the system maintainable
Document the final configuration after it works. Note the important URLs, service names, backup locations, renewal/expiry dependencies and any change that would surprise another administrator. Revisit the setup after major platform upgrades because defaults, supported runtimes and interface labels evolve. A reliable environment is not one that was configured once; it is one whose current state is understood, monitored and recoverable.
Where to go next
Use the related guides below to expand the setup rather than solving the same problem from scratch. If the platform has outgrown shared hosting or you need managed implementation, the service recommendation at the bottom of this guide links to the most relevant hosting, streaming, development or optimisation option on this site.
Interface labels and supported versions can change. Use the controls and documentation supplied with your current hosting environment, and keep a backup or recovery path before material changes.