Vertica(DBaaS)

• 1: Overview
• 1.1: Server Type
• 1.2: Monitoring metrics
• 2: How-to guides
• 2.1: Backing up and restoring Vertica
• 3: API Reference
• 4: CLI Reference
• 5: Release Note

1 - Overview

Service Overview

Vertica(DBaaS) is a high-availability enterprise database built on a Data Warehouse for large-scale data analysis and processing. Through a single engine, it serves as a data analytics platform that can perform basic analyses such as querying data from various sources without moving them, as well as AI analyses like machine learning. In the 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, it provides an automatic backup feature at user‑specified times to support data recovery at the desired point in case of DB server or data issues.

Service Architecture Diagram

Provided features

Vertica(DBaaS) provides the following features.

• Auto Provisioning (Auto Provisioning): Automatically installs the standard version of the Samsung Cloud Platform database based on Virtual Servers of various specifications.
• Cluster Configuration: Provides a self-high-availability architecture in a masterless form.
• Operation Control Management: Provides functionality to control the status of running servers. You can start or stop a server, and it can be restarted if there is a database issue or to apply configuration changes.
• Backup and Recovery: Provides data backup functionality based on proprietary backup commands. Users can set the backup retention period and start time, and additional fees apply based on backup size. It also offers a recovery feature for backed‑up data; when a user initiates recovery, a separate database is created and restored to the point selected by the user (backup creation time or a custom point). For database recovery, 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 accessed through the Cloud Monitoring service.
• High-Performance Processing of Large-Scale Data: It guarantees stable performance in a Mixed Workload environment of massive parallel processing (MPP, Massively Parallel Processing) and SQL queries. Vertica processes queries through distributed processing and is designed so that queries can be initiated from any node, eliminating a Single Point of Failure where queries would not execute if a specific node fails.

Component

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 wish 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 halted is set to six months before the EoTS date.

The EOS and EoTS dates may change according to the supplier’s policy, 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), see 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 and prepare in advance.

1.1 - Server Type

Vertica(DBaaS) server type

Vertica (DBaaS) offers server types configured with various combinations of CPU, memory, and network bandwidth. When creating Vertica(DBaaS), the Database Engine is installed according to the server type selected for the intended 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.

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

db2 server type

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

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

dbh2 server type

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

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

1.2 - Monitoring metrics

Vertica(DBaaS) Monitoring Metrics

The table below shows the performance monitoring metrics for Vertica (DBaaS) that can be viewed through Cloud Monitoring. For detailed Cloud Monitoring usage, see the Cloud Monitoring guide.

The server monitoring metrics for Vertica (DBaaS) are described in the Virtual Server Monitoring Metrics guide.

2 - How-to guides

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

Create Vertica (DBaaS)

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

To create Vertica(DBaaS), follow these steps.

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

2. On the Service Home page, click the Vertica(DBaaS) Create button. 2. Create navigate to the page.

