A backup is useful only if it contains the required data and can be restored within a practical process. Website files alone may not include database content, mailbox messages, scheduled tasks or DNS settings. Start by identifying which components are needed to rebuild the service, and record the tools and access required for recovery.
Recommended workflow
- Include the required files, database exports and configuration information, using a consistent point in time where possible.
- Confirm that the archive can be opened and that encryption or access keys are available to the authorized recovery owner.
- Run a representative restore test and document any manual steps or external dependencies that remain.
Keep recovery copies separate from the source service where possible and protect their access credentials. Monitor completed backup jobs, storage consumption and retention rather than assuming that a schedule always succeeds. Weeby Backup plans specify storage capacity and retention scope; retained versions also consume that capacity, so growing source data can affect the available history.
Test a restore to an isolated destination before relying on the backup for production recovery. Check that the application can read the restored database and files, and verify a meaningful function such as a login or recent record.
