Vertica(DBaaS)

• 1: Overview
• 1.1: Server Type
• 1.2: Monitoring Metrics
• 2: How-to guides
• 2.1: Vertica Backup and Recovery
• 3: API Reference
• 4: CLI Reference
• 5: Release Note

1 - Overview

Service Overview

Vertica(DBaaS) is a high-availability enterprise database based on Data Warehouse for large-scale data analysis/processing. It is a data analysis platform that, through a single engine, can perform basic analyses such as queries on data coming from various sources without moving them, as well as AI analyses like machine learning. In Samsung Cloud Platform, DB management functions such as high‑availability configuration, backup/recovery, patching, parameter management, and monitoring are added to ensure stable management of single instances or critical data, enabling automation of tasks throughout the database lifecycle. Additionally, to prepare for issues with DB servers or data, it provides an automatic backup function at user‑specified times, supporting data recovery at the desired point in time.

Service Architecture Diagram

Provided Features

Vertica (DBaaS) provides the following features.

• Auto Provisioning: Automatically installs the DB of the standard version of Samsung Cloud Platform based on Virtual Servers of various specifications.
• Cluster configuration: Provides its own high-availability architecture in a Masterless form.
• Operation Control Management: Provides a function to control the status of running servers. Servers can be started and stopped, and can be restarted if there is a problem with the DB or to apply configuration values.
• Backup and Recovery: Provides a data backup function based on its own backup commands. The backup retention period and backup start time can be set by the user, and additional charges apply based on backup size. It also provides a recovery function for backed-up data; when the user performs a recovery, a separate DB is created and recovery proceeds to the point selected by the user (backup save point, user-specified point). When recovering a Database, you can choose to install the Management Console for use.
• Service status query: You can view the final status of the current DB service.
• Monitoring: CPU, memory, DB performance monitoring information can be checked through the Cloud Monitoring service.
• High-performance processing of large-scale data: Guarantees stable performance in environments with massive parallel processing (MPP, Massively Parallel Processing) and SQL query Mixed Workload. Vertica processes queries through distributed processing and has a structure that allows queries to be started from any node, so there is no Single Point of Failure where queries would not be executed in case of a specific node failure.

Components

Vertica(DBaaS) provides pre-validated engine versions and various server types. Users can select and use them according to the scale of the service they want to configure.

Engine Version

The engine versions supported by Vertica(DBaaS) are as follows.

Technical support can be used until the supplier’s EoTS (End of Technical Service) date, and the EOS date when new creation is stopped is set to six months before the EoTS date.

According to the supplier’s policy, the EOS and EoTS dates may change, so please refer to the supplier’s license management policy page for details.

Server Type

The server types supported by Vertica (DBaaS) are as follows.

For detailed information about the server types provided by Vertica (DBaaS), please refer to Vertica server types.

Preliminary Service

This is a list of services that must be pre-configured before creating the service. Please refer to the guide provided for each service for details and prepare in advance.

1.1 - Server Type

Vertica(DBaaS) server type

Vertica(DBaaS) provides a server type composed of various combinations such as CPU, Memory, Network Bandwidth, etc. When creating Vertica(DBaaS), the Database Engine is installed according to the server type selected for the purpose of use.

The server types supported by Vertica(DBaaS) are as follows.

Standard db1v2m4

db1 server type

The db1 server type of Vertica(DBaaS) is provided with standard specifications (vCPU, Memory) and is suitable for various database workloads.

• Up to 3.3Ghz Intel 3rd generation (Ice Lake) Xeon Gold 6342 Processor
• Supports up to 16 vCPUs and 256 GB of memory
• Up to 12.5 Gbps networking speed

DB2 server type

The db2 server type of Vertica(DBaaS) is provided with standard specifications (vCPU, Memory) and is suitable for various database workloads.

• Up to 3.2GHz Intel 4th generation (Sapphire Rapids) Xeon Gold 6448H Processor
• Supports up to 16 vCPUs and 256 GB of memory
• Up to 12.5 Gbps networking speed

DBH2 Server Type

The dbh2 server type of Vertica(DBaaS) is provided with large-capacity server specifications and is suitable for database workloads for large-scale data processing.

