1z0-1072-22 Exam Dumps - Oracle Cloud Solutions Infrastructure Questions and Answers

Database backups can fail for various reasons. Typically, a backup fails because either the database host cannot access the object store, or there are problems on the host or with the database configuration.

First need to determining the Problem

In the Console, a failed database backup either displays a status of Failed or hangs in the Backup in Progress or Creating state. If the error message does not contain enough information to point you to a solution, you can use the database CLI and log files to gather more data. Then, refer to the applicable section in this topic for a solution.

Database Service Agent Issues

Your Oracle Cloud Infrastructure Database makes use of an agent framework to allow you to manage your database through the cloud platform. Occasionally you might need to restart the dcsagent program if it has the status of stop/waiting to resolve a backup failure.

Object Store Connectivity Issues

Backing up your database to Oracle Cloud Infrastructure Object Storage requires that the host can connect to the applicable Swift endpoint. You can test this connectivity by using a Swift user.

Host Issues

One or more of the following conditions on the database host can cause backups to fail:

- Interactive Commands in the Oracle Profile

- The File System Is Full

- Incorrect Version of the Oracle Database Cloud Backup Module

- Changes to the Site Profile File (glogin.sql)

Database Issues

An improper database state or configuration can lead to failed backups.

- Database Not Running During Backup

- Archiving Mode Set to NOARCHIVELOG (When you provision a new database, the archiving mode is set to ARCHIVELOG by default. This is the required archiving mode for backup operations)

- Stuck Database Archiver Process and Backup Failures

- Temporary Tablespace Errors

- RMAN Configuration and Backup Failures

- RMAN Retention Policy and Backup Failures

- Loss of Objectstore Wallet File and Backup Failures

TDE Wallet and Backup Failures

- Incorrect TDE Wallet Location Specification

- Incorrect State of the TDE Wallet

- Incorrect Configuration Related to the TDE Wallet

- Missing TDE Wallet File

As this is not new provisioned database and already in the ARCHIVELOG , regular backups of DB system to OCI object storage in places, so the best answers are,

- Ensure that your database host can connect to the OCI object storage

- Restart the database service agent

Setting Up a Remote Peering

Create the RPCs: Each VCN administrator creates an RPC for their own VCN's DRG.

Share information: The administrators share the basic required information.

Set up the required IAM policies for the connection: The administrators set up IAM policies to enable the connection to be established.

Establish the connection: The requestor connects the two RPCs (see Important Remote Peering Concepts for the definition of the requestor and acceptor).

Update route tables: Each administrator updates their VCN's route tables to enable traffic between the peered VCNs as desired.

Update security rules: Each administrator updates their VCN's security rules to enable traffic between the peered VCNs as desired.

You can filter results by request actions to zero in on only the events with operations that interest you. For example, say that you only want to know about instances that were deleted during a specific time frame. Select a delete request action filter to see only the events with delete operations

All data is encrypted at rest. and In-transit encryption provides a way to secure your data between instances and mounted file systems using TLS v. 1.2 (Transport Layer Security) encryption.

File Storage service supports the AUTH_UNIX style of authentication and permission checking for remote NFS client requests.

References:

Terraform configuration files can use either of two formats: Terraform domain-specific language (HashiCorp Configuration Language format [HCL]), which is the recommended approach, or JSON format if the files need to be machine-readable.

References:

“In this case, your security rules might not include the IP range for the source of the health check requests. You can find the health check source IP on the Details page for each backend server. You can also use the API to find the IP in the sourceIpAddress field of the HealthCheckResult object.”

https://docs.cloud.oracle.com/ia as/Content/Balance/Tasks/editinghealthcheck.htm#health-status