Available in Classic and VPC
You can set up and edit a remote backup and delete an immediate remote backup job in the Remote Backup interface. See items you need to check before creating a remote backup job.
Remote backup is a redundancy feature that prevents data loss by securely replicating backup data to storage in a separate zone. By using remote backup feature, you can quickly recover original data even if the backup data store fails or data is lost.
Remote Backup interface
The Remote Backup interface includes the following components:
| Component | Description |
|---|---|
| ① Menu name | Current menu name and number of remote backup jobs created. |
| ② Basic features | Available features when you first enter the Remote Backup menu.
|
| ③ Management features | Features to manage created remote backup jobs.
|
| ④ Remote backup job list | The list of created remote backup jobs.
|
| ⑤ Search bar and filter | You can search for remote backup by name, and filter through the job list by the remote backup job cycle type. |
Items to check before creating a remote backup job
Before creating a remote backup job, you need to check the remote backup targets by remote backup time, data retention period, and the pricing for the remote backup job as follows:
Initial remote backup target
Even if the retention period of the remote backup target has expired, remote backup is still performed and network transfer charges apply.
- Full and incremental backup: You can select all full and incremental backup data which retention period has not expired at the time of setting up the remote backup job as the remote backup target.
If you perform the initial remote backup job on incremental backup data whose retention period has not expired, the immediately preceding incremental backup data of that incremental backup and the original full backup data are included as the remote backup target, regardless of whether the retention period has expired.
- Full backup: Among the backup data since the creation of the remote backup job, the most recently performed full backup is selected as the remote backup target.
In the following cases, the remote backup job is performed as scheduled, but the volume of remote backup is 0 and not actually occur:
- The start date of the initial remote backup job is earlier than the start date of full backup for original data. (Remote backup to be performed as usual from the next job.)
- The target backup data is the same as the most recently performed full backup data.
Remote backup targets after initial remote backup
- Full and incremental backup: All backup data created since the last remote backup until the next remote backup is selected as the remote backup target.
- Full backup: Among the data since the last remote backup until the next remote backup, the most recently performed full backup data is selected as the remote backup target.
Retention period for backup data of remote backup target
Regardless of the retention period, the backup data is stored until the remote backup is completed. However, you cannot use this backup data to recover data after the expiration date, and there will be no charge for it.
Retention period of the remote backup data
The backup retention period of the remote backup data is set at the execution time of the original backup as the standard, not the execution time of the remote backup.
The following is an example of how the retention period of remote backup data is set:
- Original backup: Retention period - 7 days
- Execution date: January 1, 2026 00:00
- Expiration date: January 7, 2026 23:59
- Remote backup: Retention period - 14 days
- Execution date: January 5, 2026 00:00
- Expiration date: January 14, 2026, 23:59 (14 days from the original backup date and time)
Remote backup pricing criteria
You will be charged from the time the remote backup job is performed until the remote backup data retention expiration date.
If the original data changes frequently and incremental backups increase, the volume of remote backup jobs also increases. To avoid being charged unexpectedly for remote backup, constantly monitor the volume of data change.
Remote backup job scenarios (examples)
The target backup data for remote backup may vary depending on the time when the remote backup job is created and started. The following are example scenarios of remote backup job by remote backup target:
- Original backup schedule: Perform full backup once a week and daily for incremental backup.
| Backup cycle | Backup method | Start day | Start time | Retention period |
|---|---|---|---|---|
| Weekly | Full | Every Friday | AM 10:00 | 7 days |
| Daily | Incremental | Every day | AM 08:00 | 7 days |
The backup data created according to the backup schedule is as follows:
- Remote backup schedule
- Remote backup scheduled date: April 16
- Retention period: 14 days
| Remote backup cycle | Start day | Start time |
|---|---|---|
| Weekly | Every Wednesday | PM 11:00 |
If "Full and incremental backup" is selected for remote backup target
- First remote backup target
- As of April 16, the remote backup scheduled date, every full backup and incremental backup file created before that date that has not expired its retention period is targeted for remote backup.
- If the first target file for remote backup is an incremental backup file, then the full backup that it is based on and any subsequent incremental backups are also included as targets for remote backup (regardless of the expiration of retention period).
- When the remote backup task schedule runs, all full and incremental backup files among the above targets whose retention periods have not expired are backed up remotely.
- Remote backup targets after initial remote backup: All backup data created since the last remote backup task until the next remote backup task is selected as the remote backup target.
Remote backup target files depending on the remote backup settings are as follows:
If "Full backup" is selected for remote backup target
- First remote backup target
- The most recent full backup file that was created after April 16, the remote backup scheduled date, that has not expired its retention period is targeted for remote backup.
- If there is no full backup file created at the time the remote backup is performed, or if there are no full backup file created during the week (week start: Sunday), the file cannot be subject to remote backup.
- Remote backup targets after initial remote backup: Among the data since the last remote backup until the next remote backup, the most recently performed full backup data is selected as the remote backup target.
Remote backup target files depending on the remote backup settings are as follows:
If "Full backup" is selected and immediate backup file outside of the backup schedule created
Remote backup target files depending on the remote backup settings are as follows:
If the remote backup cycle is set to "Daily", only scheduled backups are subject to remote backup.
In this case, immediate backup files created outside the backup schedule are excluded from remote backup.
Create remote backup job
You can create remote backup jobs for backup data redundancy. To create a remote backup job:
- In the NAVER Cloud Platform console, navigate to Menu > All Services > Storage > Backup > Remote Backup.
- Click [Set remote backup].
- When the remote backup setting interface appears, set the information of the remote backup job, then click [Next].
- Remote backup name: Enter a unique name for managing the remote backup job.
- The name should start with an English letter and be between 3-30 characters, consisting of lowercase English letters, numbers, and hyphens (-).
- Job: Select the job for remote backup target.
- Zone: Zone where remote backup data will be saved.
- Connecting storage: Name of the storage created in the selected zone.
- Remote backup target: Select target to perform remote backup.
- Full and incremental backup: Perform remote backup for both full and incremental backup data.
- Full backup: Perform remote backup for full backup data only.
- Retention period: Set the period for storing the remote backup data.
- The default retention period is 7 days and can be set from a minimum of 7 days to a maximum of 365 days, depending on your remote backup cycle. Also, the retention period must be set to at least 2 times as long as your remote backup cycle. For more information on the retention period, see Retention period for remote backup data.
- Remote backup cycle: Select the cycle to perform the remote backup job.
- Daily: Set a Start time to perform daily remote backup jobs.
- Weekly: Set the Start day and Start time for performing weekly remote backup jobs.
- Monthly: Select the Schedule criteria for performing monthly remote backup jobs, select the Start day or Start date based on the selected schedule criteria, then set the Start time.
- For the Start day, you can select the first or last week.
- If you select the Start date as the Last day of the month, the backup job runs on that day.
- If there's no selected Start date in the month, the remote backup job does not run.
- Example: If you set the Start date to the 31st, the remote backup job is performed in January, March, May, July, August, October, and December.
CautionIf the target backup data is the same as the most recently performed full backup data, the volume of remote backup is set to 0 for the job. To avoid this, when selecting remote backup cycle as "Weekly", you must set the different days for the original backup schedule and the remote backup.
- Remote backup name: Enter a unique name for managing the remote backup job.
- Check the content of the notification popup, then click [OK].
- After confirming the settings, click [Start].
- The remote backup job appears in the list with the status Creating, and the status changes to Created when the settings are finished.
Edit remote backup job
You can edit the retention period of the remote backup data, the remote backup cycle, and the start time of the remote backup. To edit the information of a remote backup job:
- In the NAVER Cloud Platform console, navigate to Menu > All Services > Storage > Backup > Remote Backup.
- In the remote backup list, click to select the remote backup job to edit, then click [Edit].
- When the Edit remote backup popup appears, apply the modifications, then click [Edit].
- The status of the remote backup job is displayed as Editing, and changes to Created when the editing is complete.
Remote backup targets cannot be edited. If you need to edit this, you must create a new remote backup job.
- (You cannot change the settings of a remote backup job that was only performed on full backup to include full and incremental backups, or change a remote backup job that was only performed on full and incremental backups to include only full backup.)
Immediate backup for remote backup job
You can perform immediate backup for the remote backup data. To perform immediate backup:
- In the NAVER Cloud Platform console, navigate to Menu > All Services > Storage > Backup > Remote Backup.
- In the remote backup list, click to select the remote backup job to perform immediate backup, then click [Immediate backup].
- Click [Run].
- The immediate backup is performed.
Delete remote backup job
To delete a remote backup job:
Deleting a remote backup job also deletes the remote backup data by that job, regardless of its retention period. If necessary, Restore the remote backup data to another resource first using the restoration feature.
- In the NAVER Cloud Platform console, navigate to Menu > All Services > Storage > Backup > Remote Backup.
- In the remote backup list, click to select the remote backup job to delete, then click [Delete].
- View the Delete job popup, click the check box, then click [Delete].
- The status of the remote backup job is displayed as Deleting and disappears once it is deleted completely.