Which two are required for autonomous database manual backup?
What best practice shall one follow to create a backup or replication policy that can live longer than the 60 days retention for Autonomous Database (Shared)? Show
asked Nov 23, 2021 at 5:57
The current retention for automated and manual backups on Autonomous Database (Shared) is 60 days. You can use Data Pump Export for archival purposes or “backups” for longer than 60 days. Ref - I am a product manager on the Oracle Autonomous Database. answered Nov 23, 2021 at 5:57
An Autonomous Database resource is a user database. When you create an Autonomous Database, you choose the Autonomous Container Database for it and you specify "Data Warehouse" or "Transaction Processing" as its workload type to create an Autonomous Data Warehouse database or an Autonomous Transaction Processing database. You can create hundreds of Autonomous Databases on an Exadata Infrastructure. As described in Available Exadata Infrastructure Hardware
Shapes, the maximum is determined by the capacity of your Exadata Infrastructure hardware. Create an Autonomous DatabaseFollow these steps to create an autonomous database on an Oracle Exadata Database Service on Cloud@Customer system.
Manage Access Control List of an Autonomous DatabaseEnabling an access control list with an empty list of IP addresses makes the database inaccessible.
View a List of Autonomous DatabasesFollow these steps to view a list of autonomous databases on an Oracle Exadata Database Service on Cloud@Customer system.
View Details of an Autonomous DatabaseFollow these steps to view detailed information about an autonomous database on an Oracle Exadata Database Service on Cloud@Customer system.
Rotate ADB Encryption KeyFollow these steps to rotate the TDE Master key. On key rotation, the ADB life cycle goes through the regular updating state and returns to available. You can rotate the TDE Master key as many times as you want. The new TDE Master Key is stored in the same wallet in which the previous key was stored. Rotating the TDE Master Key leads to the new key being generated in OKV and assigned to this database. You can view all of the keys in OKV. Note You can rotate both Oracle-managed and customer-managed encryption keys.
Set the Password of an Autonomous Database's ADMIN UserFollow these steps to set the ADMIN database user's password for an autonomous database on an Oracle Exadata Database Service on Cloud@Customer system.
Scale the CPU Core Count or Storage of an Autonomous DatabaseFollow these steps to scale the CPU core count or storage an autonomous database on an Oracle Exadata Database Service on Cloud@Customer system up or down.
Enable or Disable Auto Scaling for an Autonomous DatabaseOracle Autonomous Database on Oracle Exadata Database Service on Cloud@Customer systems provides an auto scaling feature that automatically increases the number of cores an automonomous database during periods of increased demand and, as demand returns to normal, automatically decreases the number of cores down to the databases's base number. Note the following points regarding the auto scaling feature:
Follow these steps to enable or disable auto scaling for an autonomous database.
Move an Autonomous Database to Another CompartmentFollow these steps to move an autonomous database on an Oracle Exadata Database Service on Cloud@Customer system from one compartment to another compartment. Note
Stop or Start an Autonomous DatabaseFollow these steps to stop or start an autonomous database on an Oracle Exadata Database Service on Cloud@Customer system.
Note Stopping your database has the following consequences:
Restart an Autonomous DatabaseTo resolve some autonomous database issues with minimal downtime on Exadata Database Service on Cloud@Customer systems, you can restart the database. Restarting an autonomous database on an Oracle Exadata Database Service on Cloud@Customer system is equivalent to manually stopping and then starting the database. Using restart allows you to minimize downtime and requires only a single action. Follow these steps to restart an autonomous database.
Back Up an Autonomous Database ManuallyOracle Autonomous Database automatically backs up autonomous databases on an Oracle Exadata Database Service on Cloud@Customer system. In addition, you can manually back up an autonomous database should the need arise. Note During the backup operation, your autonomous database remains available. However, lifecycle management operations such as stopping it, scaling it, or terminating it are disabled.
Optionally, you can check the state of your backup in the list of backups on the database details page. For some states, an information icon is displayed to provide additional details regarding the state or ongoing operations like deletions. The backup has one of the following states:
Restore an Autonomous DatabaseYou can use any existing manual or automatic backup to restore and recover an autonomous database on an Oracle Exadata Database Service on Cloud@Customer system, or you can restore and recover the database to any point in time during the retention period of its automatic backups. Note Restoring an autonomous database puts the database in the unavailable state during the restore operation. You cannot connect to a database in this state. The only lifecycle management operation supported in the unavailable state is terminate.
Restore from a BackupFollow these steps to restore an autonomous database on an Oracle Exadata Database Service on Cloud@Customer system from a specific backup.
Restore to a Point in TimeFollow these steps to restore an autonomous database on an Oracle Exadata Database Service on Cloud@Customer system to a specific point in time.
Clone an Autonomous DatabaseFollow these steps to clone an autonomous database on an Oracle Exadata Database Service on Cloud@Customer system. You can use the cloning feature to create a point-in-time copy of your Autonomous Database for purposes such as testing, development, or analytics. To clone only the database schema of your source database, choose the metadata clone option. Clone Types The clone feature offers the following two types of Autonomous Database clones:
Steps
The Console displays the details page for the new clone of your database and the service begins provisioning the Autonomous Database. Note the following:
The Clone source is displayed in the General Information section of the cloned database details page. Click the name to view details of the source database. Note that if the source database is deleted, then this key/value pair is not displayed. Clone an Autonomous Database BackupFollow these steps to clone an autonomous database on an Oracle Exadata Database Service on Cloud@Customer system. You can use the cloning feature to create a point-in-time copy of your Autonomous Database for purposes such as testing, development, or analytics. To clone only the database schema of your source database, choose the metadata clone option. Clone Types The clone feature offers the following two types of Autonomous Database clones:
Steps
The Console displays the details page for the new clone of your database and the service begins provisioning the Autonomous Database. Note the following:
Clone a Standby DatabaseFollow these steps to clone a standby autonomous database on an Oracle Exadata Database Service on Cloud@Customer system. You can use the cloning feature to create a point-in-time copy of your Autonomous Database for purposes such as testing, development, or analytics. Clone Types: The clone feature offers the full-clone option to create a database that includes the metadata and data from the source database. Steps
The Console displays the details page for the new clone of your database and the service begins provisioning the Autonomous Database. Note the following:
The Clone source is displayed in the General Information section of the cloned database details page. Click the name to view details of the source database. Note that if the source database is deleted, then this key/value pair is not displayed. Clone a Standby Database BackupFollow these steps to clone an autonomous database backup on an Oracle Exadata Database Service on Cloud@Customer system. You can use the cloning feature to create a point-in-time copy of your Autonomous Database for purposes such as testing, development, or analytics. To clone only the database schema of your source database, choose the metadata clone option. Clone Types The clone feature offers the following two types of Autonomous Database clones:
Steps
The Console displays the details page for the new clone of your database and the service begins provisioning the Autonomous Database. Note the following:
Terminate an Autonomous DatabaseFollow these steps to terminate an Autonomous Database on an Oracle Exadata Database Service on Cloud@Customer system. WARNING: Terminating an Autonomous Database permanently deletes it. The database data will be lost when the system is terminated. However, automatic backups are not deleted if you have chosen Recovery Appliance or NFS as a backup destination. You can delete automatic backups directly from the Recovery Appliance or NFS.
API to Manage Autonomous DatabasesMonitor Performance with Autonomous Database MetricsYou can monitor the health, capacity, and performance of your Autonomous Databases with metrics, alarms, and notifications. You can use Oracle Cloud Infrastructure console or Monitoring APIs to view metrics.
View Top Six Metrics for an Autonomous DatabaseDisplays the top six metrics that are available in the metrics section on the Autonomous Database details page. To view metrics you must have the required access as specified in an Oracle Cloud Infrastructure policy (whether you're using the Console, the REST API, or other tools). See Getting Started with Policies for information on policies. Perform the following prerequisite steps as necessary:
To view metrics for an Autonomous Database instance:
View Aggregated Metrics for Autonomous Databases in a CompartmentLearn to view aggregated metrics for Autonomous Databases in a compartment. To view metrics you must have the required access as specified in an Oracle Cloud Infrastructure policy (whether you're using the Console, the REST API, or other tool). See Getting Started with Policies for information on policies Perform the following prerequisite steps as necessary:
To use the metrics service to view Autonomous Database metrics:
To create an alarm on a specific metric, click Options and select Create an Alarm on this Query. See Managing Alarms for information on setting and using alarms. Autonomous Database Metrics and DimensionsYou can limit the instances where you see metrics with dimensions. The available dimensions include: workload type, instance display name, region, and the instance OCID. Use dimensions by selecting values in the Oracle Cloud Infrastructure Console Service Metrics page or by setting dimension values with the API. See View Aggregated Metrics for Autonomous Databases in a Compartment to view metrics and to select metric dimensions. See Database Metrics for a list of the database metrics and dimensions. Which 2 locations can be used to store your DB system database backups?You can store backups in the cloud or in local storage.
What are two prerequisites for successful deployment of an autonomous dedicated database in OCI?Before you discover Autonomous Databases – Dedicated, you must ensure that you have performed the following tasks:. Create an Autonomous Database – Dedicated in Oracle Cloud Infrastructure. ... . Configure and deploy Oracle Enterprise Manager on Oracle Cloud Infrastructure.. Which are two characteristics of autonomous transaction processing?A fully managed open source database service for transactional and analytical workloads. A highly optimized, secure, and unified low-latency cross-cloud experience. Use high-performance Exadata Database and Oracle Autonomous Database services with data residency in your data center.
Which two statements are true about autonomous database?Which two statements are true about accessing Autonomous Database Tools? AAccess to Database Actions is available for all users of Autonomous Database. BOracle Machine Learning is available only with Autonomous Data Warehouse (ADW) Database.
|