abbieleigheventsstyling.com → data → cloud computing storage → synology to cloud backup
Posted on by Alan Ingram

Synology to cloud backup

Synology NAS unit connected to network with cloud icon overlay showing data flowing to remote server

Synology to cloud backup is a feature within Synology DiskStation Manager (DSM) that automatically replicates selected data from a Synology NAS to a remote cloud storage provider, enabling offsite data protection and disaster recovery. This process runs on a schedule or triggers based on file changes, ensuring consistent backups without manual intervention.

The core function of Synology to cloud backup is to move data from local storage on a Synology NAS to a cloud service such as Google Cloud Storage, Amazon S3, or Microsoft Azure. This enables users to maintain a secure copy of critical files beyond their physical premises, reducing risk from hardware failure, theft, or natural disasters. The feature integrates with DSM's Backup & Replication tool and supports encryption both during transfer and at rest.

According to Synology's official documentation, the feature supports over 20 cloud providers through standardized protocols like S3-compatible APIs. Backups can be configured to run hourly, daily, or weekly, with options to retain multiple versions using snapshots. For example, a user with a DS223j NAS can set up a backup job to sync 1.2 TB of media files to Google Cloud Storage every 12 hours, with retention set to keep the last 30 versions.

How it works

Synology to cloud backup operates via the Backup & Replication application in DSM. Once enabled, users select a source folder on the NAS-such as a shared folder containing financial records or project assets-and designate a cloud destination. The system then creates a scheduled task that checks for changes and uploads modified or new files incrementally.

During upload, data is compressed and encrypted using AES-256 encryption before leaving the NAS. The encryption key can be managed locally or stored in a cloud-based key management service. This helps even if the cloud provider experiences a breach, data remains inaccessible without the key. Synology recommends using a dedicated backup user account with limited permissions to reduce attack surface.

For large datasets, incremental updates minimize bandwidth usage. A test conducted by TechRadar in 2023 showed that backing up 500 GB of video files from a Synology DS1823+ to Google Cloud Storage consumed 1.8 Gbps average bandwidth over 4 hours, with 93% of data transferred as delta updates after the initial sync.

Supported providers and configuration types

Synology to cloud backup supports many cloud services. The following table outlines major compatible providers, their access methods, and recommended use cases:

Provider Access Method Use Case Encryption Support
Google Cloud Storage OAuth 2.0 + Service Account High availability, global access Yes (client-side and server-side)
Amazon S3 Access Key/Secret Key Cost-effective, mature infrastructure Yes (AES-256)
Microsoft Azure Blob Storage Shared Access Signature (SAS) Enterprise environments with Azure integration Yes (TLS + client-side encryption)
Backblaze B2 API Key Low-cost long-term archival Yes (client-side encryption optional)

Each provider requires unique credentials and settings. For example, setting up Google Cloud Storage involves creating a service account in the Google Cloud Console, granting it "Storage Admin" role, and downloading a JSON key file to import into DSM. The process takes under 15 minutes and is documented in detail on the Synology Knowledge Center.

A common mistake is assuming all providers support versioning. Only those with native versioning-like AWS S3 and Google Cloud Storage-retain deleted or overwritten files. Backblaze B2 does not, requiring users to enable "versioning" explicitly in the bucket settings. Failing to do so results in permanent data loss upon overwrite.

Real-world use cases and limitations

In a small business environment, a marketing agency used Synology to cloud backup to protect client campaign assets. They configured a daily backup of a 750 GB shared folder to Google Cloud Storage using a 100 Mbps internet connection. Initial sync took 36 hours due to full data transfer. Subsequent backups averaged 2.1 hours and used 1.4 TB of outbound data monthly.

Performance varies based on internet speed and data size. A 2022 benchmark by PCMag found that syncing 1 TB of data over a 50 Mbps connection took 18 hours, while a 1 Gbps connection reduced the time to 3.5 hours. Bandwidth throttling during peak hours can extend this further.

One non-obvious limitation is that Synology to cloud backup does not support cross-platform file attributes like Windows NTFS ACLs or macOS extended attributes. These metadata elements are stripped during transfer, which can affect restore accuracy in mixed OS environments. Users relying on fine-grained access control must reapply permissions manually after restoration.

During a test in 2023, a user reported that restoring a 200 GB dataset from Google Cloud Storage took 14 hours due to throttled download speeds. The issue was resolved by adjusting the backup job's "maximum concurrent downloads" setting from 4 to 12, which improved throughput by 62%. This highlights the importance of tuning parameters beyond default settings.

Common misconceptions and corrections

Many assume Synology to cloud backup provides real-time synchronization. It does not. The process runs on a schedule-typically every 15 minutes to 24 hours-meaning changes may take up to the interval to appear in the cloud. For near-real-time needs, users should consider Synology's Hyper Backup with continuous replication to a remote NAS instead.

Another misconception is that cloud backup replaces full system imaging. It does not. While Synology to cloud backup protects individual files and folders, it does not capture system state, boot partitions, or application configurations. For complete system recovery, users must combine it with a full system backup using DSM's System Backup or a third-party tool like Veeam.

Finally, some believe that encrypting data at rest in the cloud eliminates the need for client-side encryption. This is incorrect. Cloud providers have administrative access to data unless encrypted before upload. Synology recommends enabling client-side encryption in the backup job settings to ensure data confidentiality even if the cloud provider is compromised.

After setting up a Synology to cloud backup job for a home office, I observed that the initial sync failed twice due to a misconfigured firewall rule blocking outbound port 443. After correcting the rule, the job completed successfully in 12 hours. This experience reinforced the importance of checking network policies before deployment.

When choosing a provider, compare costs. Google Cloud Storage charges $0.02 per GB/month for standard tier, while Backblaze B2 is $0.005 per GB/month. Over 1 TB, this difference amounts to $15 per month. For long-term storage, Backblaze B2 offers better value, though with less global redundancy.

Synology to cloud backup is not a substitute for a complete disaster recovery plan. It is a critical component of one. When paired with regular testing, proper access controls, and monitoring, it delivers reliable offsite protection for valuable data.


Related Posts