OpenText Analytics Database 26.2.x – Microsoft Azure in MC

Mc: Creating an Eon Mode cluster and database in Azure in MC

Mon, 01 Jan 0001 00:00:00 +0000

After you deploy a Management Console instance on Azure, you can provision a cluster and create an Eon Mode database.

Prerequisites

Before you begin, complete or obtain the following:

Complete Deploy Vertica from the Azure Marketplace
Complete the cluster and storage requirements described in Eon Mode on Azure prerequisites
SSH public key used when deploying the MC instance
Review Recommended Azure VM types and operating systems
OpenText™ Analytics Database credentials
Management Console credentials

Creating the database

Complete the following steps from the Management Console:

Log in to the Management Console.
On the Management Console home page, select Create new database.
On License, select the following license mode option:
- Premium Edition: Use your OpenText™ Analytics Database license. After you select this option, click Browse to locate and upload your database license key file, or manually enter it in the field.
Click Next. On Azure Environment, supply the following information:
- SSH Public Key: Paste the same public key used when you deployed the MC instance in the Azure Marketplace.
- 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.
- CIDR Range: The range of IP addresses for client and SSH access. Azure requires that the last octet is 0 and the prefix is 24. For example, 10.20.30.0/24.
- Node IP Setting: Choose Public IP - Dynamic, Public IP - Static, or Private IP. For details, see the Azure documentation.
- Communal Storage URL: The path to a new subfolder in your existing Azure Blob storage account and container. The subfolder must not already exist.
- 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, click the slider to the right to display the Tag Name and Tag Value fields. Click Add to create the tag. Added tags are displayed below the fields. OpenText recommends that you use lowercase characters in tag fields.
Click Next. Database Parameters accepts identifying information about your database and OS version:
- Database Name: The name for your new database. See Creating a database name and password for database name requirements.
- Administrator Username: The name of the database superuser.
- Administrator Password: The password for the database administrator user account. For details, see Password guidelines.
- Confirm Password: Reenter the Administrator Password.
- Vertica Version: Select the desired OpenText™ Analytics Database version. You can select from the latest hotfix of recent OpenText™ Analytics Database releases. For each database version, you can also select the operating system. For available OS and major version options, see Recommended Azure Operating Systems.
- Load Sample Data: Optional. Click the slider to the right to preload your database with example clickstream data. This option is useful if you are testing features and want some preloaded data in the database to query.
Click Next. On Azure configuration, supply the following information:
- Number of Nodes: The initial number of nodes for your database.
- Number of Vertica Database Shards: Sets the number of shards in your database. The database suggests a number of shards automatically, based on your node count. After you set this value, you cannot change it later. The shard count must be greater than or equal to the maximum subcluster count. Be sure to allow for node growth. See Configuring your Vertica cluster for Eon Mode for recommendations.
- Virtual machine (VM) size: The instance types used for the nodes. For a list of recommended instances, see Recommended Azure VM types and operating systems.
- Local Storage per Node: Customize your cluster according to your storage needs. For the default settings for each supported instance, see Eon Mode volume configuration defaults for Azure.
Click Next. On Review, confirm your selections. Click Edit to return to a previous section and make changes.
When you are satisfied with your selections, click the I accept the terms and conditions checkbox.
Click Create Cluster to create a Eon Mode cluster on Azure.

After creating the database

After you create the database, click Get Started to view the Databases page. To view your database, select Manage and View Your Vertica Database to go to the database Overview.

You can also view your database from the Recent Databases section of the MC home page.

For additionalinformation about managing your cluster, instances, and database using Management Console, see Managing database clusters .

Mc: Eon Mode volume configuration defaults for Azure

Mon, 01 Jan 0001 00:00:00 +0000

When you provision an Eon Mode database cluster, Management Console (MC) configures separate volumes for the depot, catalog, and temp directories. The specific volumes and sizes that Management Console configures vary depending on the Azure instance type that you select when provisioning the cluster.

MC follows these rules when allocating resources for these directories for an Eon Mode database cluster:

Depot: Use Standard or Premium LRS to ensure the data is durable.
Catalog: Use Standard or Premium LRS to ensure the data is durable.
Temp: Allocate instance store if available with the selected instance type. Otherwise, allocate Standard or Premium LRS volumes.

If NVMe or Local SSD are displayed as volume types for an instance, there are no other choices. You must choose a different VM to change the volume type.

For details about each disk type, see the Azure documentation.