3. Vertica(DBaaS) Creation page: enter the information required to create the service and select detailed options.

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

     Category	required status	Detailed description
     Image version	Required	Provide a 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.

     Category	required status	Detailed description
     Server name Prefix	Required	The server name where Vertica will be installed must start with a lowercase English letter, and using lowercase letters, numbers, and special characters(-) input 3 to 13 characters Based on the server name, a postfix such as 001, 002 is appended to create the actual server name
     Cluster name	required	Cluster name composed of servers Enter using English letters, 3 ~ 20 characters A cluster is a unit that groups multiple servers
     Number of nodes	required	Number of data nodes Enter the number of nodes in the range of 1-10 If you configure the cluster by entering the number of nodes as 2 or more, you achieve high availability (High Availability)
     Service Type > Server Type	Required	Data node server type Standard: Standard specification commonly used High Capacity: Large-capacity server with 24 vCores or more For detailed information about the server types provided by Vertica (DBaaS), refer to Vertica(DBaaS) Server Type
     Service Type > Planned Compute	Select	Status of resources with Planned Compute configured In Use: Number of resources with Planned Compute configured that are currently in use Configured: Number of resources with Planned Compute configured Coverage Preview: Amount applied per resource by Planned Compute Apply for Planned Compute Service: Go to the Planned Compute service application page For more details, see Planned Compute Apply
     Service Type > Block Storage	Essential	Block Storage type to be used for data nodes Base OS: Area where the engine is installed DATA: Data file storage area After selecting the storage type, enter the capacity (see Block Storage 생성하기 for details on each Block Storage type) SSD: Standard Block Storage SSD_KMS: Additional encrypted volume using KMS (Key Management System) encryption keys The configured storage type is also applied to additional storage Capacity must be entered as a multiple of 8 within the range 16 to 5,120 Add: DATA, Backup data storage area After selecting Use, enter the storage’s purpose, capacity To add storage, click the Add button; to delete, click the x button, up to 9 can be added Capacity can be entered as a multiple of 8 within the range 16 to 5,120, and up to 9 can be created
     Management Console	Selection	If you select Use, you can configure the Node’s server type and Block Storage settings for cluster management and monitoring.
     Management Console > Server Type	Required	Selecting a data node server type for cluster management and monitoring
     Management Console > Block Storage	Required	Select the Block Storage type to be used for data nodes for cluster management and monitoring
     Network > Common Settings	Required	Network settings for servers created by the service Select when you want to apply the same settings to all installed servers Select a pre‑created VPC and Subnet IP: Enter each server’s IP Public NAT setting is only available in per‑server settings
     Network > Server-specific Settings	Required	Network settings for the servers created by the service Select when you want to apply different settings per installed server Choose a pre‑created VPC and Subnet IP: Enter the IP for each server Public NAT requires the VPC to be connected to an Internet Gateway; when use is checked, you can select a reserved IP from the VPC product’s Public IP pool. For details, see Public IP 생성하기.
     IP access control	Selection	Service Access Policy Configuration Since the access policy is set for the IP entered on the page, a separate Security Group policy configuration is 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 the Add button To delete an entered IP, click the x button next to the entered IP
     maintenance period	Selection	Database maintenance window If you select Use, set the day, start time, and duration It is recommended to set a maintenance window for stable DB management. Patch operations will be performed at the scheduled time, causing service interruption If set to unused, Samsung SDS is not responsible for issues arising from unapplied patches.

     Table. Vertica (DBaaS) service configuration items
   • Enter required database configuration information Enter or select the required information in this area.

     Category	required status	Detailed description
     Database name	Essential	Server name applied during DB installation must start with an English letter and be entered using English letters and numbers, 3 to 20 characters
     Database username	Required	DB user name An account with the same name is also created on the OS Enter using lowercase English letters, 2 to 20 characters Restricted database user names can be checked in the Console
     Database password	Essential	Password to use when accessing the DB English letters, numbers, and special characters (“ ‘ excluded) and enter 8~30 characters
     Database password verification	Required	Re-enter the same password to use for DB access
     Database Port number	Required	Port number required for DB connection Enter the DB port within the range 1200 ~ 65535
     Backup > Use	Select	Node backup usage Select Use to choose the node backup retention period and backup start time
     Backup > Retention Period	Select	Backup retention period Select the backup retention period. Set the file retention period to 7 days ~ 35 days Backup files incur additional charges based on size
     Backup > Backup Start Time	Select	Backup start time Select backup start time The minute(s) at which the backup runs is set randomly, and the backup end time cannot be set
     License Key	Required	Enter the Vertica License Key held by the customer If the entered license key is invalid, the service cannot be created
     DB Locale	Required	Settings related to string handling, numeric/currency/date/time display formats, etc., to be used with Vertica (DBaaS) The database is created with default settings based on the selected locale
     time zone	Required	Standard time zone to use with Vertica (DBaaS)

     Table. Vertica (DBaaS) required configuration items
   • In the Additional Information Input area, enter or select the required information.

     Category	required status	Detailed description
     tag	Select	Add Tag Up to 50 per resource can be added After clicking the Add Tag button, enter or select Key, Value values

     Table. Vertica (DBaaS) additional information input fields

4. Summary Review the detailed information and estimated charges generated in the panel, then click the Create button.

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

