HS3 for system integrators: how to bring S3 storage into your backup strategy (Synology, QNAP and public sector)

Synology and QNAP NAS remain the primary on-prem work point. HS3 becomes the remote copy for scheduled backup jobs: offsite cloud destination, data in Italy, service included in Host's ACN level 1 (QC1) qualification path.

• No proprietary Host agents. Endpoint, Access Key / Secret Key and bucket are enough.
• Same model as Veeam, scripts and S3 clients. If the technician already speaks S3, there is no new protocol to learn.
• Scalable. From 1 TB to hundreds of TB without redesigning the customer's architecture.

Synology — Hyper Backup

On Synology you typically use Hyper Backup with destination S3 Storage / Custom Server URL: versioned backup, schedule, integrity check and, if needed, client-side encryption. Endpoint, Access Key, Secret Key and bucket name are enough to open the job.

QNAP — HBS 3 (Hybrid Backup Sync)

On QNAP you use HBS 3: create a Storage Space of type Amazon S3 & S3 Compatible and send one-way backups to the bucket, with SSL and retention/rotation policies.

For the public sector — and for many private contracts that reuse the same perimeter — ACN Cloud rules and QC1 backup measures point, in short, to:

• Periodic backups with confidentiality, integrity and availability of copies
• At least one copy on media not permanently reachable from the primary system (protection from ransomware or NAS compromise)
• Encrypted transmission to the remote site
• Periodic restore tests (SLO at least yearly)
• Use of qualified cloud services when public-sector data or services transit or reside in the cloud

HS3 answers that model as follows: an offsite copy outside the NAS and the customer's local network; data stays in Italy (Host datacenters, with Turin ↔ Pisa geographic resilience); communications over HTTPS; data encrypted at rest on Host infrastructure and protected with Erasure Coding across nodes/disks; versioning and object lock (immutability) available against accidental or malicious deletes or changes. HS3 Object is among Host cloud services indicated as ACN-qualified, together with hosting, VPS and owned DC infrastructure.

Typical 3-2-1 scheme adapted to the NAS:

• Production data on the NAS
• One local copy (snapshot, second volume or second NAS)
• One remote copy on HS3 via Hyper Backup or HBS, on a night schedule
• Defined retention and rotation; where anti-ransomware is needed, immutability/lock and NAS-side encryption
• Restore test at least yearly, with reporting you can offer as a value-added service

For public bodies with “ordinary” data and QC1 duties, this is usually the simplest architecture to justify in a project and in a tender.

• Natural NAS upsell: you sell not only hardware, but compliant offsite backup in Italy.
• Native integration in tools technicians already know (Hyper Backup, HBS, Veeam, scripts).
• Predictable costs: clear TB pricing, no egress traffic fees and no API request fees — you pay for used space.
• Scale without redesign: from 1 TB to hundreds of TB.
• Flexible partner model: dedicated accounts per end customer, or one aggregated account with sub-buckets and separate keys.

The self-service plan starts at 1 TB for € 7.00 / month, with extra at € 0.0070 / GB beyond committed.

For partners:

• Silver 50 TB at € 300 / month (extra € 0.0060 / GB)
• Gold 150 TB at € 750 / month (extra € 0.0050 / GB)
• Platinum 300 TB at € 1,300 / month (extra € 0.0043 / GB)

1 commercial TB = 1,000 GB. Postpaid billing (1st of the month, period = previous month). On volumes and multi-year commitments (1–3–5 years), dedicated terms and Premium support are possible.

• Storage infrastructure uptime: 99.95% yearly (Internet reachability and nodes)
• Base support via ticket, Mon–Fri 7:00–19:00, on connectivity, HS3 parameters and read/write performance
• Activation from Customer Area / control.host.it, or commercial onboarding for partners

Product documentation: Cloud Object Storage HS3. Terms and SLA: CDF Object Storage HS3 (PDF), ODS 4 — SLA and policy, reseller terms.

• Map typical NAS average volumes (today and at 12 months)
• Choose the model: white-label/partner or per-customer accounts
• Define endpoint, bucket, keys and — where needed — object lock / versioning
• Configure Hyper Backup or HBS with schedule, retention and client-side encryption if required
• Plan the yearly restore test and reporting
• Align tender documentation: ACN qualification, ISO 27001, Italy localisation, DPA

For a technical-commercial discussion on a real customer portfolio, contact us: we provide endpoint, Synology/QNAP checklist and, if useful, a trial account.