Native backup on Oracle Cloud: three tiers, WORM immutability and self-thawing Archive

Cheap cloud storage is worthless if your backup software treats it as a dumb S3 bucket. NGBackup's OCI Object Storage driver is native — it speaks Oracle Cloud Infrastructure's own REST API and HTTP Signatures, not the S3-compatibility gateway — and it has been validated by Oracle. Every number below was measured against a live OCI tenancy in the São Paulo region.

Three storage tiers, one policy

Set StorageClass on the Cloud resource and the driver uploads to the matching tier — no second tool, no manual lifecycle scripts. All three were backed up and restored end-to-end against the live bucket, byte-for-byte identical:

• Standard — restore in ~0.1 s. Hot data.
• Infrequent Access — restore in ~0.1 s. Cheaper to store, same instant read.
• Archive — the cheapest tier. Frozen until restored; and here is the trick below.

Archive that thaws itself

OCI answers a read of a frozen Archive object with HTTP 409 NotRestored. Most tools stop there and make you file a restore request, wait, and come back. The NGBackup driver does it for you: it transparently issues the restore, polls the object's state until it is thawed, and re-reads — unattended. Measured end-to-end on a real Archive object: about 50 minutes, within Oracle's stated "up to ~1 hour" for Archive restore, and the returned bytes were identical to what was backed up. You start the restore and walk away; the driver waits, not you.

WORM immutability that won't lie to you

Immutability is the anti-ransomware backstop: an attacker who reaches your backups still can't delete or overwrite them. On OCI this is enforced by bucket retention rules, and the driver models it honestly:

• Set ObjectLock = Governance or Compliance with a retention period, and at connection time the driver verifies the bucket actually carries a retention rule at least that long. If it doesn't, the driver refuses to connect rather than silently uploading unprotected backups you'd only discover were mutable during an incident.
• Compliance additionally requires the rule to be compliance-locked; Governance accepts an unlocked rule. The driver checks the difference and refuses the mismatch.
• Under an active rule, OCI blocks both delete and overwrite — proven live: a locked object returned HTTP 403 RetentionRuleViolation on both delete and re-PUT, and the original content stayed intact.

That "refuse rather than pretend" behavior is the point. A backup tool that accepts an immutability setting the storage can't honor is worse than one without it — it gives you false confidence. NGBackup fails closed.

Configured in the web console

Every OCI field — region, namespace, bucket, tenancy/user/fingerprint/key, storage tier, ObjectLock and the Archive-restore tuning — is edited on the Cloud resource form in the NGBackup web console. No config files to hand-edit on the storage node.

Get NGBackup free or book a POC and put your backups on Oracle Cloud — native, immutable, and hands-free on Archive.

Figures measured July 2026 on a live OCI tenancy (sa-saopaulo-1). Archive restore latency depends on Oracle's service and varies up to ~1 hour.