View Vertica (DBaaS) detailed information

The Vertica(DBaaS) service allows you to view and edit the full list of resources and detailed information. The Vertica(DBaaS) Details page is composed of Details, Tags, Job History tabs.

To view detailed information about the Vertica (DBaaS) service, follow these steps.

1. All Services > Data Analytics > Vertica(DBaaS) Click the menu. 1. Go to the Service Home page of Vertica (DBaaS).
2. On the Service Home page, click the Vertica(DBaaS) menu. 2. Navigate to the Vertica(DBaaS) List page.
3. On the Vertica(DBaaS) List page, click the resource to view detailed information. 3. Vertica(DBaaS) Details Navigate to the page.
   • Vertica(DBaaS) Details At the top of the page, status information and additional feature information are displayed.

     Category	Detailed description
     Cluster status	Cluster status Creating: Creating cluster Editing: Cluster is changing to an Operation execution state Error: Cluster encountered a failure while performing tasks If it occurs continuously, contact the administrator Failed: Cluster failed during creation Restarting: Cluster is restarting Running: Cluster is running normally Starting: Cluster is starting Stopped: Cluster is stopped Stopping: Cluster is stopping Synchronizing: Cluster is synchronizing Terminating: Cluster is terminating Unknown: Cluster status is unknown If it occurs continuously, contact the administrator Upgrading: Cluster is upgrading
     Cluster control	Button to change the cluster state Start: Start a stopped cluster Stop: Stop a running cluster Restart: Restart a running cluster
     View more features	Cluster-related management buttons Service status synchronization: Real-time DB service status lookup Backup history: When backup is configured, check whether the backup runs correctly and view its history Database recovery: Recover the DB based on a specific point in time
     Service termination	Button to cancel the service

     Table. Vertica (DBaaS) status information and additional features

Detailed information

Vertica(DBaaS) List page lets you view detailed information of the selected resource and, if needed, modify the information.

tag

Vertica(DBaaS) List page lets you view the tag information of the selected resource, and add, modify, or delete it.

Work History

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

Managing Vertica (DBaaS) Resources

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

Control operation

If changes occur to a running Vertica (DBaaS) resource, you can start, stop, or restart it.

To control the operation of Vertica (DBaaS), follow these steps.

1. All Services > Data Analytics > Vertica(DBaaS) Click the menu. 1. Go to the Service Home page of Vertica (DBaaS).
2. Click the Vertica(DBaaS) menu on the Service Home page. 2. Navigate to the Vertica(DBaaS) List page.
3. Vertica(DBaaS) List page, click the resource to control its operation. 3. Vertica(DBaaS) Details Navigate to the page.
4. Check the Vertica (DBaaS) status and complete the change using the control button below.
   • Start: The server where the Vertica(DBaaS) service is installed and the Vertica(DBaaS) service is running.
   • Stop: The server on which the Vertica (DBaaS) service is installed and the Vertica (DBaaS) service will be stopped (Stopped).
   • Restart: Only the Vertica(DBaaS) service will be restarted.

Synchronize service status

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

To view the service status of Vertica (DBaaS), follow these steps.

1. All Services > Data Analytics > Vertica(DBaaS) Click the menu. 1. Go to the Service Home page of Vertica (DBaaS).
2. On the Service Home page, click the Vertica(DBaaS) menu. 2. Go to the Vertica(DBaaS) List page.
3. On the Vertica(DBaaS) List page, click the resource to view the service status. 3. Vertica(DBaaS) Details Go to the page.
4. Click the Service Status Sync button. 4. While it is being queried, the cluster changes to Synchronizing state.
5. When the query completes, the status in the server information field is updated, and the cluster changes to the Running state.

Change server type

You can change the configured server type.

To change the server type, follow these steps.

1. All Services > Data Analytics > Vertica(DBaaS) Click the menu. 1. Go to the Service Home page of Vertica (DBaaS).
2. On the Service Home page, click the Vertica(DBaaS) menu. 2. Go to the Vertica(DBaaS) List page.
3. Vertica(DBaaS) List On the page, click the resource to change the server type. 3. Vertica(DBaaS) Details Navigate to the page.
4. Click the Edit icon of the server type you want to change at the bottom of the detailed information. 4. Edit Server Type popup window opens.
5. Edit Server Type After selecting the server type in the popup window, click the Confirm button.

