Skip to main content
DCHost / Practical guide

Backups and restoring your website

A backup is a copy of your site taken at a particular time. Restoring brings files or data from that copy back into use. When choosing a date, also consider records created after it.

Mercury, Venus, World and Mars web hosting plans include weekly backups. Confirm the available recovery dates, coverage and retention conditions for your service. A weekly schedule does not mean every copy taken since the service began is still available.

Do not assume the same coverage applies to VPS, dedicated servers or other services; check their terms separately.

Visual guideThree checks before a restore

Establish backup availability and data coverage before proceeding.

  1. Which date?

    Find a suitable recovery point before the problem began.

  2. Which data?

    Identify whether you need files, a database, email or a combination.

  3. What will you verify?

    Sign-in, important records, forms and email where applicable.

Confirm that the requested date and coverage are available for your service before restoring.

Take a current copy before changes​

When? Just before a major update or migration. A weekly backup may not contain data added today.

  1. Take a current copy of the website files.
  2. Back up the database as part of the same plan. It stores records such as posts, users and orders.
  3. If you need to protect email, confirm that the messages are actually included.
  4. Record the backup date and contents. Check that the file opens; use the backup verification guide below for a full check.
  5. Store the copy in a restricted location, outside website folders that can be downloaded through a browser.

Choose the recovery point​

A recovery point is the date and time you want to return to from the available backups.

  1. Record when the problem first appeared and which data was affected.
  2. Open a support ticket in the DCHost customer portal. Identify the service, preferred date and whether you need files, a database, email or a combination restored.
  3. Confirm with support that this recovery date and coverage are available before proceeding.
  4. Preserve a copy of the current state too. Restoring may affect orders or content created after the selected backup.
  5. Consider whether the backup can be tested separately before restoring the live service.
  6. Check that the file and database versions are compatible with the same application version.

Example: If a problem started on Tuesday, Sunday's backup may help, but it will not contain Monday's orders. Decide how to preserve those records before restoring.

Visual guideProtect data created after the backup

This timeline is an example; available backup dates depend on the service.

  1. Sunday · Backup taken

    The copy contains records present at this point in time.

  2. Monday · New record

    A later order is not included in Sunday’s copy.

  3. Tuesday · Restore decision

    Decide how to preserve the new order before using Sunday’s backup.

Returning to an older backup can affect newer records as well as undoing a problem.

Verify after restoration​

  1. Open the home page and several important internal pages.
  2. Sign in as an administrator and compare important records with the backup date.
  3. Verify forms and uploads with controlled tests.
  4. If email was restored, check folders and messages.
  5. Review the error logs.

Expected result: The intended files and records work as expected for the selected date. If an outdated plugin or compromised account caused the original problem, fix that cause too; restoring an older backup does not resolve it by itself.

Export the data you will need before ending a service. Do not assume a backup available today will remain available later or after cancellation. Keep the copies you need under your own control.