Settings
You can edit task settings when creating a backup task, or edit it after a backup task is created.
Notes:
- Names of tasks may include 1 to 32 Unicode characters, but cannot contain the following characters:
! " # $ % & ' ( ) * + , / : ; < = > ? @ [ ] \ ^ ` { } | ~
- Client-side encryption cannot be disabled once the task is set up, nor can the password be changed.
- Setting of backup data compression cannot be changed once the task is set up.
- If you select Enable client-side encryption, your password/encryption key is required to restore data in this task. Losing the password/encryption key will cause permanent data loss.
- Backup tasks are not resumable if interrupted. Make sure the network connection is stable and the total data size fits the bandwidth to reduce possible interruptions.
To rotate versions:
Backup rotation is a version management mechanism. It helps to manage backup versions by automatically deleting older, unnecessary versions and potentially freeing up storage space. You can enable this function at Task Settings or configure it when you create a backup task.
- Select the desired backup task on the left panel, and click Edit or Settings > Task Settings.
- Select Enable backup rotation, and choose the desired rotation mode:
- From the earliest versions: Delete the earliest backup versions when the available versions exceed the defined number.
- Smart Recycle: The system will retain every backup version until the specified number of versions is exceeded. When rotation is triggered, the system will first rotate the versions that do not meet any of the conditions; if all the existing versions meet the conditions below, the system will rotate the earliest version:
- Hourly versions from the past 24 hours: Keep the earliest version created each hour.
- Daily versions from the past 1 day to 1 month: Keep the earliest version created each day.
- Weekly version older 1 month: Keep the earliest version created each week.
- Customized retention policy: You can add up to seven rules to retention period and versioning interval according to your needs. For example, setting up a one-month retention period and one-week versioning interval would indicate that one backup version will be retained per week and that four backup versions will be retained in total.
- Specify the maximum number of versions. When the version number exceeds this number, the oldest version is rotated.
- If you have configured a repeated backup schedule at Schedule, you can preview how your backup versions will be retained and the earliest recovery point in the timeline.
- Click OK to save the settings.
Note:
- Locked versions will never be removed.
- Only multi-version backup tasks provide version rotation.
- Version rotation is not supported in DSM 5.1 or below.
- Rotation will be triggered right after the setting is changed or the backup task is completed.
- Locked versions are excluded when calculating the maximum number of versions.
To perform file-level deduplication:
File-level deduplication is supported by Hyper Backup on DSM 6.1 or above. In addition to performing cross-version deduplication, Hyper Backup can also perform data deduplication when files are being renamed or copied to enhance storage efficiency.
Note:
- Deduplication of copied and renamed files is supported by models equipped with 128MB RAM or above, and by Hyper Backup on DSM 6.1 or above. File-level deduplication is not supported by versions prior to Hyper Backup 2.0.0 and Hyper Backup Vault 2.0.0.
- Deduplication of copied files is not performed on files with data size of less than 1KB.
- Deduplication of copied files can detect most of the files copied between different versions. However, not all of the copied files can be identified. Deduplication may vary according to your data settings.