Add storage

If you need more than 5 TB of data storage, you can add additional storage. In a high‑availability configuration (HA cluster), expanding or adding storage capacity is applied simultaneously to all databases.

To add storage, follow these steps.

1. All Services > Data Analytics > Vertica(DBaaS) Click the menu. 1. Go to the Service Home page of Vertica (DBaaS).
2. On the Service Home page, click the Vertica(DBaaS) menu. 2. Navigate to the Vertica(DBaaS) List page.
3. On the Vertica(DBaaS) List page, click the resource to add storage. 3. Vertica(DBaaS) Details Navigate to the page.
4. Click the Add Disk button at the bottom of the detailed view. 4. Additional Storage Request The popup window opens.
5. Additional Storage Request In the popup window, after entering the purpose and size, click the Confirm button.

Expand storage

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

To expand storage capacity, follow the steps below.

1. Click the All Services > Data Analytics > Vertica(DBaaS) menu. 1. Go to the Service Home page of Vertica (DBaaS).
2. On the Service Home page, click the Vertica(DBaaS) menu. 2. Vertica(DBaaS) List Go to the page.
3. On the Vertica(DBaaS) List page, click the resource to change the server type. 3. Go to the Vertica(DBaaS) Details page.
4. Click the Edit button for the additional Disk you want to add at the bottom of the detailed information. 4. Edit Additional Storage A popup window opens.
5. Edit Additional Storage In the popup window, after entering the expansion capacity, click the Confirm button.

Changing the Recovery DB instance type

After the DB recovery is complete, you can change the instance type on the Recovery details screen.

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

1. Click the All Services > Data Analytics > Vertica(DBaaS) menu. 1. Go to the Service Home page of Vertica (DBaaS).
2. On the Service Home page, click the Vertica(DBaaS) menu. 2. Navigate to the Vertica(DBaaS) List page.
3. On the Vertica(DBaaS) List page, click the resource to change the Recovery DB instance type. 3. Vertica(DBaaS) Details Go to the page.
4. Click the Change Instance Type button. 4. Change Instance Type A confirmation dialog will appear.

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

Cancel Vertica (DBaaS)

You can cancel the unused Vertica (DBaaS) to reduce operating costs. However, if you terminate the service, the running service may be stopped immediately, so you should proceed with the termination only after fully considering the impact that may occur when the service is discontinued.

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

1. All Services > Data Analytics > Vertica(DBaaS) Click the menu. 1. Go to the Service Home page of Vertica (DBaaS).
2. On the Service Home page, click the Vertica(DBaaS) menu. 2. Navigate to the Vertica(DBaaS) List page.
3. On the Vertica(DBaaS) List page, select the resource to cancel and click the Cancel Service button.
4. After termination is complete, check on the Vertica(DBaaS) list page whether the resource has been terminated.

2.1 - Backing up and restoring Vertica

Users can set up backups for Vertica (DBaaS) via the Samsung Cloud Platform Console and restore from the backed‑up files.

Backing up Vertica (DBaaS)

You can configure the backup feature to ensure that user data is stored securely. Additionally, you can verify whether a backup completed successfully using the backup history feature, and you can also delete backed‑up files.

Configure Backup

For backup configuration of Vertica(DBaaS), please refer to Create Vertica(DBaaS).

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

1. Click the All Services > Data Analytics > Vertica(DBaaS) menu. 1. Go to the Service Home page of Vertica (DBaaS).
2. On the Service Home page, click the Vertica(DBaaS) menu. 2. Go to the Vertica(DBaaS) List page.
3. Vertica(DBaaS) List page, click the resource to configure a backup. 3. Vertica(DBaaS) Details Navigate to the page.
4. Click the Edit button of the backup item. 4. Backup Settings The popup window opens.
5. When setting up a backup, click Backup Settings in the popup window, click Enable, select the retention period and backup start time, and click the Confirm button.
   • If you want to stop the backup configuration, deselect Use in the Backup Settings popup and authenticate via the logged‑in user’s mobile phone.
     Once user authentication is completed, the backup configuration will be disabled and backup execution will stop.

