Reviving an Eon Mode database on Azure 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 terminated, 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.

Many of the fields in the revive workflow are populated with information provided during provisioning. For details about fields with existing values, see Creating an Eon Mode cluster and database in Azure in MC.

The following steps revive an Eon Mode database on Azure:

  1. On the MC home page, select Revive Eon Mode database. The Provision & Revive an Eon Mode Database window opens.

  2. On Specify cluster access preferences, supply the following information:

    • Azure Subnet: The subnet for your cluster. Select the same subnet used when you deployed the MC instance in the Azure Marketplace. If your organization requires multiple subnets for security purposes, see the Azure documentation for additional information.

    • SSH Public Key: Paste the same public key used when you deployed the MC instance in the Azure Marketplace.

    • CIDR Range: The range of IP addresses for client and SSH access.

  3. Select Next. On Specify Azure AZB path for Communal Storage of database, you can enter a parent directory to list all available Eon Mode databases within that directory:

    1. Enter the directory name. At minimum, you must provide the account and container name, and optionally subfolder names in the following format:

      azb://storage-account/container[/subfolder-name/...]

    2. Select Discover. The MC lists all available Eon Mode databases within the container or subfolder.

    3. Select the database that you want to revive from the list.

  4. Select Next. On Enter revive database configurations, supply the following information:

    • Revive to Vertica Version: Lists the currently available Vertica versions. If you select a version that is later than the version that you used to provision the database, the MC upgrades the database version automatically.

    • Password: The password for the database superuser.

    • Confirm Password: Reenter Password.

  5. Select Next. On Specify cloud instance and depot data storage, supply the following information about the depot:

    • Virtual Machine (VM) Size: The machine types used for the nodes. For recommended machine types, see the memory optimized machine types in Recommended Azure VM types and operating systems.

    • Managed Disk Volume Type: Available for Azure managed disks only. For details about each disk type, see the Azure documentation.

    • Managed Disk Volume Size (GB) per Volume per Available Node: Volume size for each node. This value is populated with the volume configuration defaults for the associated instance type.

    • Node IP Setting: Choose Public IP - Dynamic, Public IP - Static, or Private IP. For details, see the Azure documentation.

  6. Select Next. On Specify additional storage and tag info, supply the following information:

    • Managed Volume Type: Available only for Azure managed disks. For details about each disk type, see the Azure documentation.

    • For the catalog and temp paths, provide the following information:

      • Managed Disk Volume Type: Available only for Azure managed disks. For details about each disk type, see the Azure documentation.

      • Managed Disk Volume Size (GB) per Available Node: Volume size for each node. This value is populated with the volume configuration defaults for the associated VM type.

    • Tag Azure Resources: Optional. Assign distinct, searchable metadata tags to the instances in this cluster. Many organizations use labels to organize, track responsibility, and assign costs for instances.
      To add a tag, select the checkbox to make the Tag Name and Tag Value available. Click Add to create the tag. Tags are displayed below the fields. Vertica recommends that you use lowercase characters in tag fields.

  7. Select Next. On Review revive information, confirm your selections. Select Back to return to a previous section and make changes.

  8. When you are satisfied with your selections, select the Accept terms and conditions checkbox.

  9. Select Revive Database to revive the Eon Mode database on Azure.

For details about database clusters in Management Console, see Managing database clusters.