You can protect Oracle databases that are hosted by an Amazon EC2 account and that reside on Amazon Elastic Block Storage (EBS) volumes. Infrastructure as a service (IaaS) -based Oracle deployments with EBS volumes are also supported. You can perform full IntelliSnap backups of the Oracle databases from the CommCell Console.
The Commvault software automatically discovers the EBS data volumes that are associated with the instance, so there is no additional user configuration when the volumes change.
You can restore the snapshot to the same EC2 instance or to a new EC2 instance.
If your configuration includes an LVM in a CentOS or Red Hat configuration, see IntelliSnap Backup - Support for additional information on how to protect your data.
If you want to configure forever incremental backups for large Oracle databases, do the following:
-
Refer to Forever Incremental Backups for Large Oracle Databases Hosted on AWS or Azure for more information.
-
When mounting or restoring from a backup copy for several databases, the iSCSI server and cache configuration needs a cache volume to temporarily store blocks. For more details about how to centralize the cache, see Using Commvault iSCSI Server for Instant Clones.
Before You Begin
-
Download and apply amazon_DB_FS_permissions.json for the AWS Identity and Access Management (IAM) policy. For information about broader permissions that apply to a CommCell's operations, see Requirements and Usage for AWS IAM Policies and Permissions.
Note
If you have previously downloaded and used the amazon_DB_FS_permissions.json file and want to use the "forever incremental backups for Oracle on AWS or Azure" feature, you need to download and apply the Commvault Platform Release 2023E version or a later version of the file, since it has the ebs:ListSnapshotBlocks permission defined.
-
Obtain a user access key by using AWS Identity and Access Management (IAM). For more information, go to the Amazon IAM User Guide website, Managing Access Keys for IAM Users. You can use the IAM user access keys to control access to specific AWS services and resources for an AWS account.
Procedure
-
Install the MediaAgent on the Oracle client.
-
Use the Amazon Access Key for the User and the Amazon Secret Key for the password for the Array credentials.
-
If you have not done so already, configure a storage policy for the database.
-
If you have not done so already, configure a storage policy for the logs.
-
Create a Snapshot Copy for the database.
-
Configure a backup copy for the database.
-
Create two subclients for the instance:
-
Create an online subclient for the database.
-
Select Amazon as the Available Snap Engine (Create New Subclient dialog box, IntelliSnap Operations tab, Available Snap Engine).
-
If you want to configure forever incremental backups for large Oracle databases, select Volume Copy (Block-Level Backup - Supports Instant Database Recovery) as the copy option (Create New Subclient dialog box, IntelliSnap Operations tab, Copy Option).
-
-
Create a subclient for the log files.
-
Select Amazon as the Available Snap Engine (Create New Subclient dialog box, IntelliSnap Operations tab, Available Snap Engine).
-
If you want to configure forever incremental backups for large Oracle databases, select Volume Copy (Block-Level Backup - Supports Instant Database Recovery) as the copy option (Create New Subclient dialog box, IntelliSnap Operations tab, Copy Option).
-
The advantage of using two subclients is that you can schedule log backups more frequently to ensure that the protected data contains the latest information.
-
-
You can restore the database from the backup or the backup copy
-
To restore from the backup, see Perform a restore.
-
To restore from a backup copy, see Restoring Data from a Backup Copy.
-