A Block Volume that Is Backed Up, to Another Region
Every tenancy ships Bronze, Silver and Gold policies and a volume follows one only through a separate assignment - the page reads Backup policy: none for the many never assigned. Assigns a policy to the volume it creates and refuses one without. Custom schedules add destination_region and retention lock, which Oracle policies lack: same-region backups are a copy of the failure.
Verification
Static-verifiedPassed: validated and lint-clean (provider-schema-validated for AWS/Azure/GCP; Terraform-language lint elsewhere).
Conformance
- Static validation (fmt · validate · tflint)
- Security scan clean (Checkov)
- Plan tests (mocked: validation rules · outputs)
Provenance
- SHA-256 checksum
- Signature (pending)
Functional
- Live test pending (no cloud run yet)
Last verified 2026-09-14 · how we verify
Use it from the registry
terraform · opentofumodule "block_volume" {
source = "www.iac-bazaar.com/iac-bazaar/oci-block-volume/oci"
version = "1.0.0"
}Needs a registry token from /account/tokens. The module itself is free; the account is what identifies you. Full setup: registry docs.
Inputs & outputs
Create a free account to read this module's contract
The declared contract - every input name, type, default and description, plus every output - is shown to signed-in accounts, not to anonymous visitors.
A free account sees the contract of every module in the catalogue. There is no subscription and nothing to buy - the modules are free to download, and they run under Vizier.
Documentation
oci-block-volume
A block volume with a backup policy that is assigned, and backups that leave
the region. Works with Terraform and OpenTofu (>= 1.6), oci provider
>= 8.0, < 9.0.
A backup policy that is assigned to nothing backs up nothing. Every OCI
tenancy ships Bronze, Silver and Gold, and a volume follows one only through
a separate assignment resource. The volume's page shows "Backup policy:
none" for the many that were never assigned, easy to miss among the green.
This module assigns one to the volume it creates - a custom policy defined
here, or an Oracle policy by name - and refuses a volume with none unless
accept_no_backups.
Oracle's policies stay in the region. A custom policy with
destination_region copies each backup to a second region, which is the
difference between a backup and a copy of the failure. A custom policy is
also where retention lock lives: locked backups cannot be deleted before
they expire, including by the account that made them. A custom policy
without a destination region needs accept_same_region_backups.
Encryption is always on; the question is whose key. Without kms_key_id
the volume uses an Oracle-managed key that protects the disk from the
datacenter and not from the tenancy. Refused without
accept_oracle_managed_key.
vpus_per_gb is the performance dial and the price. Auto-tune drops a
detached volume to Lower Cost by itself; raising a busy one needs
performance_auto_tune_max_vpus.
Verification
Static validation runs tofu fmt, init, validate, tflint and checkov.
This module has not yet had a live test, so it is published as statically
validated with its live test pending and does not carry the live-tested mark.
Usage code & full reference need an account
The complete copy-paste usage, the full input/output reference, and operational notes are free with an account - shown here and bundled in the download. Sign in and this section fills in.
- Usage
Related modules
oci-file-storage
Elastic NFSv3 file system with mount target, export options, snapshots and NSG-scoped access.
oci-object-storage-bucket
Bucket with versioning, lifecycle/auto-tiering, retention rules, replication and pre-authenticated request support.
ibm-block-volume
VPC backup policies match volumes by user tag, so a volume created without the tag sits silently outside the policy; encryption is provider-managed unless a root key CRN is given; and an attachment can delete the volume with the instance. The policy created with its plan and the volume tagged with the tag it matches (none by name), your key when given, the volume kept on instance deletion.
do-volume
Droplet backups copy the boot disk and nothing attached to it, so a database whose data lives on a volume is an empty server to the backup; there is no snapshot schedule for volumes either. A formatted, attached, regional volume with two outputs that say exactly that, so whatever consumes the module cannot assume a copy exists.
scaleway-block-volume
iops is required, is the price per GB, and cannot change after creation; snapshots exist as a resource you take and nothing on the platform schedules one; the volume is zonal and attaches from the server side. The tier validated to the two that exist, a baseline snapshot when asked, and an output that says no schedule exists.
hetzner-volume
delete_protection defaults to off, a deleted volume is gone at once with no soft delete and nothing to restore from, and server snapshots do not include volumes. Protection on and off only by name, a filesystem so automount works, exactly one of server or location, and an output that says volume snapshots do not exist.