Instance Type	Instance Storage	Depot	Catalog	Temp
E16ds v4	1 x 600GB	Configurable 8 Data Disks/Managed Disk/Remote Storage 8 x 75 GB Premium/Standard LRS Default: Premium LRS	Data Disk 50 GB Premium/Standard LRS - Durable Default: Premium LRS	1 x 600GB Temporary local SSD (ephemeral) Display: "Local SSD"
E20ds v4	1 x 750 GB	Data Disk 8 x 75 GB	Data Disk 50 GB	1 x 600GB Temporary local SSD (ephemeral) Display: "Local SSD"
E32ds v4	1 x 1200 GB	Data Disk 8 x 75 GB	Data Disk 50 GB	1 x 600GB Temporary local SSD (ephemeral) Display: "Local SSD"
E48ds v4	1 x 1800 GB	Data Disk 8 x 75 GB	Data Disk 50 GB	1 x 600GB Temporary local SSD (ephemeral) Display: "Local SSD"
E64ds v4	1 x 2400 GB	Data Disk 8 x 75 GB	Data Disk 50 GB	1 x 600GB Temporary local SSD (ephemeral) Display: "Local SSD"
E80ids v4	1 x 2400 GB	Data Disk 8 x 75 GB	Data Disk 50 GB	1 x 600GB Temporary local SSD (ephemeral) Display: "Local SSD"
E16s v4	Instance Store not supported	Configurable 8 Data Disks 8 x 75 GB (user defined)	Data Disk 50 GB	Data Disks 1 x 300 GB (user-defined) No less than 300 GB Premium/Standard LRS - Durable Default: Premium LRS 300GB Min: 50 GB Max: 10000 GB Note This instance type supports Remote storage only. Temp uses Data Disks.
E20s v4	Instance Store not supported	Data Disk 8 x 75 GB	Data Disk 50 GB	Data Disks 1 x 300 GB (user-defined) No less than 300 GB Premium/Standard LRS - Durable Default: Premium LRS 300GB Min: 50 GB Max: 10000 GB
E32s v4	Instance Store not supported	Data Disk 8 x 75 GB	Data Disk 50 GB	Data Disks 1 x 300 GB (user-defined) No less than 300 GB Premium/Standard LRS - Durable Default: Premium LRS 300GB Min: 50 GB Max: 10000 GB
E48s v4	Instance Store not supported	Data Disk 8 x 75 GB	Data Disk 50 GB	Data Disks 1 x 300 GB (user-defined) No less than 300 GB Premium/Standard LRS - Durable Default: Premium LRS 300GB Min: 50 GB Max: 10000 GB
E64s v4	Instance Store not supported	Data Disk 8 x 75 GB	Data Disk 50 GB	Data Disks 1 x 300 GB (user-defined) No less than 300 GB Premium/Standard LRS - Durable Default: Premium LRS 300GB Min: 50 GB Max: 10000 GB
E80s v4 Note You cannot use this type to revive an Eon Mode database.	Instance Store not supported	Data Disk 8 x 75 GB	Data Disk 50 GB	Data Disks 1 x 300 GB (user-defined) No less than 300 GB Premium/Standard LRS - Durable Default: Premium LRS 300GB Min: 50 GB Max: 10000 GB
E16s v3	1 x 256 GB	Data Disk 8 x 75 GB	Data Disk 50 GB	1 x 256 GB Use Temporary local SSD (instance store is ephemeral)
E20s v3	1 x 320 GB	Data Disk 8 x 75 GB	Data Disk 50 GB	1 x 320 GB Use Temporary local SSD (instance store is ephemeral)
E32s v3	1 x 512 GB	Data Disk 8 x 75 GB	Data Disk 50 GB	1 x 512 GB Use Temporary local SSD (instance store is ephemeral)
E48s v3	1 x 768 GB	Data Disk 8 x 75 GB	Data Disk 50 GB	1 x 768 GB Use Temporary local SSD (instance store is ephemeral)
E64s v3	1 x 864 GB	Data Disk 8 x 75 GB	Data Disk 50 GB	1 x 864 GB Use Temporary local SSD (instance store is ephemeral)
E64is v3 Note You cannot use this type to revive an Eon Mode database.	1 x 864 GB	Data Disk 8 x 75 GB	Data Disk 50 GB	1 x 864 GB Use Temporary local SSD (instance store is ephemeral)

Instance Type

Instance Storage

Depot

Catalog

Temp

E16ds v4

1 x 600GB

Configurable 8 Data Disks/Managed Disk/Remote Storage

8 x 75 GB

Premium/Standard LRS

Default: Premium LRS

Data Disk

50 GB

Premium/Standard LRS - Durable

Default: Premium LRS

1 x 600GB

Temporary local SSD (ephemeral)

Display: "Local SSD"

E20ds v4

1 x 750 GB

Data Disk

8 x 75 GB

