Protect Oracle Databases

Once you have registered an Oracle server as a source, you're ready to protect the Oracle Databases on that server.

To protect your Oracle Databases:

1. In DataProtect as a Service, navigate to Sources, find the Oracle source name and then click Protect.

2. Click Add Objects. Browse through the Oracle server instances and select the databases that you want to protect. Click Continue.

3. Click the Edit (pencil) icon next to the selected object and select one of the following options:

   • System selects active node. Cohesity auto-selects an active single-instance Oracle node and configures the number of RMAN channels for the database object. (Default)

   • Select specific node(s). If you select this option, you can choose the number of RMAN channels and the SBT library path to be used for the database object.

   • Delete Archive Log. Toggle on and specify the days after which the archived logs on the source database should be deleted. If you enter a value of "0" days, source archived logs will be deleted immediately after each successful protection run.

     If you do not enable this option, Cohesity will not delete the archived logs after each protection run and you are responsible for deleting the archived logs from the source server.

4. Click Save.

5. In the New Protection dialog, select a Policy that matches the schedule and retention period you need. If the existing policies do not meet your needs, you can create a new policy with the settings you need.

   The Oracle adapter for the CCS SaaS solution relies on the SBT library to back up and recover. This requires occasional full backups. Please consider this while configuring the backup policies for the Oracle database.

6. If you wish to configure a specific End Date, Alerts, and other additional settings, click Additional Settings.

7. Click Protect.

The backups start immediately after you protect the objects, regardless of the time you set for the protection run.

Additional Settings

Advance Settings	Description
Start Time	Available only if the selected policy is set to Backup Daily. Indicates what time the protection run should start. Enter the Start Time and select AM or PM. The default time zone is the browser's time zone. You can change the time zone of the protection run by selecting a different time zone here.
End Date	If you need to end protection on a specific date, enable this to select the date.
Priority	Select a priority for the protection task execution. Cohesity supports concurrent backups, but if the number of tasks exceeds the ability to process them, they are executed in this priority order: High-priority tasks Medium-priority tasks Low-priority tasks
Alerts	Click to enable one or more of these alert types to trigger alerts for the following events and click Add to enter email addresses. SLA Violation. Creates warning alert when a protection run exceeds the configured SLA. Sends email. Failure. Creates critical alert when object protection fails to complete. Sends email. Success. Creates information alert when object protection completes. Does not send email.
SLA	The service-level agreement (SLA) defines how long the administrator expects a protection run to take. Enter: Full. The number of minutes you expect a full protection run, which captures all the blocks in an object, to take. Incremental. The number of minutes you expect an incremental protection run, which captures only the changed blocks in an object, to take.
Cancel Runs at Quiet Time Start	(Available only if the selected policy has at least one Quiet Time.) When enabled, all the protection runs that are currently executing will cancel when the Quiet Time period starts. By default, this setting is disabled, meaning that after a protection run starts, it continues to execute even when a Quiet Time period starts. However, new protection runs will not start during a Quiet Time.

Next > When the first protection run completes, you will be ready to recover your protected Oracle Databases if and when you need to.