Table: oci_core_volume_default_backup_policy - Query OCI Core Volume Default Backup Policies using SQL
The OCI Core Volume Default Backup Policy is a resource within Oracle Cloud Infrastructure (OCI) that provides automated backups of block volume data. The policy determines the frequency of automatic backups and the retention period for these backups. It is a crucial component of the OCI Block Volume service, helping to ensure data durability and protection.
Table Usage Guide
The oci_core_volume_default_backup_policy
table provides insights into the default backup policies associated with OCI Core Volumes. As a database administrator or DevOps engineer, use this table to explore policy-specific details, such as backup frequency and retention periods. This can be particularly useful for maintaining regular data backups, ensuring data durability, and planning disaster recovery strategies.
Examples
Basic info
Explore which default backup policies have been created and when, to gain insights into the history and management of your data backups. This can help in assessing the regularity and effectiveness of your backup strategies.
select id, display_name, time_createdfrom oci_core_volume_default_backup_policy;
select id, display_name, time_createdfrom oci_core_volume_default_backup_policy;
Get schedule info for each volume backup policy
This query is useful for gaining insights into the scheduling of volume backup policies. It helps in understanding the timing, frequency, and retention period of backups, which can assist in optimizing storage management and disaster recovery plans.
select id, display_name, s ->> 'backupType' as backup_type, s ->> 'dayOfMonth' as day_of_month, s ->> 'hourOfDay' as hour_of_day, s ->> 'offsetSeconds' as offset_seconds, s ->> 'period' as period, s ->> 'retentionSeconds' as retention_seconds, s ->> 'timeZone' as time_zonefrom oci_core_volume_default_backup_policy, jsonb_array_elements(schedules) as s;
select id, display_name, json_extract(s.value, '$.backupType') as backup_type, json_extract(s.value, '$.dayOfMonth') as day_of_month, json_extract(s.value, '$.hourOfDay') as hour_of_day, json_extract(s.value, '$.offsetSeconds') as offset_seconds, json_extract(s.value, '$.period') as period, json_extract(s.value, '$.retentionSeconds') as retention_seconds, json_extract(s.value, '$.timeZone') as time_zonefrom oci_core_volume_default_backup_policy, json_each(schedules) as s;
Query examples
Schema for oci_core_volume_default_backup_policy
Name | Type | Operators | Description |
---|---|---|---|
_ctx | jsonb | Steampipe context in JSON form. | |
display_name | text | A user-friendly name for volume backup policy. | |
id | text | = | The OCID of the volume backup policy. |
schedules | jsonb | The collection of schedules that this policy will apply. | |
sp_connection_name | text | =, !=, ~~, ~~*, !~~, !~~* | Steampipe connection name. |
sp_ctx | jsonb | Steampipe context in JSON form. | |
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 policy was created. | |
title | text | Title of the resource. |
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_default_backup_policy