Browse this section

How to request a restore

A restore can overwrite data created after the selected recovery point. State exactly what you need recovered and whether the recovered copy should replace production or be placed in a separate location for review.

Include in your ticket

  • Service reference, application or dataset, and the files, database or entire machine to restore.
  • The required recovery date and time with timezone, plus when the problem was first noticed.
  • Whether current production data must be preserved and who can authorise replacement.
  • A safe destination or validation plan, acceptable downtime and any dependencies that must be recovered together.

Where practical, validate a separate restored copy first. Check application logins, recent records, permissions and background jobs before switching traffic. A requested recovery point is subject to the backups and retention actually available for your service.

Was this guide helpful?

Related guides

Defining a backup policy for your service

A useful backup policy starts with the data you need to recover and the loss your business can tolerate. Specify both the recovery point objective, meaning acceptable data loss, and the rec…

RAID, snapshots and backups: what each protects

These mechanisms address different failure situations. RAID or replication can keep data available through some component failures. A snapshot can preserve a point-in-time state. An indepen…

Application-consistent database backups

Copying database files while an application is actively writing may not produce a recoverable backup unless the database and backup method support that process. Choose a method appropriate …

Planning retention and backup storage capacity

Backup capacity depends on the amount of protected data, its rate of change, retention and the backup format. Retaining several recovery points does not always mean storing the same number …

Need help applying this to your service?

Tell us your service reference and what you need to achieve. Never include passwords or private keys in a ticket.

Contact support →
← All knowledgebase topics