Check backup history

To view the backup history, follow these steps.

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

Delete backup files

To delete the backup history, follow these steps.

1. All Services > Data Analytics > Vertica(DBaaS) Click the menu. 1. Go to the Service Home page of Vertica (DBaaS).
2. On the Service Home page, click the Vertica(DBaaS) menu. 2. Go to the Vertica(DBaaS) List page.
3. Vertica(DBaaS) List page, click the resource to view the backup history. 3. Vertica(DBaaS) Details Navigate to the page.
4. Click the Backup History button. 4. Backup History The popup window opens.
5. Backup History In the popup window, check the files you want to delete, then authenticate using the logged-in user’s mobile phone.
   • When user authentication is completed, the backup file is deleted.

Recover Vertica(DBaaS)

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

To restore Vertica(DBaaS), follow these steps.

1. Click the All Services > Data Analytics > Vertica(DBaaS) menu. 1. Go to the Service Home page of Vertica (DBaaS).
2. On the Service Home page, click the Vertica(DBaaS) menu. 2. Go to the Vertica(DBaaS) List page.
3. On the Vertica(DBaaS) resource list page, click the resource you want to recover. 3. Vertica(DBaaS) Details Go to the page.
4. Database Recovery button, click it. 4. Database(DBaaS) Recovery Navigate to the page.
5. After entering the relevant information in the Database Recovery area, click the Complete button.

   Category	required status	Detailed description
   Recovery Type	Required	Set the point in time the user wants to recover Backup point (recommended): Recover based on the backup file. Select from the list of backup file timestamps displayed Recovery point: Choose the date and time to recover. Can be selected from the start time of the backup history
   Server name Prefix	Essential	Recovery DB server name Start with a lowercase English letter and use lowercase letters, numbers, and special characters (-) to enter 3 to 16 characters Based on the server name, a postfix such as 001, 002 is appended to generate the actual server name
   Cluster name	Required	Recovery DB cluster name Enter using English letters, 3 to 20 characters A cluster is a unit that groups multiple servers
   Number of nodes	Selection	Data node count 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 specification commonly used High Capacity: large-capacity server with 24 vCores or more
   Service Type > Planned Compute	Selection	Status of resources with Planned Compute configured In Use: Number of resources with Planned Compute that are currently in use Configured: Number of resources with Planned Compute configured Coverage preview: Amount applied per resource by Planned Compute Planned Compute Service Application: Go to the Planned Compute service application page For more details, refer to Planned Compute Apply
   Service Type > Block Storage	Required	Block Storage settings used by the recovery DB Basic OS: Area where the DB engine is installed DATA: Storage area for table data, archive files, etc. Applied identically with the storage type set in the original cluster After selecting Use, enter the storage purpose and capacity To add storage, click the Add button; to delete, click the x button 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	Essential	Management Console server type After selecting Use, select the storage purpose and capacity Standard: standard specification commonly used High Capacity: large-capacity server with 24vCore or more
   Management Console > Block Storage	Required	Block Storage settings used by the Management Console Select Use, then select Default OS
   Database username	Required	Database username Apply the same username set in the original cluster
   Database password	Essential	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 Configuration Since the access policy is set for the IP entered on the page, you do not need to configure a separate Security Group policy. 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	Database maintenance window If you select Use, set the day of week, start time, and duration It is recommended to set a maintenance window for stable management of the database. Patch operations will be performed at the scheduled time, causing service interruption If set to not use, Samsung SDS is not responsible for issues arising from patches not being applied.
   License Key	Required	Enter the Vertica License Key to recover If the entered license key is invalid, the service cannot be created
   tag	Selection	Add Tag After clicking the Add Tag button, enter or select Key, Value values

   Table. Vertica (DBaaS) recovery configuration items

3 - API Reference

4 - CLI Reference

5 - Release Note

Vertica(DBaaS)