This is the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

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.

Cloud Monitoring 서비스 종료 안내

According to Samsung Cloud Platform’s policy, the Cloud Monitoring service is scheduled to be discontinued.

Accordingly, services whose monitoring metrics are linked in Cloud Monitoring will no longer be able to monitor resources through Cloud Monitoring after the service improvement work in November 2026.
After that, resource monitoring can be continuously performed through the ServiceWatch service released in October 2025.

To ensure smooth service usage, proceed with the migration work according to the service termination schedule below.

  1. Guide to applying resource-specific monitoring service

    • New Resources: Resources created after the July 2026 service improvement work are provided with default monitoring using the ServiceWatch service.
    • Existing resources: After the service improvement work in September 2026 We provide monitoring concurrently through the Cloud Monitoring service and the ServiceWatch service.
    • During the parallel operation period, we need to prepare for the Servicewatch transition *
      Performance and log data backup, settings configured by users linked with existing Cloud Monitoring (e.g. Check the event policy, etc., and perform tasks such as resetting the ServiceWatch service, and complete them.
  2. Cloud Monitoring Service Phased Termination Schedule Notice

    • Console menu termination (September 2026 service improvement work)
      • You cannot access the Cloud Monitoring Console through the Console menu; you can only connect via the separate URLs for each region listed below.
  • Service termination (service improvement work in November 2026)
    • All services of Cloud Monitoring, including the API, will be permanently discontinued.
      • After the service ends in November, Cloud Monitoring data cannot be viewed. * Complete the ServiceWatch migration within the parallel operation period**

For detailed information about ServiceWatch, please refer to the ServiceWatch 개요.

Vertica(DBaaS) Create

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

안내
  • Before creating the service, configure the VPC’s Subnet type as General.
    • If the subnet type is Local, the creation of the corresponding Database service is not possible.
  • When loading more than 2 TB of large data, backups may take a long time or the database’s performance may degrade. * To prevent this, it is necessary to consider operational aspects such as cleaning up unnecessary data or migrating old data to a statistical collection environment.
  • This service is provided on a Single-AZ basis.

Follow these steps to create Vertica(DBaaS).

  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 Create Vertica (DBaaS) button. 2. Go to the Create page.

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

    • Image and Version Selection area, select the required information.
      Category
      required status
      Detailed description
      Image versionRequiredProvide 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 PrefixEssentialThe server name where Vertica will be installed
      • must start with a lowercase English letter, and using lowercase letters, numbers, and special characters (-) be entered with 3 ~ 13 characters
      • Based on the server name, a postfix such as 001, 002 is appended to create the actual server name
      Cluster nameRequiredCluster name composed of servers
      • Enter using English letters, 3 ~ 20 characters
      • A cluster is a unit that groups multiple servers
      Number of nodesRequiredNumber of data nodes
      • Enter the number of nodes within the range of 1-10
      • If you configure the cluster by entering a Node count of 2 or more, you achieve high availability (High Availability)
      Service Type > Server TypeRequiredData node server type
      • Standard: Standard specification commonly used
      • High Capacity: Large-capacity server with 24 vCores or more
      Service Type > Planned ComputeSelectionStatus 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
      Service Type > Block StorageRequiredBlock 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 applied identically 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 purpose and 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 ConsoleselectionIf you select Use, you can configure the Node’s server type and Block Storage for cluster management and monitoring.
      Management Console > Server TypeRequiredSelecting a data node server type for cluster management and monitoring
      Management Console > Block StorageRequiredSelect the Block Storage type to be used for data nodes for cluster management and monitoring
      Network > Common SettingsRequiredNetwork settings where servers generated by the service are installed
      • Select when you want to apply the same settings to all installed servers
      • Select a pre‑created VPC and Subnet
      • Each server’s IP is generated automatically
      • Public NAT setting is only available in per‑server settings
      Network > Server-specific SettingsRequiredNetwork settings where servers generated by the service are installed
      • Select when you want to apply different settings for each installed server
      • Select a pre‑created VPC and Subnet
      • IP: Enter the IP for each server
      • Public NAT feature is available only when the VPC is connected to an Internet Gateway, if you check use, you can select a reserved IP from the VPC product’s Public IP pool. For more details, refer to Public IP 생성하기
      IP access controlSelectionService 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 (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 periodSelectionDB maintenance window
      • If you select Use, you can set the day, start time, and duration
      • The maintenance window is a feature that lets the user define the time slot for patch operations, and any patch work within that period must be performed directly by the user.
      • We ask you to set a maintenance window for the stable operation of the system, and we are not responsible for any issues arising from not setting it or from failure to perform tasks within the window.
      Table. Vertica(DBaaS) Service Configuration Items
    • Enter required database configuration information In this area, enter or select the required information.
      Required status
      Detailed description
      Database nameRequiredServer name applied during DB installation
      • must start with an English letter and be entered using English letters and numbers, 3 to 20 characters long
      Database usernameRequiredDB 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 viewed in the Console
      Database passwordRequiredPassword to use when accessing the DB
      • Include letters, numbers, and special characters ( excluded) and enter 8 to 30 characters
      Check database passwordRequiredRe-enter the same password to use for DB access
      Database Port numberRequiredPort number required for DB connection
      • Enter the DB port within the range 1200 ~ 65535
      Backup > UseSelectionNode backup usage
      • Use to select node backup retention period and backup start time
      Backup > Retention periodselectionBackup retention period
      • Select the backup retention period. Set the file retention period from 7 days to 35 days
      • Backup files incur additional charges based on size
      Backup > Backup Start TimeSelectionBackup start time
      • Select backup start time
      • The minutes when the backup runs (minutes) are set randomly, and the backup end time cannot be set
      ServiceWatch log collectionSelectionServiceWatch log collection status
      • Select Use to configure the ServiceWatch log collection feature
      • It is provided free of charge up to 5 GB for all services within the Account, and charges apply based on storage size for usage exceeding 5 GB.
      • When collected, log groups and log streams are created automatically, and they cannot be deleted until the resources are removed.
      • To prevent exceeding 5 GB, it is recommended to delete log data directly or shorten the retention period.
      License KeyRequiredEnter the Vertica License Key owned by the customer
      • If the entered license key is invalid, service creation is not possible
      DB LocaleRequiredSettings related to string handling, numeric/currency/date/time display formats, etc., to be used in Vertica (DBaaS)
      • The database is created with default settings based on the selected locale
      Time zoneRequiredStandard 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.
      Required
      Detailed description
      tagSelectionAdd 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.

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

Vertica(DBaaS) Check 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 consists of Details, Tags, Job History tabs.

Follow the steps below to view detailed information about the Vertica (DBaaS) service.

  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. Vertica(DBaaS) List Click the resource on the page to view detailed information. 3. Navigate to the Vertica(DBaaS) Details page.
    • Vertica(DBaaS) Details At the top of the page, status information and additional feature information are displayed.
      Detailed description
      The cluster is currently in a stopped state. It will be automatically started when a new job is submitted. If you want to start it manually, click the Start button. If you want to stop it, click the Stop button. If you want to delete the cluster, click the Delete button. If you want to edit the cluster, click the Edit button. If you want to view the cluster details, click the Details button. If you want to view the cluster logs, click the Logs button. If you want to view the cluster metrics, click the Metrics button. If you want to view the cluster configuration, click the Configuration button. If you want to view the cluster status, click the Status button. If you want to view the cluster health, click the Health button. If you want to view the cluster usage, click the Usage button. If you want to view the cluster cost, click the Cost button. If you want to view the cluster billing, click the Billing button. If you want to view the cluster usage history, click the Usage History button. If you want to view the cluster cost history, click the Cost History button. If you want to view the cluster billing history, click the Billing History button. If you want to view the cluster usage summary, click the Usage Summary button. If you want to view the cluster cost summary, click the Cost Summary button. If you want to view the cluster billing summary, click the Billing Summary button. If you want to view the cluster usage details, click the Usage Details button. If you want

      title: “Cluster Management” date: 2023-01-01 tags: [“cluster”, “management”]

      cluster:
        name: "my-cluster"
        status: "stopped"
        nodes: 3
        type: "m5.large"
      
      def start_cluster():
          # code to start the cluster
          pass
      ``` | Cluster status: **Creating**: Creating the cluster<ul><li>**Error**: Error occurred while creating the cluster</li></ul>If it persists, contact the administrator<ul><li></li></ul><ul><li>**Failed**: Failed during cluster creation<ul><li></li></ul>**Restarting**: Restarting the cluster</li></ul><ul><li>**Running**: Cluster is running normally</li></ul><ul><li>**Starting**: Starting the cluster</li></ul><ul><li>**Stopped**: Cluster is stopped</li></ul><ul><li>**Stopping**: Stopping the cluster</li></ul><ul><li>**Synchronizing**: Synchronizing the cluster</li></ul><ul><li>**Terminating**: Terminating the cluster</li></ul><ul><li>**Unknown**: Unknown cluster status</li></ul>If it persists, contact the administrator<ul><li></li></ul><ul><li>**Upgrading**: Upgrading the cluster<ul><li></li> |
      | Cluster control | Buttons to change the cluster state<ul><li>**Start**: Start a stopped cluster</li></ul><ul><li>**Stop**: Stop a running cluster</li></ul><ul><li>**Restart**: Restart a running cluster</li></ul> |
      | View more features | Cluster management buttons<ul><li>**Service status synchronization**: Real-time DB service status lookup</li></ul><ul><li>**Backup history**: When backup is configured, check whether the backup runs correctly and view its history</li></ul><ul><li>**Database recovery**: Recover the DB based on a specific point in time</li></ul> |
      | Service cancellation | Button to cancel the service |
      <div class="figure-caption">
        Table. Vertica (DBaaS) status information and additional features
      </div>
      
        
      

Detailed Information

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

Detailed description
Server InformationServer information configured in this cluster
  • Category: Server type (Vertica cluster nodes are shown as Data, and the Management Console is shown as Console)
  • Server Name: Server name
  • IP Port: Server IP and port
  • Availability Zone: Server creation location
  • Status: Server status
serviceService name
Resource TypeResource Type
SRNUnique resource ID in Samsung Cloud Platform
  • refers to the cluster SRN
Resource Nameresource name
  • means the cluster name
Resource IDUnique resource ID in the service
ConstructorUser who created the service
Creation Date/TimeService creation date and time
ModifierUser who edited the service information
Modification date and timeDate and time the service information was modified
Image/VersionInstalled DB image and version information
Cluster nameCluster name of the configured servers
Database nameServer name applied during DB installation
Database usernameDB user name
Planned ComputeResource status with Planned Compute configured
Maintenance periodDB Maintenance Period Status
  • If you need to set the maintenance period, click the Edit icon to configure
BackupBackup Configuration Status
  • If backup configuration is required, click the Edit icon to set it
ServiceWatch log collectionServiceWatch Log Collection Configuration Status
  • If log collection configuration is required, click the Edit icon next to Log Collection to configure
Managed ConsoleManaged Console resource status configured during DB installation
NetworkInstalled network information (VPC, Subnet)
IP access controlService access policy configuration
  • If you need to add or remove an IP, click the Edit icon to configure
Time zoneStandard time zone where the Vertica (DBaaS) DB will be used
LicenseVertica(DBaaS) license information
Server InformationData/Console server type, default OS, additional Disk information
  • If you need to modify the server type, click the Edit icon next to the server type to set it. Refer to the server type modification procedure at 서버 타입 변경하기
    • Modifying the server type requires a server reboot
  • If you need to expand storage, click the Edit icon next to the storage capacity to expand it. Refer to the storage expansion procedure at 스토리지 증설하기
  • If you need to add storage, click the Add Disk button next to the additional Disk to add it. Refer to the storage addition procedure at 스토리지 추가하기
Table. Vertica (DBaaS) detailed information items

tag

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

CategoryDetailed description
Tag listTag list
  • You can view the Key and Value information of the tag
  • Up to 50 tags can be added per resource
  • When entering a tag, you can search and select from the existing list of created Keys and Values
Table. Vertica(DBaaS) tag tab item

Job History

On the Vertica(DBaaS) List page, you can view the operation history of the selected resource.

CategoryDetailed description
Task History ListResource Change History
  • Operation Time, Resource ID, Resource Name, Operation Details, Event Topic, Operation Result, Operator Information Check
Table. Vertica (DBaaS) Job History Tab Detailed Information Items

Vertica(DBaaS) Managing Resources

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

Operation Control

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

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

  1. All Services > Data Analytics > Vertica(DBaaS) Click the menu. 1. Go to the Vertica(DBaaS) Service Home page.
  2. On the Service Home page, click the Vertica(DBaaS) menu. 2. Vertica(DBaaS) List Navigate to the page.
  3. Vertica(DBaaS) List On the page, click the resource you want to control. 3. Vertica(DBaaS) Details Navigate to the page.
  4. Check the Vertica (DBaaS) status and complete the change using the control button below.
    • Start: Vertica(DBaaS) service is installed on the server and the Vertica(DBaaS) service is running (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 check 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. Vertica(DBaaS) List Navigate to the page.
  3. Vertica(DBaaS) List Click the resource on the page to view the service status. 3. Navigate to the Vertica(DBaaS) Details page.
  4. Service status synchronization Click the button. 4. While it is being queried, the cluster changes to Synchronizing state.
  5. Once the query is complete, the status in the server information item is updated, and the cluster changes to Running state.

Change Server Type

You can change the configured server type.

Caution
  • If the server type is configured as Standard, it cannot be changed to High Capacity. * If you want to change to High Capacity, create a new service.
  • If you modify the server type, a server restart is required. * Please verify separately any software license modifications or software settings and their implementation due to server specification changes.

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. Vertica(DBaaS) List Go to the 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 The 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. Navigate to the Service Home page of Vertica (DBaaS).
  2. On the Service Home page, click the Vertica(DBaaS) menu. 2. Vertica(DBaaS) List Navigate to the page.
  3. Vertica(DBaaS) List On the page, click the resource to add storage. 3. Vertica(DBaaS) Details Go to the page.
  4. Click the Add Disk button at the bottom of the detailed information. 4. Additional Storage Request The popup window opens.
  5. Additional Storage Request In the popup window, after entering the purpose and capacity, click the Confirm button.

Expanding 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 increase storage capacity, follow the steps below.

  1. All Services > Data Analytics > Vertica(DBaaS) Click the menu. 1. Navigate to the Service Home page of Vertica (DBaaS).
  2. On the Service Home page, click the Vertica(DBaaS) menu. 2. Vertica(DBaaS) List Navigate to the page.
  3. On the Vertica(DBaaS) List page, click the resource to change the server type. 3. Vertica(DBaaS) Details Navigate to the 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 popup opens.
  5. Edit Additional Storage After entering the expansion capacity in the popup window, click the Confirm button.

Changing the Recovery DB instance type

After 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. All Services > Data Analytics > Vertica(DBaaS) menu, click it. 1. Navigate 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 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 perform the same function as a single DB.

Vertica(DBaaS) Terminate

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

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

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

1 - Backing up and restoring Vertica

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

Vertica(DBaaS) Backup

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

Configure Backup

For backup configuration of Vertica (DBaaS), refer to Vertica(DBaaS) 생성하기.

Follow the steps below to modify the backup settings of Vertica(DBaaS).

Caution
  • When a backup is configured, it runs at the designated time after the set schedule, and additional fees are incurred based on the backup volume.
  • If you change the backup setting to unused, backup execution stops immediately, and the stored backup data is deleted and can no longer be used.
  1. All Services > Data Analytics > Vertica(DBaaS) Click the menu. 1. Navigate 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 for which you want to configure a backup. 3. Vertica(DBaaS) Details Go to the page.
  4. Click the Edit button of the backup item. 4. Backup Settings The popup window opens.
  5. When configuring 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, deselect Backup Setting in the Use popup window and authenticate via the logged-in user’s mobile phone.
      Once user authentication is completed, the backup setting is disabled and backup execution stops.

Check backup history

안내
To set notifications for backup success and failure, you can configure them through the Notification Manager product. For a detailed usage guide on configuring notification policies, please refer to 알림 정책 생성하기.

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. Vertica(DBaaS) List Navigate to the page.
  3. On the Vertica(DBaaS) List page, click the resource to view the backup history. 3. Navigate to the Vertica(DBaaS) Details page.
  4. Click the Backup History button. 4. Backup History The 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 file

To delete the backup history, follow these steps.

Caution
Backup files cannot be restored after deletion. Please be sure to confirm that the data is unnecessary before deleting it.
  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. 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.

Vertica(DBaaS) Recover

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.

Caution
복구 수행을 위해서는 데이터 유형 Disk 용량과 적어도 동일한 용량이 필요합니다. If disk space is insufficient, recovery may fail.

To recover 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. Vertica(DBaaS) List Navigate to the page.
  3. Vertica(DBaaS) resource On the list page, click the resource you want to recover. 3. Vertica(DBaaS) Details Go to the page.
  4. Click the Database Recovery button. 4. Database(DBaaS) Recovery Go to the page.
  5. Database Recovery area, after entering the relevant information, click the Complete button.
    구분
    Required status
    Detailed description
    Copy the restored file the restored file the restored file the restored file the restored file the restored file the restored file the restored file the restored file.RequiredSet 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 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 PrefixRequired복구 DB 서버 이름
    • 영문 소문자로 시작하여 소문자, 숫자와 특수문자(-)를 사용하여 3~16자로 입력
    • 서버명 기반으로 001, 002와 같은 postfix 가 붙어 실제 서버명이 생성됨
    Cluster nameRequiredRecovery DB cluster name
    • Enter using English letters, 3 ~ 20 characters
    • A cluster is a unit that groups multiple servers
    Number of nodesSelectionNumber of data nodes
    • Set to be the same as the number of nodes configured in the original cluster
    Service Type > Server TypeRequiredRecovery DB server type
    • Standard: standard specifications commonly used
    • High Capacity: large-capacity server of 24 vCore or more
    Service Type > Planned ComputeSelectionPlanned Compute가 설정된 자원 현황
    • 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
    Service Type > Block StorageRequiredBlock 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 TypeRequiredManagement Console server type
    • After selecting Use, choose the storage purpose and capacity
    • Standard: standard specification commonly used
    • High Capacity: large-capacity server with 24 vCore or more
    Management Console > Block StorageRequiredBlock Storage settings used by the Management Console
    • Select Use and then select Default OS
    Database usernameRequiredDatabase username
    • Apply the same username set in the original cluster
    Database passwordRequiredDatabase password
    • Apply the same password set in the original cluster
    Database Port numberRequiredDatabase Port number
    • Apply the same Port number as set in the original cluster
    IP access controlSelectionService 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 (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 periodSelectionDB maintenance window
    • If you select Use, you can set the day of the week, start time, and duration
    • The maintenance window is a feature that allows the user to set the time slot for performing patch operations, and any patch tasks within that period must be carried out directly by the user.
    • We ask you to set a maintenance window for the stable operation of the system, and we are not responsible for any issues arising from not setting it or from failure to perform tasks within the window.
    License KeyRequiredEnter the Vertica License Key to recover
    • If the entered license key is invalid, the service cannot be created
    tagSelectionAdd Tag
    • Add Tag after clicking the button, enter or select Key, Value values
    Table. Vertica (DBaaS) recovery configuration items