Scheduling Cloud Backups (CLI)
Before you can configure a cloud backup, you must configure a cloud target, see Configuring Cloud Backup and Restore Operations.
Use the following procedure to schedule cloud backups of a share.
Previously, users needed to manually generate a snapshot before performing a backup. To create incremental backups, they also needed to manage the parent snapshots and use these as the basis for subsequent backups.
To simplify the process, manual snapshot management is no longer required. Now, the system automatically generates a system snapshot before each backup, similar to replication and automated snapshots. Then, the system retains and reuses the system snapshots for incremental backups, eliminating manual snapshot tracking and maintenance.
Snapshots to be used for backups can be taken half-hourly, hourly, daily, weekly, or monthly and are named .cloud-<targetId>:<format>:<timestamp>. For example .cloud-eca5c5e2-79ee-4e62-8ad1-d1f56cfc02a8:zfs:20251120T185100UTC. The backup itself is named <pool>/<collection>/<project>/<share>.cloud<targetId>:<format>:<timestamp>. For example p0/local/default/f0@.cloud-eca5c5e2-79ee-4e41-8jd1-d1f56cfc02a8:zfs:20251120T185100UTC
By combining incremental backups with scheduled full backups, you can achieve a good compromise between backup speed, storage efficiency, and recovery reliability. The incremental field sets how many incremental backups occur between full backups in your schedule. For example, if the incremental value is set to 1, the system first performs a full backup (a complete copy of all data). The next scheduled backup is an incremental backup (only changes since the last full backup). After this incremental, the system performs another full backup on the next cycle, and the pattern repeats: full → incremental → full → incremental.