The page has been translated by Gen AI.

DB Backup and Recovery

The user can set up a backup of MySQL(DBaaS) through the Samsung Cloud Platform Console and restore it with the backed-up file.

MySQL(DBaaS) Backup

PostgreSQL(DBaaS) provides a data backup feature based on its own backup command. It also provides an optimized backup environment for data protection and management through backup history checking and backup file deletion functions.

Setting up backup

The method of setting up a backup for MySQL(DBaaS) is described in MySQL(DBaaS) creation guide.

To modify the backup settings of the generated resource, follow these steps.

Caution

For stable backup, it is recommended to add a separate BACKUP storage or to sufficiently expand the storage capacity. Especially when the backup target data exceeds 100 GB and the data change is frequent, please secure additional storage equivalent to about 60% of the data capacity. For storage addition and expansion methods, please refer to the MySQL(DBaaS) Add Storage, MySQL(DBaaS) Expand Storage guides. If backup is set, backup is performed at the specified time after the set time, and additional fees are incurred depending on the backup capacity.
If the backup setting is changed to unset, the backup operation will be stopped immediately, and the saved backup data will be deleted and can no longer be used.

To set up backup, follow these steps.

All Services > Database > MySQL(DBaaS) menu is clicked. It moves to the Service Home page of MySQL(DBaaS).
Service Home page, click the MySQL(DBaaS) menu. Move to the MySQL(DBaaS) list page.
MySQL(DBaaS) list page, click the resource to set the backup. It moves to the MySQL(DBaaS) details page.
Click the Edit button of the backup item. The Backup Settings popup window opens.
If you set up a backup, click Use in the Backup Settings popup window, select the retention period, backup start time, and Archive backup cycle, and then click the Confirm button.
- If you want to stop the backup settings, uncheck Use in the Backup Settings popup window and click the OK button.

Check Backup History

Notice

To set up notifications for backup success and failure, you can set it up through the Notification Manager product. For detailed usage guidelines on notification policy settings, please refer to Creating a Notification Policy.

To view the backup history, follow these steps.

All Services > Database > MySQL(DBaaS) menu is clicked. It moves to the Service Home page of MySQL(DBaaS).
On the Service Home page, click the MySQL(DBaaS) menu. It moves to the MySQL(DBaaS) list page.
MySQL(DBaaS) list page, click the resource to check the backup history. Move to the MySQL(DBaaS) details page.
Click the Backup History button. The Backup History popup window opens.
Backup History popup window where you can check the backup status, version, backup start time, backup completion time, and capacity.

Delete backup files

Caution

Backup files cannot be restored after deletion. Please make sure to confirm that the data is unnecessary before deleting it.

To delete the backup history, follow these steps.

Click All Services > Database > MySQL(DBaaS) menu. It moves to the Service Home page of MySQL(DBaaS).
On the Service Home page, click the MySQL(DBaaS) menu. It moves to the MySQL(DBaaS) list page.
MySQL(DBaaS) list page, click the resource to check the backup history. Move to the MySQL(DBaaS) detail page.
Click the Backup History button. The Backup History popup window opens.
Backup History popup window, check the file you want to delete, and then click the Delete button.

Recovering MySQL(DBaaS)

In the event of a failure or data loss that requires restoration from a backup file, recovery is possible based on a specific point in time through the recovery function. When performing MySQL (DBaaS) recovery, a new server is created with the OS image at the initial provisioning time, the DB is installed with the version at the backup point in time, and the recovery proceeds with the DB configuration information and data.

Caution

To perform recovery, at least 2 times the capacity of the data type Disk capacity is required. If the disk capacity is insufficient, recovery may fail.

To restore MySQL(DBaaS), follow these steps.

All Services > Database > MySQL(DBaaS) menu is clicked. It moves to the Service Home page of MySQL(DBaaS).
On the Service Home page, click the MySQL(DBaaS) menu. It moves to the MySQL(DBaaS) list page.
MySQL(DBaaS) resource list page, click the resource you want to restore. It moves to the MySQL(DBaaS) details page.
Database Recovery 버튼을 클릭하세요. Database Recovery 페이지로 이동합니다.
Enter the corresponding information in the Database Recovery Configuration area, and then click the Complete button.

Classification	Necessity	Detailed Description
Recovery Type	Required	Set the point in time you want to recover Backup Point (Recommended): Recover based on the backup file. Select from the list of backup file points displayed in the list Custom Point: Recover to the desired point within the range of possible backup times. The recoverable period is from the initial backup start time to the current time, based on the Archive backup cycle setting value, and can be recovered up to 1 hour/30 minutes/10 minutes/5 minutes ago. Select the date and time you want to back up
Server name prefix	Required	Server name of the recovery DB Start with lowercase English letters, using lowercase letters, numbers, and special characters (`-`) to input 3 ~ 16 characters A postfix such as 001, 002 is attached based on the server name, and the actual server name is created
Cluster Name	Required	Cluster name of the recovery DB Enter in English, 3-20 characters Cluster is a unit that bundles multiple servers
Service Type > Server Type	Required	Server type where the recovery DB will be installed Standard: Standard specification commonly used High Capacity: High-capacity server with 24vCore or more (to be provided later)
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 Setting: Number of resources with Planned Compute set Coverage Preview: Amount applied by Planned Compute for each resource Create Planned Compute Service: Move to the Planned Compute service application page For more information, refer to Apply for Planned Compute
Service Type > Block Storage	Required	Recovery DB uses Block Storage settings Basic OS: Area where the DB engine is installed DATA: Storage area for table data, archive files, etc. The storage type set in the original cluster is applied in the same way Capacity can be entered in multiples of 8 in the range of 16 to 5,120 Additional: DATA, Archive, TEMP, Backup data storage area The storage type set in the original cluster is applied in the same way Only DATA, TEMP, and Archive purposes can be added in the recovery DB After selecting Use, enter the purpose and capacity of the storage To add storage, click the + button, and to delete, click the x button Capacity can be entered in multiples of 8 in the range of 16 to 5,120, and up to 9 can be created
Database username	required	Database username set in the original DB
Database Port number	required	Database Port number set in the original DB
IP Access Control	Select	IP address to access the recovery DB Enter in IP format (e.g., `192.168.10.1`) or CIDR format (e.g., `192.168.10.1/32`, `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 is selected to set the day, start time, and duration It is recommended to set the maintenance period for stable management of the DB, and patch work is performed at the set time, resulting in service interruption If not used, Samsung SDS is not responsible for any problems that occur due to non-application of patches.
tag	selection	add tag add tag button, click after Key, Value value input or selection

Fig. MySQL(DBaaS) Recovery Configuration Items

Managing DB Services

Setting up Read Replica