Complete and inspect CodeGuard's first backup before treating a new site as protected. The account's activated status alone does not prove that both website files and databases were captured.
IN THIS ARTICLE
01 Accept the first backup
- Open the intended site and check its file path, selected folders and connected databases.
- Start the available initial or on-demand backup if one is not already running.
- Watch the job status until it completes or reports a specific failure. Avoid starting overlapping work.
- Browse the backup contents or request a download and confirm key application files and upload folders.
- Check each database backup separately, including the selected database name and timestamp.
02 Use a short acceptance record
Record the site, live document root, database names, first successful timestamps, exclusions and person who verified the sample. Keep this with the site's operational documentation so a future restore request starts with known facts.
03 Match the failed stage to the next check
Use the actual job message and timestamp. These are diagnostic categories, not guaranteed CodeGuard error labels.
| Observed failure | Next useful check |
|---|---|
| Connection is rejected during authentication | Compare the saved username, credential, protocol and port with the hosting account. Update the protected connection settings, then retest. |
| Connection times out before files can be listed | Ask the hosting administrator to check the endpoint and firewall logs at that time, including access from the current official CodeGuard source addresses. |
| Some folders cannot be read | Confirm the selected document root and the backup account's access to those exact paths. Correct the required access without opening all files to everyone. |
| Files complete but database backup fails | Investigate the database host, selected database and permissions separately. A successful file connection does not validate database access. |
| No clear error, but progress appears stalled | Record the job start time, last visible progress and approximate selected data size. Send that evidence to support before starting repeated jobs or deleting the site record. |
After correcting the identified cause, run the supported backup action and repeat the content checks above. Keep any still-missing component recorded as a protection gap.
Common questions
Why is the first backup slower?
The initial copy needs to capture the selected content. Subsequent jobs can use the service's change-detection approach. Investigate an actual error or lack of progress rather than expecting every site to finish in the same time.
Why is its size different from hosting disk usage?
Selection, exclusions and storage representation can affect the figure. Verify contents instead of judging completeness by size alone.
Can I deploy a major change immediately?
Wait until the relevant backup completes and the required restore method is understood. For a database-driven store, preserve both components at a suitable point before changing the application.
If the first backup is incomplete, correct the connection or scope and repeat the acceptance checks. Do not silently accept missing uploads or databases merely because the dashboard shows a green status for one component.