Reviving an Eon Mode Database on AWS in MC

An Eon Mode database keeps an up-to-date version of its data and metadata in its communal storage location. After a cluster hosting an Eon Mode database is stopped, this data and metadata continue to reside in communal storage. When you revive the database later, Vertica uses the data in this location to restore the database in the same state on a newly provisioned cluster.

If Management Console has been installed using a CloudFormation template from the AWS Marketplace, you can use the Provision and Revive wizard in Management Console.

You can only revive an Eon Mode database if it is version 9.1.0 or higher.

During a revive of your database, when you select a Vertica version that is higher than the version of the original database in the communal storage, Vertica upgrades your database to match the Vertica version you selected. This upgrade may cause the database revive to take longer. To bypass this upgrade, select the Vertica version of your original database.

After your Vertica database has been upgraded, you can not downgrade your database later.

See Shutting Down and Reviving An Eon Mode Database for how to revive a database using admintools.

If you need to revive your database on a previously existing cluster, you must revive it using admintools, not Management Console. For example, use admintools if you stopped a cluster whose hosts use instance storage where data is not persistently stored, and plan to bring back the database on the same cluster.

Prerequisites

  • The communal storage location (an AWS S3 bucket) of the stopped Eon Mode database you plan to revive. (For how to stop or terminate a cluster using Management Console, see Viewing and Managing Your Cluster.)
  • The username and password of the Eon Mode database you plan to revive.
  • An AWS account with permissions to create a VPC, subnet, security group, instances, and roless
  • An Amazon key pair for SSH access to an instance.

Revive the Database

You use a wizard in Management Console to provision a new cluster and revive a database onto it. For the new cluster, Management Console automatically provisions the same number of instances used by the database when it was last shut down.

You should not use the same communal storage location for running multiple databases, as it causes data corruption. To avoid corruption, you should also never use the revive functionality to simultaneously run the same Eon Mode database on different clusters.

  1. From the Management Console home page, click Provision and Revive an Eon Mode Database. The Provision and Revive an Eon Mode Database wizard opens.
  2. Enter your cloud credentials and cluster preferences. Your cluster must be in the same region as your communal storage location's S3 bucket. To revive the cluster in a new region, you must:
    1. Create a new S3 bucket in the new region.
    2. Copy the previous S3 bucket's contents into it.
    3. Provide the new S3 bucket URL in Step 3.

  3. By default, Vertica creates your cluster in the same subnet as your Management Console instance. If you want to manage all Vertica clusters in the same VPC, you can provision your Vertica database in a different subnet than the Management Console instance. To do so, on the AWS Credentials page, select Show Advanced Options and enter a value in the Subnet field.

    If you specify a different subnet for your database, make sure to secure the subnet.

  4. Enter the S3 URL of the database you are reviving. When you enter an S3 bucket location, Management Console discovers all known Eon Mode databases.
  5. Select the correct database to revive.
  6. Provide the database administrator credentials for the database you are reviving. These credentials are the same as the ones used by the database in the previous cluster.

  7. In the Database Version field, choose the desired Vertica database version. Select from the latest hotfix of recent Vertica releases. For each Vertica version, you can select from a list of associated Linux operating systems.

    If you select a Vertica version that is higher than the version of the original database in the communal storage, Vertica upgrades your database to match the Vertica version you selected. This upgrade may cause the database revive to take longer. To bypass this upgrade, select the Vertica version of your original database.

    After your Vertica database has been upgraded, you can not downgrade your database later.

  8. Choose instance types for the cluster. Management Console provisions the same number of instances used by the database when it was last shut down. The wizard automatically configures separate volumes for the depot, catalog, and temp directories, based on the instance type you select. The last step displays a confirmation page showing the configured volumes. For details on the volume configurations that MC provides, see Eon Mode Volume Configuration Defaults for AWS and Enterprise Mode Volume Configuration Defaults for AWS.Enterprise Mode Volume Configuration Defaults for AWS

    To ensure against data loss, choose instances that use EBS storage. EBS storage is durable, while instance store is temporary. For Eon mode, Management Console displays an alert to inform the user of the potential data loss when terminating instances that support instance store.

  9. Choose whether to encrypt your EBS volumes. With AWS, only 4th and 5th generation instance types (c4, r4, and m4; c5, r5, and m5) support encrypting EBS volumes.
  10. Optionally, you can tag the instances. In the Tag EC2 instances field, if another cluster is already running, Management Console fills those fields with the tag values for the first instance in the cluster. You can accept the defaults, or enter new tag values.
  11. Review your choices, accept the license agreement, and click Create to revive the database on a new cluster. If the version of Management Console you use to revive is higher than that of the database, Management Console first notifies you that it is about to automatically upgrade the database. After starting the revive process, the wizard displays its progress. After a successful revive, the database starts automatically.
  12. When the revive process is complete, click Get Started to navigate to the Fast Tasks page.