Data Disk

50 GB

1 x 600GB

Temporary local SSD (ephemeral)

Display: "Local SSD"

E32ds v4

1 x 1200 GB

Data Disk

8 x 75 GB

Data Disk

50 GB

1 x 600GB

Temporary local SSD (ephemeral)

Display: "Local SSD"

E48ds v4

1 x 1800 GB

Data Disk

8 x 75 GB

Data Disk

50 GB

1 x 600GB

Temporary local SSD (ephemeral)

Display: "Local SSD"

E64ds v4

1 x 2400 GB

Data Disk

8 x 75 GB

Data Disk

50 GB

1 x 600GB

Temporary local SSD (ephemeral)

Display: "Local SSD"

E80ids v4

1 x 2400 GB

Data Disk

8 x 75 GB

Data Disk

50 GB

1 x 600GB

Temporary local SSD (ephemeral)

Display: "Local SSD"

E16s v4

Instance Store not supported

Configurable 8 Data Disks

8 x 75 GB (user defined)

Data Disk

50 GB

Data Disks

1 x 300 GB (user-defined)

No less than 300 GB

Premium/Standard LRS - Durable

Default: Premium LRS 300GB

Min: 50 GB

Max: 10000 GB

Note

This instance type supports Remote storage only. Temp uses Data Disks.

E20s v4

Instance Store not supported

Data Disk

8 x 75 GB

Data Disk

50 GB

Data Disks

1 x 300 GB (user-defined)

No less than 300 GB

Premium/Standard LRS - Durable

Default: Premium LRS 300GB

Min: 50 GB

Max: 10000 GB

E32s v4

Instance Store not supported

Data Disk

8 x 75 GB

Data Disk

50 GB

Data Disks

1 x 300 GB (user-defined)

No less than 300 GB

Premium/Standard LRS - Durable

Default: Premium LRS 300GB

Min: 50 GB

Max: 10000 GB

E48s v4

Instance Store not supported

Data Disk

8 x 75 GB

Data Disk

50 GB

Data Disks

1 x 300 GB (user-defined)

No less than 300 GB

Premium/Standard LRS - Durable

Default: Premium LRS 300GB

Min: 50 GB

Max: 10000 GB

E64s v4

Instance Store not supported

Data Disk

8 x 75 GB

Data Disk

50 GB

Data Disks

1 x 300 GB (user-defined)

No less than 300 GB

Premium/Standard LRS - Durable

Default: Premium LRS 300GB

Min: 50 GB

Max: 10000 GB

E80s v4

Note

You cannot use this type to revive an Eon Mode database.

Instance Store not supported

Data Disk

8 x 75 GB

Data Disk

50 GB

Data Disks

1 x 300 GB (user-defined)

No less than 300 GB

Premium/Standard LRS - Durable

Default: Premium LRS 300GB

Min: 50 GB

Max: 10000 GB

E16s v3

1 x 256 GB

Data Disk

8 x 75 GB

Data Disk

50 GB

1 x 256 GB

Use Temporary local SSD

(instance store is ephemeral)

E20s v3

1 x 320 GB

Data Disk

8 x 75 GB

Data Disk

50 GB

1 x 320 GB

Use Temporary local SSD

(instance store is ephemeral)

E32s v3

1 x 512 GB

Data Disk

8 x 75 GB

Data Disk

50 GB

1 x 512 GB

Use Temporary local SSD

(instance store is ephemeral)

E48s v3

1 x 768 GB

Data Disk

8 x 75 GB

Data Disk

50 GB

1 x 768 GB

Use Temporary local SSD

(instance store is ephemeral)

E64s v3

1 x 864 GB

Data Disk

8 x 75 GB

Data Disk

50 GB

1 x 864 GB

Use Temporary local SSD

(instance store is ephemeral)

E64is v3

Note

You cannot use this type to revive an Eon Mode database.

1 x 864 GB

Data Disk

8 x 75 GB

Data Disk

50 GB

1 x 864 GB

Use Temporary local SSD

(instance store is ephemeral)

Mc: Reviving an Eon Mode database on Azure in MC

Mon, 01 Jan 0001 00:00:00 +0000

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:

On the MC home page, select Revive Eon Mode database.
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.
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.
Select Next. On Enter revive database configurations, supply the following information:
- Revive to Vertica Version: Lists the currently available OpenText™ Analytics Database 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.
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.
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. OpenText recommends that you use lowercase characters in tag fields.
Select Next. On Review revive information, confirm your selections. Select Back to return to a previous section and make changes.
When you are satisfied with your selections, select the Accept terms and conditions checkbox.
Select Revive Database to revive the Eon Mode database on Azure.

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