• Up to 3.2GHz Intel 4th generation (Sapphire Rapids) Xeon Gold 6448H Processor
• Supports up to 128 vCPUs and 1,536 GB of memory
• Up to 25Gbps networking speed

1.2 - Monitoring Metrics

Vertica(DBaaS) monitoring metrics

The following table shows the performance monitoring metrics of Vertica (DBaaS) that can be checked through Cloud Monitoring. For detailed instructions on how to use Cloud Monitoring, please refer to the Cloud Monitoring guide.

The server monitoring metrics of Vertica(DBaaS) refer to the Virtual Server monitoring metrics guide.

2 - How-to guides

Users can create the Vertica(DBaaS) service by entering required information and selecting detailed options through Samsung Cloud Platform Console.

Create Vertica(DBaaS)

You can create and use the Vertica(DBaaS) service in Samsung Cloud Platform Console.

Follow the procedure below to create Vertica(DBaaS).

1. Click All Services > Data Analytics > Vertica(DBaaS) menu. You will be moved to the Service Home page of Vertica(DBaaS).

2. Click Create Vertica(DBaaS) button on the Service Home page. You will be moved to the Create page.

3. Enter the information required to create the service and select detailed options on the Create Vertica(DBaaS) page.

   • Select the required information in the Image and Version Selection area.

     Division	Required	Description
     Image Version	Required	List of Vertica(DBaaS) versions

     Table. Vertica(DBaaS) Image and Version Input Items
   • Enter or select the required information in the Service Information Input area.

     Division	Required	Description
     Server Name Prefix	Required	Server name where Vertica is installed Start with lowercase English letters, and enter 3 to 13 characters using lowercase letters, numbers, and special characters (-) Actual server name is created with postfix such as 001, 002 based on server name
     Cluster Name	Required	Cluster name where servers are configured Enter 3 to 20 characters using English letters Cluster is a unit that bundles multiple servers
     Node Count	Required	Number of data nodes Enter node count in the range of 1-10 If you enter 2 or more nodes to configure a cluster, you secure High Availability
     Service Type > Server Type	Required	Data node server type Standard: Standard specifications commonly used High Capacity: Large capacity servers with 24vCore or more For more information about server types provided by Vertica(DBaaS), refer to Vertica(DBaaS) Server Type
     Service Type > Planned Compute	Optional	Resource status where Planned Compute is set In Use: Number of resources in use among resources where Planned Compute is set Set: Number of resources where Planned Compute is set Coverage Preview: Amount applied with Planned Compute for each resource Apply for Planned Compute Service: Move to Planned Compute service application page For more information, refer to Apply for Planned Compute
     Service Type > Block Storage	Required	Block Storage type to be used for data nodes Basic OS: Area where engine is installed DATA: Data file storage area Select storage type and enter capacity (for detailed information about each Block Storage type, refer to Create Block Storage) SSD: General Block Storage SSD_KMS: Additional encrypted volume using KMS(Key Management System) encryption key Set Storage type is also applied identically to additional storage Enter capacity in multiples of 8 in the range of 16 ~ 5,120 Additional: DATA, Backup data storage area Select Use and enter storage Purpose, Capacity Click + button to add storage, and click x button to delete, you can add up to 9 Enter capacity in multiples of 8 in the range of 16 ~ 5,120, and you can create up to 9
     Management Console	Optional	If Use is selected, server type and Block Storage settings for Node for cluster management and monitoring
     Management Console > Server Type	Required	Select data node server type for cluster management and monitoring
     Management Console > Block Storage	Required	Select Block Storage type to be used for data node for cluster management and monitoring
     Network > Common Settings	Required	Network settings where servers created in the service are installed Select to apply the same settings to all servers being installed Select previously created VPC and Subnet IP: Enter IP for each server Public NAT settings are only possible with per-server settings
     Network > Per-Server Settings	Required	Network settings where servers created in the service are installed Select to apply different settings for each server being installed Select previously created VPC and Subnet IP: Enter IP for each server Public NAT function can be used only when VPC is connected to Internet Gateway. If Use is checked, you can select from reserved IPs in Public IP of VPC product. For more information, refer to Create Public IP
     IP Access Control	Optional	Service access policy settings Access policy is set for IPs entered on the page, so separate Security Group policy settings are not required Enter in IP format (example: 192.168.10.1) or CIDR format (example: 192.168.10.0/24, 192.168.10.1/32) and click Add button To delete entered IP, click x button next to the entered IP
     Maintenance Window	Optional	DB maintenance window If Use is selected, set day of week, start time, and duration It is recommended to set a maintenance window for stable DB management. Patch work proceeds at the set time and service interruption occurs If set to Not Used, problems caused by not applying patches are not the responsibility of Samsung SDS

     Table. Vertica(DBaaS) Service Configuration Items
   • Enter or select the required information in the Database Configuration Required Information Input area.

     Division	Required	Description
     Database Name	Required	Server name applied when DB is installed Start with English letters, and enter 3 to 20 characters using English letters and numbers
     Database Username	Required	DB username Account with that name is also created in OS Enter 2 to 20 characters using lowercase English letters Database usernames with restricted use can be checked in Console
     Database Password	Required	Password to use when accessing DB Enter 8 to 30 characters including English letters, numbers, and special characters (excluding " ’)
     Database Password Confirmation	Required	Re-enter the password to use when accessing DB identically
     Database Port Number	Required	Port number required for DB connection Enter DB port in the range of 1200 ~ 65535
     Backup > Use	Optional	Whether to use node backup Select Use and select node backup retention period and backup start time
     Backup > Retention Period	Optional	Backup retention period Select backup retention period. File retention period can be set from 7 days to 35 days Separate fees are charged for backup files depending on capacity
     Backup > Backup Start Time	Optional	Backup start time Select backup start time Backup execution minutes are set randomly, and backup end time cannot be set
     License Key	Required	Enter Vertica License Key held by customer If the entered license key is invalid, service creation is not possible
     DB Locale	Required	Settings related to string processing, number/currency/date/time display format, etc. to use in Vertica(DBaaS) DB is created with default settings to the selected Locale
     Time Zone	Required	Standard time zone to use in Vertica(DBaaS)

     Table. Vertica(DBaaS) Required Configuration Items
   • Enter or select the required information in the Additional Information Input area.

     Division	Required	Description
     Tags	Optional	Add tags Can add up to 50 per resource After clicking Add Tag button, enter or select Key, Value values

     Table. Vertica(DBaaS) Additional Information Input Items

4. Check the detailed information and estimated billing amount in the Summary panel, and click Complete button.

   • When creation is completed, check the created resource on the Resource List page.

Check Vertica(DBaaS) Detailed Information

Vertica(DBaaS) service can check and modify the entire resource list and detailed information. The Vertica(DBaaS) Details page consists of Details, Tags, Operation History tabs.

Follow the procedure below to check the detailed information of Vertica(DBaaS) service.

1. Click All Services > Data Analytics > Vertica(DBaaS) menu. You will be moved to the Service Home page of Vertica(DBaaS).
2. Click Vertica(DBaaS) menu on the Service Home page. You will be moved to the Vertica(DBaaS) List page.
3. Click the resource for which you want to check detailed information on the Vertica(DBaaS) List page. You will be moved to the Vertica(DBaaS) Details page.
   • Status information and additional feature information are displayed at the top of the Vertica(DBaaS) Details page.

     Division	Description
     Cluster Status	Cluster status Creating: Cluster is being created Editing: Cluster is changing to state where Operation is being performed Error: Cluster failed while performing operation If it occurs continuously, contact administrator Failed: Cluster failed during creation process Restarting: Cluster is being restarted Running: Cluster is operating normally Starting: Cluster is being started Stopped: Cluster is stopped Stopping: Cluster is in stopping state Synchronizing: Cluster is being synchronized Terminating: Cluster is being deleted Unknown: Cluster status is unknown If it occurs continuously, contact administrator Upgrading: Cluster is changing to state where upgrade is being performed
     Cluster Control	Buttons to change cluster status Start: Start the stopped cluster Stop: Stop the running cluster Restart: Restart the running cluster
     Additional Features More	Cluster-related management buttons Synchronize Service Status: Check real-time DB service status Backup History: If backup is set, check whether backup is executed normally and history Database Recovery: Recover DB based on specific time point
     Service Termination	Button to terminate service

     Table. Vertica(DBaaS) Status Information and Additional Features

Details

You can check the detailed information of the resource selected on the Vertica(DBaaS) List page and modify information if necessary.

Tags

You can check the tag information of the resource selected on the Vertica(DBaaS) List page and add, change, or delete tags.

Operation History

You can check the operation history of the resource selected on the Vertica(DBaaS) List page.

Manage Vertica(DBaaS) Resources

If you need to change existing configuration options of created Vertica(DBaaS) resources or add storage configuration, you can perform tasks on the Vertica(DBaaS) Details page.

Control Operation

If there are changes to running Vertica(DBaaS) resources, you can start, stop, or restart.

Follow the procedure below to control the operation of Vertica(DBaaS).

1. Click All Services > Data Analytics > Vertica(DBaaS) menu. You will be moved to the Service Home page of Vertica(DBaaS).
2. Click Vertica(DBaaS) menu on the Service Home page. You will be moved to the Vertica(DBaaS) List page.
3. Click the resource for which you want to control operation on the Vertica(DBaaS) List page. You will be moved to the Vertica(DBaaS) Details page.
4. Check Vertica(DBaaS) status and complete changes through the following control buttons.
   • Start: Server where Vertica(DBaaS) service is installed and Vertica(DBaaS) service become running.
   • Stop: Server where Vertica(DBaaS) service is installed and Vertica(DBaaS) service become stopped.
   • Restart: Only Vertica(DBaaS) service is restarted.

Synchronize Service Status

You can synchronize the real-time service status of Vertica(DBaaS).

Follow the procedure below to check the service status of Vertica(DBaaS).

1. Click All Services > Data Analytics > Vertica(DBaaS) menu. You will be moved to the Service Home page of Vertica(DBaaS).
2. Click Vertica(DBaaS) menu on the Service Home page. You will be moved to the Vertica(DBaaS) List page.
3. Click the resource for which you want to check service status on the Vertica(DBaaS) List page. You will be moved to the Vertica(DBaaS) Details page.
4. Click Synchronize Service Status button. Cluster changes to Synchronizing status during checking.
5. When checking is completed, status is updated in the server information item, and cluster changes to Running status.

Change Server Type

You can change the configured server type.

Follow the procedure below to change the server type.

1. Click All Services > Data Analytics > Vertica(DBaaS) menu. You will be moved to the Service Home page of Vertica(DBaaS).
2. Click Vertica(DBaaS) menu on the Service Home page. You will be moved to the Vertica(DBaaS) List page.
3. Click the resource for which you want to change server type on the Vertica(DBaaS) List page. You will be moved to the Vertica(DBaaS) Details page.
4. Click Modify icon of the server type you want to change at the bottom of detailed information. Modify Server Type popup window opens.
5. Select server type in the Modify Server Type popup window, and click Confirm button.

Add Storage

If you need more than 5 TB of data storage space, you can add storage. If it is High Availability configuration (HA cluster), when storage capacity is expanded or added, it is applied to all DBs simultaneously.

Follow the procedure below to add storage.

1. Click All Services > Data Analytics > Vertica(DBaaS) menu. You will be moved to the Service Home page of Vertica(DBaaS).
2. Click Vertica(DBaaS) menu on the Service Home page. You will be moved to the Vertica(DBaaS) List page.
3. Click the resource for which you want to add storage on the Vertica(DBaaS) List page. You will be moved to the Vertica(DBaaS) Details page.
4. Click Add Disk button at the bottom of detailed information. Request Additional Storage popup window opens.
5. Enter purpose and capacity in the Request Additional Storage popup window, and click Confirm button.

Expand Storage

You can expand storage added as data area up to 5TB based on initially allocated capacity. You can expand storage without stopping Vertica(DBaaS), and if configured as a cluster, all nodes are expanded simultaneously.

Follow the procedure below to expand storage capacity.

1. Click All Services > Data Analytics > Vertica(DBaaS) menu. You will be moved to the Service Home page of Vertica(DBaaS).
2. Click Vertica(DBaaS) menu on the Service Home page. You will be moved to the Vertica(DBaaS) List page.
3. Click the resource for which you want to change server type on the Vertica(DBaaS) List page. You will be moved to the Vertica(DBaaS) Details page.
4. Click Modify button of the additional Disk you want to expand at the bottom of detailed information. Modify Additional Storage popup window opens.
5. Enter expansion capacity in the Modify Additional Storage popup window, and click Confirm button.

Change Recovery DB Instance Type

After DB recovery is completed, you can change the instance type in the Recovery detailed information screen.

Follow the procedure below to change the Recovery DB instance type.

1. Click All Services > Data Analytics > Vertica(DBaaS) menu. You will be moved to the Service Home page of Vertica(DBaaS).
2. Click Vertica(DBaaS) menu on the Service Home page. You will be moved to the Vertica(DBaaS) List page.
3. Click the resource for which you want to change Recovery DB instance type on the Vertica(DBaaS) List page. You will be moved to the Vertica(DBaaS) Details page.
4. Click Change Instance Type button. Change Instance Type confirmation dialog is displayed.

• DB instance type is changed from Recovery to Active to perform the same function as a single DB.

Terminate Vertica(DBaaS)

You can reduce operating costs by terminating unused Vertica(DBaaS). However, if you terminate the service, the running service may stop immediately, so you should fully consider the impact of service interruption before proceeding with termination work.

Follow the procedure below to terminate Vertica(DBaaS).

1. Click All Services > Data Analytics > Vertica(DBaaS) menu. You will be moved to the Service Home page of Vertica(DBaaS).
2. Click Vertica(DBaaS) menu on the Service Home page. You will be moved to the Vertica(DBaaS) List page.
3. Select the resource to terminate on the Vertica(DBaaS) List page, and click Terminate Service button.
4. When termination is completed, check if the resource is terminated on the Vertica(DBaaS) list page.

2.1 - Vertica Backup and Recovery

Users can set up backups of Vertica (DBaaS) through the Samsung Cloud Platform Console and restore from the backed-up files.

Vertica(DBaaS) Backup

You can set up a backup function so that the user’s data can be stored safely. Also, through the backup history function, you can verify whether the backup was performed correctly and you can also delete backed-up files.

Set up backup

For backup configuration of Vertica(DBaaS), see Create Vertica(DBaaS).

To modify the backup settings of Vertica (DBaaS), follow the steps below.

1. All Services > Data Analytics > Vertica(DBaaS) Click the menu. Navigate to the Service Home page of Vertica(DBaaS).
2. Click the Vertica(DBaaS) menu on the Service Home page. Navigate to the Vertica(DBaaS) List page.
3. Click the resource to set backup on the Vertica(DBaaS) List page. You will be taken to the Vertica(DBaaS) Details page.
4. Click the Edit button of the backup item. Backup Settings popup window opens.
5. When setting up a backup, click Use in the Backup Settings popup, select the retention period and backup start time, and click the Confirm button.
   • If you want to stop the backup setting, uncheck Use in the Backup Setting popup window and click the Confirm button.

Check backup history

To view the backup history, follow these steps.

1. All Services > Data Analytics > Vertica(DBaaS) Click the menu. Go to the Service Home page of Vertica(DBaaS).
2. Click the Vertica(DBaaS) menu on the Service Home page. Navigate to the Vertica(DBaaS) list page.
3. Click the resource to view the backup history on the Vertica(DBaaS) List page. Go to the Vertica(DBaaS) Details page.
4. Click the Backup History button. Backup History popup opens.
5. Backup History In the popup window, you can check the backup status, version, backup start date and time, backup completion date and time, and size.

Delete backup file

To delete the backup history, follow the steps below.

1. All Services > Data Analytics > Vertica(DBaaS) Click the menu. Navigate to the Service Home page of Vertica(DBaaS).
2. Service Home page, click the Vertica(DBaaS) menu. Go to the Vertica(DBaaS) list page.
3. Vertica(DBaaS) List On the page, click the resource to view the backup history. Vertica(DBaaS) Details You will be taken to the page.
4. Click the Backup History button. The Backup History popup window opens.
5. Backup History In the popup window, check the file you want to delete, then click the Delete button.

Vertica(DBaaS) Recover

If restoration from a backup file is required due to a failure or data loss, you can use the cluster recovery feature to recover based on a specific point in time.

To recover Vertica (DBaaS), follow the steps below.

1. All Services > Data Analytics > Vertica(DBaaS) Click the menu. Navigate to the Service Home page of Vertica(DBaaS).
2. Click the Vertica(DBaaS) menu on the Service Home page. Go to the Vertica(DBaaS) List page.
3. Vertica(DBaaS) Resource On the list page, click the resource you want to recover. You will be taken to the Vertica(DBaaS) Detail page.
4. Click the Database Recovery button. Go to the Database(DBaaS) Recovery page.
5. Database Recovery area, after entering the relevant information, click the Complete button.

   Category	Required or not	Detailed description
   Recovery Type	Required	Set the point in time the user wants to recover Backup point (recommended): Recover based on backup file. Select from the list of backup file timestamps displayed in the list Recovery point: Choose the date and time to recover. Can be selected from the start time of the backup history
   Server Name Prefix	Required	Recovery DB Server Name Enter 3~16 characters starting with a lowercase English letter, using lowercase letters, numbers, and the special character (-) A postfix such as 001, 002 is appended based on the server name to create the actual server name
   Cluster Name	Required	Recovery DB Cluster Name Enter using English, 3 to 20 characters A cluster is a unit that groups multiple servers
   Number of nodes	Select	Number of data nodes Set to be the same as the number of nodes configured in the original cluster.
   Service Type > Server Type	Required	Recovery DB Server Type Standard: Standard specifications commonly used High Capacity: Large-capacity server of 24 vCore or more
   Service Type > Planned Compute	Select	Status of resources with Planned Compute set In Use: Number of resources with Planned Compute that are currently in use Configured: Number of resources with Planned Compute set Coverage Preview: Amount applied per resource by Planned Compute Planned Compute Service Application: Go to the Planned Compute service application page For details, refer to Planned Compute Apply
   Service Type > Block Storage	Required	Block Storage settings used by the recovery DB Base OS: Area where the DB engine is installed DATA: Storage area for table data, archive files, etc. Apply the same Storage type as set in the source cluster After selecting Use, enter the storage purpose and capacity Click the + button to add storage, and the x button to delete Capacity can be entered in multiples of 8 within the range 16 to 5,120, and up to 9 can be created
   Management Console > Server Type	Required	Management Console Server Type After selecting Use, choose the storage purpose and capacity Standard: Standard specifications commonly used High Capacity: Large-capacity server with 24 vCore or more
   Management Console > Block Storage	Required	Block Storage settings used by Management Console Select Use and then select Base OS
   Database username	Required	Database username Apply the same username set in the original cluster
   Database Password	Required	Database Password Apply the same password set in the original cluster
   Database Port Number	Required	Database Port Number Apply the same Port number as set in the original cluster
   IP Access Control	Select	Service Access Policy Settings Since the access policy is set for the IP entered on the page, you do not need to separately configure Security Group policies. Enter in IP format (e.g., 192.168.10.1) or CIDR format (e.g., 192.168.10.0/24, 192.168.10.1/32) and click the Add button To delete an entered IP, click the x button next to the entered IP
   Maintenance period	Select	DB maintenance period If Use is selected, set day of week, start time, and duration It is recommended to set a maintenance period for stable DB management. Patch work will be performed at the set time, causing service interruption If set to not use, Samsung SDS is not responsible for issues arising from unapplied patches.
   License Key	Required	Enter the Vertica License Key to recover If the entered license key is not valid, service creation is not possible
   Tag	Select	Add Tag Add Tag button click after entering or selecting Key, Value values

   Table. Vertica(DBaaS) Recovery Configuration Items

3 - API Reference

4 - CLI Reference

5 - Release Note

Vertica(DBaaS)