Restoring Overview
This article explains the basics of restoring with Eon and links to the instructions for every supported resource type.
Restoring copies data from an Eon snapshot back to a destination in your own environment.
Before you can restore, connect a restore account for the environment you want to restore to. This is a one-time step: Once the account is connected, you can restore to it as often as you need, until you disconnect or delete it.
Every restore then follows the same basic flow: find the resource’s snapshot in Eon, choose the restore granularity available for that resource type (for example, an entire EC2 instance versus just a volume), and start the restore.
The sections below link to instructions for connecting a restore account and for restoring each supported resource type.
Connect restore accounts
See About Restore Accounts to learn what a restore account is and how it works, and Manage Restore Accounts for account-level management tasks. To connect a restore account for the first time, use the guide for your cloud provider:
- AWS: Connect Restore Accounts
- Azure: Connect Restore Subscriptions
- GCP: Connect Restore Projects
- MongoDB Atlas: Connect Restore Projects
- Google Workspace: Connect Restore Workspaces
- Microsoft 365: Connect Restore Tenants
- Microsoft Entra ID: Connect Restore Tenants
Restore a resource
Once your restore account is connected, find the instructions for the resource type you want to restore:
Cloud workloads:
SaaS applications:
Bulk restore resources
When many resources need recovering at once, a bulk restore brings them back in one operation instead of one at a time. You choose a snapshot for each resource, and Eon restores each one with its restore template, a saved set of restore settings for that resource. Every resource in a bulk restore needs a restore template, so create and attach templates before you need them. Bulk restore supports EC2 instances and S3 buckets. One batch can mix both types.