Available in Classic and VPC
You can set restoration details in the Restore interface. Check out the service limits for data restoration.
Restore interface
The Restore interface includes the following components:

| Component | Description |
|---|---|
| ① Menu name | Current menu name. |
| ② Basic features | Available features when you first enter the Restore menu.
|
| ③ Restoration job list | The list of restoration jobs that are set.
|
Service limits
If you restore data to another server with the Backup service, you have following service limits:
| Service | Service limits |
|---|---|
| Common |
|
| File System |
|
| MSSQL |
|
| MySQL |
|
| PostgreSQL |
|
Set restoration job
You can select a time point of backup/remote backup to restore the backup/remote backup data at that point to the desired resource.
To set up a restoration job:
Note
- To perform a restoration job, there should be a history of complete backup/remote backup prior to setting up the job. For more information, see Job and Remote Backup.
- Data that has expired its retention period is deleted from storage, so it is not exposed when selecting a restoration target. Make sure to restore data before the retention period expires if needed.
- From the NAVER Cloud Platform console, navigate to Menu > Services > Storage > Backup.
- Click the Restore menu.
- Click [Set restoration].
- When the restoration setting interface appears, set the information of data to be restored and click [Next].
- Original resource: Select the original resource for the data to be restored.
- You can create resources by clicking [Create resource]. However, you cannot perform a restoration job on a resource immediately after its creation as it has no history of performing backup operations.
- Job: Select job of the data to be restored.
- Source storage: Select source storage of the data to be restored.
- Local storage: Storage where backup data is saved.
- Remote backup storage: Storage where remote backup data is saved.
- Restoration time point: Select time point for the job of the data to be restored.
- Most recent backup time point: The most recent backup or remote backup time point.
- Manual selection: You can select a specific time point of backup or remote backup.
- Restoration target: Select target for restoration.
- Data: Select restoration target from the File System list.
- DB: Select restoration target from the DB list.
- Original resource: Select the original resource for the data to be restored.
- After setting the information of the target resource to restore, click [Next].
- Region/Platform/Zone: Select region, platform, or zone to restore and save the data.
- If you have selected Classic, you can restore data to the server you created in VPC.
- If you have selected VPC, you cannot restore data to a server you created in Classic.
- Target resource: Select target resource to save the restored data to.
- The resources that have agents installed among the created resources are displayed in the dropdown menu. For more information on creating resources and installing agents, see Create resource and Install agent.
- If the backup type is DB, select the DB instance from the target DB instance list.
- Restoration location: Select a location to store restored data.
- Data: Select restoration location from the File System list.
- DB: Set the restoration location according to the DB type as follows:
- MSSQL: Enter the restoration location in text.
- MySQL, PostgreSQL: The Restoration target selected in step 5 is automatically set as the restoration location.
- Region/Platform/Zone: Select region, platform, or zone to restore and save the data.
- After confirming the settings, click [Begin restoration].
- Restoration is performed based on the settings, and the job is added to the list with the status of In progress. When the restoration is completed, the result is displayed under Status.
Error code
Error codes you can view in the reports and their descriptions are as follows:
| Error code | Cause | Solution |
|---|---|---|
| 23:2 | Occurs when the communication between the backup server and the client server fails. | Check the communication with the backup server (check firewall, etc.). |
| 23:10 | Occurs when the communication between the backup server and the client server fails. | Check the communication with the backup server (check firewall, etc.). |
| 23:12 | Occurs when the communication between the backup server and the client server fails. | Check the communication with the backup server (check firewall, etc.). |
| 23:47 | Occurs when the communication between the backup server and the client server fails. | Check the communication with the backup server (check firewall, etc.). |
| 23:68 | Occurs when the communication between the backup server and the client server fails. | Check the communication with the backup server (check firewall, etc.). |
| 23:70 | Occurs when there is not enough space in the recovery path. | Change to another path with enough space and recover. |
| 23:79 | Occurs when the recovery path does not exist. | Create the folder set as the recovery path and try again. |
| 23:82 | Occurs when overwriting protected files fails during recovery, causing them to be skipped. | Unprotect the file and resume recovery. |
| 23:120 | Occurs when the recovery path lacks permission to overwrite files during restoration. | Grant the permission to overwrite, then try again. |
| 23:131 | Occurs when the backup service does not work normally. | Check whether the backup service works normally. |
| 24:42 | Occurs when there is a communication error with the server to be recovered. | Check the communication (port) between the server to be recovered and the NCP backup server, and the backup service. |
| 30:130 | Occurs when recovery of certain databases fails. | Make an inquiry to Contact Support with the log attached. |
| 30:293 | Occurs when recovery of certain databases fails. | Make an inquiry to Contact Support with the log attached. |
| 30:332 | Occurs when the recovery account lacks permission or when there is an error in the account information. | Grant permission to the recovery account in SQL Server Management Studio (SSMS) and try again. |
| 30:337 | Occurs when the overwrite option is disabled and files are skipped. | Grant the recovery account permission to create and write to the database, then try again. |
| 30:422 | Occurs when the recovery account lacks permission or when there is an error in the account information. | Grant permission to the recovery account in SQL Server Management Studio (SSMS) and try again. |
| 30:424 | Occurs when the recovery account lacks permission or when there is an error in the account information. | Grant permission to the recovery account in SQL Server Management Studio (SSMS) and try again. |
| 30:436 | Occurs when the recovery account lacks permission or when there is an error in the account information. | Grant permission to the recovery account in SQL Server Management Studio (SSMS) and try again. |
| 30:486 | Occurs when the recovery account lacks permission or when there is an error in the account information. | Grant permission to the recovery account in SQL Server Management Studio (SSMS) and try again. |
| 87:18 | Occurs when recovery of certain databases fails. | Make an inquiry to Contact Support with the log attached. |
| 87:19 | When an error occurs in recovering MySQL. | Check the backup log.
|
| 87:26 | Occurs when MYSQL service is down. | Start the DB service and try again. |
| 87:34 | Occurs when there is no log backed up or when the log time point is after the backup. | Check the log backup and the log time point you selected upon recovery. |
| 87:74 | Occurs when the MySQL instance information is incorrect. | Need to check backup log files. |
| 87:86 | Occurs when the no-beep option is applied. | Annotate the no-beep option and try again. |
| 94:17 | Occurs when recovery of certain databases fails. | Make an inquiry to Contact Support with the log attached. |
| 94:26 | Occurs when PostgreSQL service is down. | Make an inquiry to Contact Support with the log attached. |
| 94:83 | Occurs when the account lacks permission to recover databases. | Grant the recovery account permission to create and write to the database, then try again. |
| 94:84 | Occurs when the database cannot be dropped in the overwrite option. | Grant the recovery account permission to database drop or drop the database manually, then try again. |
| 94:52 | When the connection remains in the DB, and it fails database drop. | End all access sessions of the DB and retry. |