--- title: "Restore" slug: "backup-restore" updated: 2026-09-17T09:18:17Z published: 2026-09-17T09:18:17Z canonical: "guide.ncloud-docs.com/backup-restore" stale: true --- > ## Documentation Index > Fetch the complete documentation index at: https://guide.ncloud-docs.com/llms.txt > Use this file to discover all available pages before exploring further. # Restore 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: ![backup-restore-screen01_ko](https://cdn.document360.io/6998976f-9d95-4df8-b847-d375892b92c2/Images/Documentation/backup-restore-screen01_en.png?sv=2026-02-06&spr=https&st=2026-10-27T19%3A51%3A15Z&se=2026-10-27T20%3A51%3A15Z&sr=c&sp=r&sig=zCvP97YwaOug7GQGF0w6DLpvJcSe9E7VvnnA7u0Xjkc%3D) | Component | Description | | --- | --- | | ① Menu name | Current menu name. | | ② Basic features | Available features when you first enter the **Restore** menu. - **[Set restoration]**: Click to [Set restoration job](/docs/en/backup-restore#%EB%B3%B5%EC%9B%90%EC%9E%91%EC%97%85%EC%84%A4%EC%A0%95). - **[Features and pricing information]**: Go to the Backup service overview page. - **[Download]**: Click to download the restoration job list. - **[Refresh]**: Reload the Restore interface. | | ③ Restoration job list | The list of restoration jobs that are set. - **Original resource (ID)**: Original resource and auto-assigned ID of the data to be restored. - **Target resource**: Target resource to store the restored data. - **Source storage**: Type of data to be restored. - **Restoration target**: Directory where the data to be restored is stored. - **Restoration time point**: Date and time when the restoration is performed. - **Status**: The current status of the restoration. - **Job**: Name of the original job for the data to be restored. - **Restoration location**: Directory where the restored data is to be saved. | ## Service limits If you restore data to another server with the Backup service, you have following service limits: | Service | Service limits | | --- | --- | | Common | - Requires backup agents to be installed on the server you want to restore. - If you are still connected to the existing DB, no restoration is performed. - Resources from different OS are not supported. | | File System | - No service limits. | | MSSQL | - Restoration can only be performed if the following information is the same: - OS type - DB version - Backup agent version | | MySQL | - Restoration can only be performed if the following information is the same: - OS type and version - DB version - Backup agent version - sa account and password | | PostgreSQL | - Restoration can only be performed if the following information is the same: - OS type and version - DB version - Backup agent version - Before restoring a database, all connections to the DB must be terminated by running the PostgreSQL DISCONNECT command. | ## 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](/docs/en/backup-job) and [Remote Backup](/docs/en/backup-remote). - 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. 1. From the NAVER Cloud Platform console, navigate to **Menu** > **All Services** > **Storage** > **Backup**. 2. Click the **Restore** menu. 3. Click **[Set restoration]**. 4. 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. 5. 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](/docs/en/backup-resource#%EB%A6%AC%EC%86%8C%EC%8A%A4%EC%83%9D%EC%84%B1) and [Install agent](/docs/en/backup-agent#%EC%97%90%EC%9D%B4%EC%A0%84%ED%8A%B8%EC%84%A4%EC%B9%98). - 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** and **PostgreSQL**: The **Restoration target** selected in step 5 is automatically set as the restoration location. 6. After confirming the settings, click **[Start 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 | | --- | --- | --- | | 7:214 | Occurs when 1 or more Linux backup target paths cannot be found. | Check the backup target paths, edit or exclude them, and then try again. | | 17:90 | Occurs when 1 or more Windows backup target paths cannot be scanned. | Check the backup target paths, edit or exclude them, and then try again. | | 19:2586 | Occurs when a backup is performed before the previous backup job finishes. | Check whether the previous backup job is completed, and then try again. | | 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 then try again. | | 23:82 | Occurs when recovery fails to overwrite protected files, 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, and 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](https://www.ncloud.com/support/question/service) with the log attached. | | 30:293 | Occurs when recovery of certain databases fails. | Make an inquiry to [Contact Support](https://www.ncloud.com/support/question/service) 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 then 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, and 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 then 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 then 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 then 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 then try again. | | 87:18 | Occurs when recovery of certain databases fails. | Make an inquiry to [Contact Support](https://www.ncloud.com/support/question/service) with the log attached. | | 87:19 | When an error occurs in recovering MySQL. | Check the backup log. - This may occur for various reasons, such as communication issues and a lack of MySQL server memory. | | 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 then try again. | | 94:17 | Occurs when recovery of certain databases fails. | Make an inquiry to [Contact Support](https://www.ncloud.com/support/question/service) with the log attached. | | 94:26 | Occurs when PostgreSQL service is down. | Make an inquiry to [Contact Support](https://www.ncloud.com/support/question/service) 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, and 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, and 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. |