Table: oci_core_volume_backup - Query OCI Core Volume Backups using SQL
Oracle Cloud Infrastructure (OCI) Core Volume Backup is a service that provides automated backups of block volumes. The backups are crash-consistent and can be used to create new volumes or restore existing volumes. This service ensures data durability and protection for your OCI resources.
Table Usage Guide
The oci_core_volume_backup
table provides insights into volume backups within OCI Core. As a system administrator, explore backup-specific details through this table, including backup size, status, and associated metadata. Utilize it to uncover information about backups, such as those that are available, the ones that are in progress, and the verification of backup policies.
Examples
Basic info
Explore which backups of your core volumes in Oracle Cloud Infrastructure have been created, along with their source type and current lifecycle state. This can help you manage and track your backups, ensuring data safety and availability.
select id, display_name, volume_id, source_type, time_created, type, lifecycle_state as statefrom oci_core_volume_backup;
select id, display_name, volume_id, source_type, time_created, type, lifecycle_state as statefrom oci_core_volume_backup;
List manual volume backup
Explore which volume backups have been manually created. This can be useful for auditing purposes, ensuring that backups are being created as intended and identifying any potential issues with backup procedures.
select id, display_name, source_type, time_created, type, lifecycle_state as statefrom oci_core_volume_backupwhere source_type = 'MANUAL';
select id, display_name, source_type, time_created, type, lifecycle_state as statefrom oci_core_volume_backupwhere source_type = 'MANUAL';
Schema for oci_core_volume_backup
Name | Type | Operators | Description |
---|---|---|---|
_ctx | jsonb | Steampipe context in JSON form. | |
compartment_id | text | = | The OCID of the compartment in Tenant in which the resource is located. |
defined_tags | jsonb | Defined tags for resource. Defined tags are set up in your tenancy by an administrator. Only users granted permission to work with the defined tags can apply them to resources. | |
display_name | text | = | A user-friendly name for the volume backup. |
expiration_time | timestamp with time zone | The date and time the volume backup will expire and be automatically deleted. | |
freeform_tags | jsonb | Free-form tags for resource. This tags can be applied by any user with permissions on the resource. | |
id | text | = | The OCID of the volume backup. |
kms_key_id | text | The OCID of the Key Management key which is the master encryption key for the volume backup. | |
lifecycle_state | text | = | The current state of a volume backup. |
region | text | The OCI region in which the resource is located. | |
size_in_gbs | bigint | The size of the volume, in GBs. | |
size_in_mbs | bigint | The size of the volume in MBs. | |
source_type | text | Specifies whether the backup was created manually, or via scheduled backup policy. | |
source_volume_backup_id | text | = | The OCID of the source volume backup. |
sp_connection_name | text | =, !=, ~~, ~~*, !~~, !~~* | Steampipe connection name. |
sp_ctx | jsonb | Steampipe context in JSON form. | |
system_tags | jsonb | System tags to volume by the service. | |
tags | jsonb | A map of tags for the resource. | |
tenant_id | text | =, !=, ~~, ~~*, !~~, !~~* | The OCID of the Tenant in which the resource is located. |
tenant_name | text | The name of the Tenant in which the resource is located. | |
time_created | timestamp with time zone | The date and time the volume backup was created. | |
time_request_received | timestamp with time zone | The date and time the request to create the volume backup was received. | |
title | text | Title of the resource. | |
type | text | The type of a volume backup. | |
unique_size_in_gbs | bigint | The size used by the backup, in GBs. | |
unique_size_in_mbs | bigint | The size used by the backup, in MBs. | |
volume_id | text | = | The OCID of the volume. |
Export
This table is available as a standalone Exporter CLI. Steampipe exporters are stand-alone binaries that allow you to extract data using Steampipe plugins without a database.
You can download the tarball for your platform from the Releases page, but it is simplest to install them with the steampipe_export_installer.sh
script:
/bin/sh -c "$(curl -fsSL https://steampipe.io/install/export.sh)" -- oci
You can pass the configuration to the command with the --config
argument:
steampipe_export_oci --config '<your_config>' oci_core_volume_backup