The earlier replication guide covered sending ZFS snapshots to a second TrueNAS system, but not everyone has access to a second physical NAS for genuine off-site placement. TrueNAS Cloud Sync Tasks offers a built-in alternative, syncing data directly from your pools to cloud storage providers like Backblaze B2 or AWS S3 (covered in the earlier provider comparison guide) without needing any additional software.

What Are Cloud Sync Tasks?

Cloud Sync Tasks are TrueNAS Scale’s built-in feature for transferring data between your local pools and a wide range of cloud storage providers, using the open-source rclone project underneath its graphical interface. Rather than manually configuring rclone yourself, TrueNAS provides a guided setup directly within the web interface.

Cloud Sync vs Replication vs Restic

This series has now covered three genuinely different off-site backup approaches:

• TrueNAS Replication (covered in an earlier guide) – ZFS-native, block-level, most efficient specifically between two TrueNAS/ZFS systems
• Restic (covered in an earlier guide) – encrypted, deduplicated, file-level, run from any Linux server, not specific to TrueNAS
• Cloud Sync Tasks – TrueNAS’s built-in, GUI-driven approach specifically for syncing to commercial cloud storage providers, without needing a second physical TrueNAS system at all

For a TrueNAS-centric homelab wanting cloud backup without managing separate Restic configuration and scheduling, Cloud Sync Tasks offers the more integrated, GUI-native path.

Setting Up Cloud Credentials

1. Go to Credentials → Backup Credentials.
2. Click Add, selecting your provider (Backblaze B2, S3-compatible services, and numerous others are supported).
3. Enter your provider’s API credentials (access key and secret, following the same account setup covered in the earlier cloud provider comparison guide).

Creating a Cloud Sync Task

1. Go to Data Protection → Cloud Sync Tasks.
2. Click Add.
3. Select the Direction: Push (local to cloud, the typical backup direction) or Pull (cloud to local, useful for restoring).
4. Select the source dataset/path and the destination cloud credential and bucket/path.
5. Configure the Transfer Mode: Sync (destination exactly mirrors source, including deletions), Copy (adds/updates but never deletes from destination), or Move (removes from source after successful transfer — rarely appropriate for backup purposes).

Choosing the Right Transfer Mode for Backup Purposes

For genuine backup purposes specifically, Copy mode is often safer than Sync — Sync mode propagating an accidental local deletion to your cloud backup defeats much of the backup’s protective purpose, similar to the concern raised in the earlier Syncthing guide about sync not being equivalent to genuine backup.

Scheduling Cloud Sync Tasks

Configure a schedule matching your actual data change rate and how much data loss you’d accept between sync runs — daily is a reasonable default for most homelab data, though genuinely critical, frequently-changing data might warrant more frequent syncing.

Encrypting Data Before It Reaches the Cloud

Unlike Restic’s built-in client-side encryption (covered in the earlier guide), TrueNAS Cloud Sync Tasks doesn’t automatically encrypt data before upload by default — for genuinely sensitive data, either enable encryption options your specific cloud provider offers, or consider encrypting the source dataset itself at the ZFS level before syncing, ensuring data isn’t sitting unencrypted at the cloud provider regardless of their own security practices.

Monitoring Cloud Sync Task Status

TrueNAS shows task history and status directly in the web interface, and can be configured to send notifications (via the SMTP relay setup covered in an earlier guide) on task failure, ensuring a broken cloud sync doesn’t go unnoticed until you actually need to restore from it.

Bandwidth Considerations

For genuinely large datasets, initial cloud sync can take considerable time depending on your upload bandwidth — consider TrueNAS’s built-in bandwidth limiting options if you don’t want the initial sync saturating your connection during active homelab usage hours, scheduling the first large sync overnight if practical.

Restoring from Cloud Sync

Reverse the direction (Pull instead of Push) to restore data from your cloud storage back to a local dataset — worth testing periodically, following the same restore-testing principle emphasized throughout the backup guides in this series, confirming your cloud sync setup would actually work when a genuine restore is needed, not just when everything is working normally.

Combining Multiple Off-Site Strategies

Given the genuinely low ongoing cost of cloud storage at homelab scale, many users run both TrueNAS replication to a second physical system (for fast, complete disaster recovery) and Cloud Sync Tasks for specific critical datasets (for genuine geographic and provider diversity beyond any single physical location you control) — redundant off-site protection is rarely wasted effort for data that genuinely matters.

Final Thoughts

Setting up TrueNAS Cloud Sync Tasks provides a genuinely integrated, GUI-driven path to cloud-based off-site backup without needing separate tooling or a second physical TrueNAS system, directly leveraging the cloud provider comparison and backup principles covered throughout this series. For a TrueNAS-centric homelab, it’s often the most straightforward way to complete the off-site component of a proper 3-2-1 backup strategy specifically for your NAS data.