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

The user can enter the required information of Vertica(DBaaS) through the Samsung Cloud Platform Console and create the service by selecting detailed options.

Creating Vertica(DBaaS)

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

To create a Vertica(DBaaS), follow these steps.

1. Click All Services > Data Analytics > Vertica(DBaaS) menu. It moves to the Service Home page of Vertica(DBaaS).

2. Service Home page, click the Vertica(DBaaS) creation button. Move to the creation page.

3. Create Vertica(DBaaS) page, enter the information required for service creation, and select detailed options.

   • Image and Version Selection area, please select the necessary information.

     Classification	Necessity	Detailed Description
     Image Version	Required	Provides a list of Vertica (DBaaS) versions

     Table. Vertica(DBaaS) image and version input items

   • Enter Service Information Enter or select the necessary information in the area.

     Classification	Necessity	Detailed Description
     Server Name Prefix	Required	The name of the server where Vertica will be installed Starts with a lowercase letter, and consists of 3 to 13 characters using lowercase letters, numbers, and special characters (-) A postfix such as 001, 002 is attached based on the server name to create the actual server name
     Cluster Name	Required	The name of the cluster that the servers are configured in Enter in English, 3-20 characters A cluster is a unit that bundles multiple servers
     Number of Nodes	Required	Number of Data Nodes The number of nodes must be entered within the range of 1-10 Entering the number of nodes as 2 or more to form a cluster ensures high availability
     Service Type > Server Type	Required	Data Node Server Type Standard: Standard specification commonly used High Capacity: High-capacity server with 24vCore or more For more information on the server types provided by Vertica(DBaaS), see Vertica(DBaaS) Server Type
     Service Type > Planned Compute	Selection	Current status of resources with Planned Compute set In Use: Number of resources with Planned Compute set that are currently in use Settings: Number of resources with Planned Compute set Coverage Preview: Amount applied by Planned Compute for each resource Apply for Planned Compute Service: Move to the Planned Compute service application page For more details, refer to How to Apply for Planned Compute
     Service Type > Block Storage	Required	Type of Block Storage to be used for data node Base OS: Area where the engine is installed DATA: Area for storing data files Select storage type and enter capacity (For more information on Block Storage type, refer to Creating Block Storage) SSD: General Block Storage SSD_KMS: Additional encryption volume using KMS (Key Management System) encryption key The set storage type will be applied equally to additional storage Capacity can be entered in multiples of 8 in the range of 16 to 5,120 Additional: DATA, Backup data storage area Select Use and enter Purpose and Capacity of storage To add storage, click the + button, and to delete, click the x button, up to 9 can be added Capacity can be entered in multiples of 8 in the range of 16 to 5,120, and up to 9 can be created
     Management Console	Selection	Use selection, then select the server type of Node for cluster management and monitoring, and Block Storage settings
     Management Console > Server Type	Required	Select server type for data node for cluster management and monitoring
     Management Console > Block Storage	Essential	Select the type of Block Storage to be used for data nodes for cluster management and monitoring
     Network > Common Settings	Required	Network settings for servers created by the service Select if you want to apply the same settings to all servers being installed Select pre-created VPC and Subnet IP: Enter the IP for each server Public NAT settings are only possible in server-specific settings
     Network > Server Settings	Required	Network settings for installing servers created by the service Select to apply different settings for each server being installed Select pre-created VPC and Subnet IP: Enter the IP for each server Public NAT feature is available only when the VPC is connected to the Internet Gateway, checking Use allows selection from the reserved IP in the VPC product’s Public IP. For more information, see Creating Public IP
     IP Access Control	Select	Set service access policy Set access policy for the IP entered on the page, so you don’t need to set Security Group policy separately 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 the entered IP, click the x button next to the entered IP
     Maintenance period	Select	DB maintenance period Use Select the day of the week, start time, and duration It is recommended to set the maintenance period for stable DB management. Patch work is performed at the set time and service interruption occurs If set to not used, SamsungSDS is not responsible for any problems that occur due to non-application of patches.

     Table. Vertica(DBaaS) Service Configuration Items

   • Database Configuration Required Information Input area, please enter or select the required information.

     Classification	Necessity	Detailed Description
     Database name	Mandatory	Server name applied when installing DB Starts with English and enters 3 to 20 characters using English and numbers
     Database username	required	DB username An account with the same name is also created in the OS Enter 2-20 characters using lowercase English letters Restricted Database usernames can be checked in the Console
     Database password	required	Password to use when accessing the DB Enter 8-30 characters including English, numbers, and special characters (excluding " ’)
     Database password confirmation	required	Re-enter the password to be used when accessing the DB
     Database Port number	required	port number required for DB connection DB port should be entered within the range of 1,024 ~ 65,535
     Backup > Use	Selection	Whether to use node backup Use is selected to select the node backup storage period and backup start time
     Backup > Retention Period	Select	Backup Retention Period Select the backup retention period. The file retention period can be set from 7 days to 35 days Backup files are charged separately depending on the capacity
     Backup > Backup start time	Select	Backup start time Select the backup start time The minutes when the backup is performed are set randomly, and the backup end time cannot be set
     License Key	Required	Enter the Vertica License Key owned by the customer If the entered license key is not valid, service creation is not possible
     DB Locale	required	Settings related to string handling, number/currency/date/time display formats, etc. to be used in Vertica(DBaaS) DB is created with the selected Locale as the default setting
     Time Zone	Required	Standard time zone to use for Vertica (DBaaS)

     Fig. Essential configuration items for Vertica(DBaaS)

   • Enter Additional Information Please enter or select the required information in the area.

     Classification	Necessity	Detailed Description
     Tag	Select	Add Tag Up to 50 can be added per resource Click the Add Tag button and enter or select Key, Value

     Fig. Vertica(DBaaS) additional information input items

4. In the Summary panel, check the detailed information generated and the estimated billing amount, and click the Complete button.

   • Once creation is complete, check the created resource on the Resource List page.

Check detailed information about Vertica(DBaaS)

The Vertica(DBaaS) service allows you to check and modify the entire resource list and detailed information. The Vertica(DBaaS) details page consists of details, tags, and operation history tabs.

To check the detailed information of the Vertica(DBaaS) service, follow the next procedure.

1. Click All Services > Data Analytics > Vertica(DBaaS) menu. It moves to the Service Home page of Vertica(DBaaS).
2. Service Home page, click the Vertica(DBaaS) menu. It moves to the Vertica(DBaaS) list page.
3. Vertica(DBaaS) list page, click on the resource to check the detailed information. Move to the Vertica(DBaaS) details page.
   • Vertica(DBaaS) Details page top shows status information and additional features.

Detailed Information

On the Vertica(DBaaS) list page, you can check the detailed information of the selected resource and modify the information if necessary.

Tag

On the Vertica(DBaaS) list page, you can check the tag information of the selected resource, and add, change, or delete it.

Work History

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

Managing Vertica (DBaaS) Resources

If you need to change the existing setting options of the generated Vertica(DBaaS) resource or add storage configuration, you can perform the task on the Vertica(DBaaS) details page.

Operating Control

If there are changes to the running Vertica (DBaaS) resource, you can start, stop, and restart it.

To control the operation of Vertica(DBaaS), follow the next procedure.

1. Click All Services > Data Analytics > Vertica(DBaaS) menu. It moves to the Service Home page of Vertica(DBaaS).
2. Service Home page, click the Vertica(DBaaS) menu. It moves to the Vertica(DBaaS) list page.
3. Click the resource to control operation on the Vertica(DBaaS) list page. It moves to the Vertica(DBaaS) detail page.
4. Check the status of Vertica(DBaaS) and complete the change through the control button below.
   • Start: The server where the Vertica(DBaaS) service is installed and the Vertica(DBaaS) service is running.
   • 중지: Vertica(DBaaS) service installed server and Vertica(DBaaS) service will be stopped.
   • Restart: Only the Vertica (DBaaS) service will be restarted.

Synchronizing Service Status

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

To check the service status of Vertica(DBaaS), follow the next procedure.

1. Click All Services > Data Analytics > Vertica(DBaaS) menu. It moves to the Service Home page of Vertica(DBaaS).
2. Service Home page, click the Vertica(DBaaS) menu. It moves to the Vertica(DBaaS) list page.
3. Click the resource to check the service status on the Vertica(DBaaS) list page. It moves to the Vertica(DBaaS) details page.
4. Service Status Synchronization button should be clicked. During the inquiry, the cluster changes to Synchronizing status.
5. Once the query is complete, the status in the server information item is updated, and the cluster changes to Running status.

Changing the Server Type

You can change the configured server type.

To change the server type, follow these steps.

1. Click All Services > Data Analytics > Vertica(DBaaS) menu. It moves to the Service Home page of Vertica(DBaaS).
2. Service Home page, click the Vertica(DBaaS) menu. Move to the Vertica(DBaaS) list page.
3. On the Vertica(DBaaS) list page, click the resource you want to change the server type for. It moves to the Vertica(DBaaS) details page.
4. Click the Edit icon of the server type you want to change at the bottom of the detailed information. The Server Type Edit popup window opens.
5. Modify Server Type In the modify server type popup window, select the server type and click the OK button.

Adding Storage

If you need more than 5 TB of data storage space, you can add storage. If it is a high-availability configuration (HA cluster), adding or expanding storage capacity will be applied to all DBs simultaneously.

To add storage, follow these steps.

1. Click All Services > Data Analytics > Vertica(DBaaS) menu. It moves to the Service Home page of Vertica(DBaaS).
2. Service Home page, click the Vertica(DBaaS) menu. It moves to the Vertica(DBaaS) list page.
3. On the Vertica(DBaaS) list page, click the resource to add storage. It moves to the Vertica(DBaaS) details page.
4. Click the Disk 추가 button at the bottom of the detailed information. The 추가 스토리지 요청 popup window will open.
5. In the Additional Storage Request popup window, enter the purpose and capacity, then click the Confirm button.

Expanding Storage

The storage added to the data area can be expanded up to a maximum of 5TB based on the initially allocated capacity. Storage can be expanded without stopping Vertica (DBaaS), and if configured in a cluster, all nodes are expanded simultaneously.

To increase the storage capacity, follow the procedure below.

1. Click All Services > Data Analytics > Vertica(DBaaS) menu. It moves to the Service Home page of Vertica(DBaaS).
2. On the Service Home page, click the Vertica(DBaaS) menu. It moves to the Vertica(DBaaS) list page.
3. On the Vertica(DBaaS) list page, click the resource you want to change the server type for. It moves to the Vertica(DBaaS) details page.
4. Click the Modify button of the additional Disk you want to add at the bottom of the detailed information. The Modify Additional Storage popup window will open.
5. Modify Additional Storage popup window, enter the expansion capacity, then click the Confirm button.

Change Recovery DB instance type

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

To change the Recovery DB instance type, follow these steps.

1. Click All Services > Data Analytics > Vertica(DBaaS) menu. It moves to the Service Home page of Vertica(DBaaS).
2. On the Service Home page, click the Vertica(DBaaS) menu. It moves to the Vertica(DBaaS) list page.
3. Vertica(DBaaS) list page, click the resource to change the Recovery DB instance type. It moves to the Vertica(DBaaS) details page.
4. Click the Change Instance Type button. The Change Instance Type confirmation window will be displayed.

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

Canceling Vertica(DBaaS)

You can cancel unused Vertica(DBaaS) to reduce operating costs. However, when canceling the service, the operating service may be stopped immediately, so you should consider the impact of stopping the service sufficiently before proceeding with the cancellation work.

To cancel Vertica(DBaaS), follow these steps.

1. Click All Services > Data Analytics > Vertica(DBaaS) menu. It moves to the Service Home page of Vertica(DBaaS).
2. Service Home page, click the Vertica(DBaaS) menu. Move to the Vertica(DBaaS) list page.
3. Vertica(DBaaS) list page, select the resource to be canceled and click the Service Cancellation button.
4. Once the cancellation is complete, check if the resource has been cancelled 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) 목록 page. Go to the Vertica(DBaaS) 상세 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.

Vertica (DBaaS)를 복구하려면 다음 절차를 따르세요.

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)