Configuring Oracle DB backups

To protect data in Oracle® databases, install the Oracle® plug-in with the IBM Cloud® Backup for Classic agent on the Oracle® database server. Then, you can add and run backup jobs that specify which databases to back up, and where to save the backup data. The plug-in provides ARCHIVELOG-based, non-RMAN backups of whole online database instances. All nontemporary table spaces and instance parameter files are automatically backed up. Full and partial databases can be restored through normal user-managed Oracle recovery mechanisms. Database passwords are encrypted for enhanced security over script-based methods.

The Oracle plug-in performs what the Oracle Corporation deems an “inconsistent” whole database backup that requires that the database is run in ARCHIVELOG mode. During a live backup, any changes to the database are written to archive logs. The database administrator must make sure that the database is in ARCHIVELOG mode.

Starting Cloud Backup Portal

You need to be connected to the IBM Cloud® private network to be able to start the Portal.

Log in to the IBM Cloud console. From the menu , select Infrastructure > Classic Infrastructure.
Click Storage > Cloud Backup to display the backup services.
Select the instance name of the IBM Cloud Account.
Click View backup portal to start the portal in your browser.

If the Portal doesn't start, you might have a problem with your VPN connection. You might also see a message that says that the form you’re sending isn’t secure. It is expected - proceed by sending the form.

Configuring a backup job

Through the IBM Cloud Backup for Classic portal, you can manage and monitor your backups. You can create a backup job for one or more Oracle databases. The backup job specifies which databases to back up, and where to save the backup data.

When you create an Oracle database backup job, you must specify credentials for the IBM Cloud Backup for Classic Agent to use to connect to the Oracle server.

To add an Oracle database backup job, complete the following tasks.

On the navigation bar, click Computers. The registered servers are displayed on the Computers page.
Find a server with the Oracle plug-in, and expand its view by clicking the computer row.
Click the Jobs tab.

If the server doesn't have a valid vault connection, then you can't access the Jobs tab.
In the Select Job Task menu, click Create New Oracle Job.
In the Connect to Oracle Server dialog box, provide the following information.
- In the Database Service Name box, type the database instance.
- In the username box, type the name of a user who has sysdba privileges.
- In the Password box, type the password for the specified user.
Click Connect.
In the Create New Job dialog box, specify the following information.
- In the Name box, type a name for the backup job.
- In the Description box, type a description for the backup job. The description is optional.
- In the Destination list, select the vault where you want to save the backup data.
  
  A vault appears in the list if it is assigned to the user, or if the user added it in the computer’s Vault Settings.
- In the Log File Options list, select the level of detail for job logging. For more information, see log file options.
- For new backup jobs, the encryption method is AES 256 bit. Existing jobs can have other encryption methods. For more information, see encryption settings.
- In the Password and Confirm Password boxes, enter an encryption password. You can also enter a password hint in the Password Hint box.
In the Include in Backup box, select the database that you want to back up.
Click Save. The job is now created, and the View/Add Schedule dialog box appears. Next, you can create a schedule for running the backup. Click Cancel if you don't want to create a schedule now.

Scheduling the backup job

In the View/Add Schedule dialog box, click Add Schedule.
In the new schedule row, in the Retention list, click a retention type.
In the Schedule box, click the arrow.
In the Configure Job Schedule dialog box, choose one of the following options.
- To run the backup on specific days each week, in the Schedule View list, click Days of Week. Select the days when you want to run the job. Then, use the At field to specify the time when you want to run the job.
- To run the backup on specific dates each month, click Days of Month in the Schedule View list. On the calendar, select the date when you want to run the job. Then, use the At field to specify the time when you want to run the job.
- To create a custom schedule, click Custom in the Schedule View list. In the Custom Cycle dialog box, enter a custom schedule. Be sure to follow the format and notation as described.
Click Okay. The schedule appears in the Schedule box.
In the Compression list, click a compression level for the backup data. Compression levels optimize the volume of data sent against the speed of processing.
For Deferring, select one of the following options.
- To allow the backup job to run without a time limit, click None in the Deferring list.
- To specify a maximum amount of time that the backup job can run, click Minutes or Hours in the Deferring list. In the adjacent box, type the maximum number of minutes or hours that the job can run.
When you use the deferring option, the backup job doesn't back up any new data after the specified amount of time, even if some data is not backed up. Changes to data that was previously backed up are still backed up, regardless of the amount of time specified.
To run the job on the specified schedule, select the Enable checkbox near the end of the row.
Click Save.

Advanced Settings

Log file options

When you create or edit a backup job, you can specify the level of detail for job logging. Select one of the following levels from the list.

Files - this setting provides the most detailed information, and is typically used for troubleshooting. It provides information about files that are backed up.
Directory - This setting provides less detail than the Files logging level. It provides information about folders that are backed up.
Summary - This setting provides high-level information, including the vault and IBM Cloud Backup for Classic Agent version, and backup sizes.
Minimal - This setting provides high-level information, including the vault and IBM Cloud Backup for Classic Agent version.

Changing the logging level affects only the log files that are created at that point and after. It does not affect previously created log files.

Encryption settings and password

Encryption settings specify the encryption type for backup data at rest on the vault. AES 256-bit encryption is the default encryption type that is available for new backup jobs. When you create a backup job, you must enter a password for the encrypted data. The password is case-sensitive. To recover the data, you must provide the encryption password that was entered when the files were backed up.

You can also enter a password hint. When you want to restore data, you can view the password hint to remind you of the encryption password for this job.

If you forget the encryption password, you lose access to the data. You cannot retrieve the password from the system.

Performance Options

Bandwidth throttling settings specify the amount of bandwidth that is used by an IBM Cloud Backup for Classic Agent for backups. For example, you might want to restrict the amount of bandwidth that is used for daytime backups so that online users are not affected. At the same time, you might allow unlimited bandwidth usage at night so that scheduled backups run as fast as possible.

Bandwidth settings include the following parameters.

Maximum bandwidth, in megabits per second, to be used by the IBM Cloud Backup for Classic Agent for all backups and restores.
Length of time during the day that throttling is in effect. Only one time-window can be specified. Outside the window, no throttling takes place.
Days of the week that throttling is in effect.

If the bandwidth-throttling time period begins when a backup is underway, the maximum bandwidth is applied dynamically to the running backup. Similarly, if the bandwidth-throttling time period ends when a backup is running, bandwidth throttling is ended for the backup.

If you edit an IBM Cloud Backup for Classic Agent’s bandwidth settings while a backup is running, the new settings do not affect the backup that is running. Bandwidth settings are applied when a backup starts, not during its operation.