Skip to navigation
RestoringRestore Accounts

About Restore Accounts

This article explains how restore accounts work in Eon, including essential details about connecting, disconnecting, and deleting them.

A restore account is a cloud entity that can be a destination when restoring. As a coverall term, these are called “accounts” in Eon. When working with a specific provider, they may be called accounts, subscriptions, projects, tenants, or workspaces.

When you connect a restore account, you’ll grant Eon the permissions it needs to create and manage resources, as well as to create a temporary restore server in the restore account. The permissions are installed using a deployment template. To review the deployment template and the permissions it installs, see the AWS, Azure, and GCP permissions deployment files.

You can add as many restore accounts as you need.

Granular restore destinations

In addition to restoring resources, you can also restore granular data to a restore account. Granular data refers to restoring individual files, folders, or records from an Eon snapshot.

You can restore files or folders with the file explorer, and you can restore individual records by querying with the database explorer.

When restoring granular data, Eon needs a storage location in the restore account to save the restored data to (for example, an S3 bucket or Azure Storage Account).

The restore server

When you restore a resource or granular data, Eon creates a temporary restore server in the restore account to run the restore operations. Once the restore is complete, Eon deletes the restore server.

The restore server requires:

  • Communication with Eon to allow the Eon control plane to manage restore operations and securely retrieve data from your vault. This can happen through outbound internet access or, for AWS private subnets, through VPC endpoints.

  • Access to the restore destination, which can be a new resource or storage for granular data. The specific requirements depend on what you’re restoring.

For requirements specific to your cloud provider, see AWS: Restore Server Requirements and GCP: Restore Server Requirements.

Disconnected and deleted restore accounts

Disconnecting and deleting are two separate actions, with different effects on your restore capability and restore account list. This section covers both.

Disconnected restore accounts

Although you can disconnect a restore account from Eon whenever you want, it’s important to know what this means for your ability to restore data. Here are the details of what happens when you disconnect a restore account:

  • Restore capability: Immediately, you won’t be able to restore data to the disconnected account.

  • Existing restore operations: Any in-progress restore operations to the disconnected account are canceled.

  • Account permissions: The permissions you granted Eon in the restore account remain in place unless you manually remove them.

You can reconnect a disconnected restore account at any time. When you reconnect, you can immediately resume restoring data to that account.

Deleted restore accounts

When you delete a restore account, Eon permanently removes it from your restore account list. This action can’t be undone. To use the account in Eon again, you’ll need to connect it as a new restore account.

The Delete option in the restore accounts page becomes available only when the account status is Disconnected or Insufficient permissions. Hovering over the unavailable option shows the reason.

Here’s what happens after you delete a restore account:

  • Restore account list: The account is no longer shown.

  • Restore jobs: Restore jobs that ran for the deleted account remain in your job history with the original name preserved.

Account display names

Eon displays a restore account using its name from the cloud provider, unless you set a custom display name in Eon. The display name appears consistently across Eon, including in your inventory, job details, notifications, and audit logs.

Setting a custom display name for the account in Eon always takes precedence over any names set in the cloud provider.

If you don’t set a custom display name, Eon infers one from information retrieved from the cloud provider:

  • AWS: Specialized logic is used, outlined in AWS account names below.
  • Azure: Subscription name is used.
  • GCP: Project name is used.

AWS account names

AWS restore accounts can have two separate provider values, shown as Account name and Account alias in the account’s details:

  • Account name: Comes from AWS Organizations. Eon gets this value only for accounts connected as part of an AWS organization, and keeps it in sync automatically whenever it syncs the organization’s member accounts. Standalone AWS accounts, connected without an organization, have no account name and show only their alias.

  • Account alias. The account’s IAM alias, if one is set.

When both values are set and differ, Eon combines them into one display name, for example Production (acme-prod). If only one value is set, Eon shows that value alone. If neither is set, Eon shows the account ID.

Additional information

Permissions deployment files:

Restore accounts:

Was this page helpful?