Skip to content

Blog

Backup and Vault: compliance does not stop at compute

Backups and secrets in Switzerland, VMware DR, nFADP and FINMA. Not HDS.

Hosting VMs in Switzerland is not enough if backups land on US object storage or secrets live in a US KMS. Hikube Backup as a Service and Vault as a Service stay in the Swiss tenant, in Geneva, Gland and Lucerne. That is often the hole in nFADP, FINMA and DORA files. Hikube provides the copy and the vault; the restore runbook and DPIA stay yours. We do not publish an RPO.

VMware DR: set backup before cutover

For a VMware exit, Backup as a Service replaces the Veeam/on-prem brick once VMs are imported (VMDK, QCOW2, ISO). Do not “turn on backup” on cutover day. The 10 to 20 VM pilot must test a restore, not only a green job. Retention and pilot RPO/RTO are mapped with an engineer, no public number is published. Hikube does not clone every Veeam plugin. S3 object storage remains if you keep a tool you operate. Path: the VMware exit. Product: managed backup.

Sync, async and RPO: do not mix the products

Hikube block storage is always geo-redundant (Geneva, Gland, Lucerne), with synchronous replication (real time) or asynchronous (improved performance). That is not the same RPO. That is not Backup as a Service. Backup as a Service is the managed copy for DR and audits. We publish neither IOPS nor RPO nor an SLA credit. Block detail: block storage.

FINMA, DORA, nFADP: evidence, not HDS

A green job is not evidence. FINMA and DORA files expect tested restores, written retention, a DR plan. nFADP: location, DPA, isolation. Hikube is not an HDS host and is not HDS-certified: that French frame is not the positioning. Finance: the finance and FINMA path. Swiss healthcare: healthcare. Hikube supports location and the copy; the memo and DPIA stay yours.

Vault: keys open the data

Data at rest includes the secrets that decrypt it. A Swiss cluster + Azure Key Vault or an AWS KMS is a weak argument. Vault as a Service aligns the vault with the same jurisdiction. Kubernetes, CI and GPU jobs plug in. Product: the secrets vault.

Velero is not Backup as a Service

Velero is an optional Kubernetes addon (cluster backup and restore). Backup as a Service targets instances and volumes, including VMware DR. Both can coexist. Do not mix them in a tender. Addons: the Kubernetes platform.

Who manages what?

Hidora SA operates the platform copy, the managed vault, the three DCs and FR/EN support. You keep runbook, tests, written retention, pilot RPO/RTO, DPIA and the outsourcing memo. Terraform integration in preparation: today, Hikube API and console.

S3 WORM is not Backup as a Service

Hikube S3 object storage has two WORM modes: governance and compliance. That is an object bucket, useful for archives and evidence. It is not the restore of a VM imported from VMware. Backup as a Service is the managed copy. Both can coexist in the tenant. S3 detail: S3 object storage.

How to start

14-day trial, no credit card. Put backup and a restore test in the pilot, not on cutover day. Terraform integration in preparation: today, Hikube API and console. Request a trial, or talk to an engineer.

Ready to run on 100% Swiss infrastructure?

14-day trial, no credit card. GPUs included.