RMAN Triggered Oracle Backups to Streamline Administration

Zmanda Classic can initiate database backups from the client side with the help of the RMAN-triggered Oracle backup feature. This capability makes it possible to trigger Oracle database backup processes from client servers using RMAN (Recovery Manager) commands.

Database administrators (DBAs) can take backups in an organization without having to log in to Zmanda Management Console (ZMC), thus making the backup and recovery process more convenient. Also, this implementation allows users who are not familiar with the ZMC interface to still successfully take backups when required.

DBAs can also back up multiple databases efficiently using this streamlined approach, ensuring better recoverability for critical systems.

Understanding the Oracle Database Backup and Recovery Techniques

RMAN Triggered Oracle Backup is an approach that helps you initiate Oracle system backups directly from the client side using Oracle’s Recovery Manager (RMAN). This method leverages Oracle’s SBT (System Backup to Tape) interface, which can integrate with various backup solutions, including Zmanda Classic.

When implementing RMAN Triggered Oracle Backup with Zmanda Classic specifically, you need to create a backup set and a user with password protection in Zmanda. System administrators will also need to perform necessary configurations before you can trigger Oracle system backups directly from the client. The following sections will guide you through these Zmanda-specific configurations step by step.

RMAN Triggered Setup for Oracle: Prerequisites and Configuration

Before implementing RMAN-triggered Oracle backups, ensure these requirements are met:

1. Software Requirements

• Oracle system 10g or newer with RMAN configured
• Zmanda Classic 3.3.9 or later software installed and configured
• Amanda client installed on the Oracle system server
• Zmanda SBT library installed and configured on the Oracle server

2. System Configuration

• Oracle user account with SYSDBA privileges
• System running in ARCHIVELOG mode (for incremental backups)
• Oracle environment variables properly set for the RMAN user (ORACLE_HOME, ORACLE_SID)

3. Network Requirements

• Network connectivity between Oracle server and Zmanda server
• Firewall settings allowing Amanda communications (typically UDP/TCP port 10080)

4. Storage Requirements

• Sufficient disk space allocated on the Zmanda server for Oracle backups
• Proper Amanda configuration including disk list, tape list, or S3 storage configuration

5. Access Requirements

• Administrative access to both Oracle system and Zmanda Management Console
• SSH or console access to the Oracle server for configuration

Verify these prerequisites before proceeding with the configuration to ensure a successful implementation.

How It Works: A Visual Overview

Now that we’ve covered the prerequisites, let’s examine how the RMAN triggered Oracle backup process actually works within the Zmanda ecosystem. Understanding this workflow will help you better grasp the integration between Oracle’s native RMAN utility and Zmanda’s backup infrastructure.

This architecture provides several key benefits:

• RMAN handles database-specific backup intelligence
• Zmanda manages storage, retention, and recovery
• No intermediary files or manual steps required
• Full integration with Zmanda’s deduplication and compression

List of Configuration Steps

Now that you understand what RMAN Triggered Oracle Backup is and how it works with Zmanda Classic, let’s walk through the practical implementation. Setting up this integration involves three main steps: creating a dedicated RMAN user, configuring the client side, and completing the server-side setup. Following these steps in sequence will ensure a successful configuration.

Step 1: Create a Separate User for RMAN Triggered Operations

1. Log in to ZMC using your credentials.
2. Select Configuration on the left side navigation bar.
3. Select Users under Configuration.
4. Click on the ADD USER button at the top right of the Users page.
5. Fill up the Add User form as applicable. Please ensure that the Role is selected as RMAN.
6. Click on the SAVE button to finish the user creation process.

Figure: Creating an RMAN User in Zmanda Management Console (ZMC)

Important: The same user credentials need to be used for the backend configurations in Step 2.

Step 2: Configure Client-Side Settings

The Client Triggered Oracle Backup feature ensures that each user within your organization need not be given access to ZMC, as database backup can be triggered directly from the client. This saves training time and streamlines backup operations.

Client Configuration File Setup

The following lines need to be added to the amanda-client.conf file located at /etc/amanda/amanda-client.conf:

Replace <backup server IP address> with your actual Zmanda server address and <user name> with the RMAN user you created in Step 1.

Password Encryption

For security, the PASS parameter cannot contain the plain text password. To encrypt it:

1. On the Oracle server, navigate to the encryption utility: cd /usr/bin/
2. Run the encryption command: ./amrman_encrypt encrypt
3. When prompted, enter the same password you used for the RMAN user in ZMC.
4. The utility will automatically update the PASS property in the amanda-client.conf file.

Step 3: Server-Side Configuration

Next, configure the backup set on the Zmanda server:

1. Log in to ZMC.
2. Navigate to the Backup Where page for the corresponding backup set.
3. Specify the configuration details for your Oracle system:
   • Select the Oracle system server as the client
   • Configure the Oracle SID and system configuration options
   • Set appropriate retention policies
4. Click on the ADD CONFIGURATION button to save configuration details.

Lastly, before you enter the RMAN utility, ensure your Oracle system configuration is properly set. This completes the setup process.

These RMAN commands can be integrated into your RMAN script with the SBT parameters shown earlier to create a comprehensive Oracle system backup strategy tailored to your specific requirements by the administrator.

Using the RMAN Triggered Feature

The following screenshot shows the RMAN command-line interface in action, demonstrating a successful connection to the Oracle database and allocation of the Zmanda SBT channel. This is what you’ll see when implementing the RMAN triggered backup process:

Figure: RMAN Command Execution for Zmanda SBT Integration

Firstly, switch to the RMAN utility. Next, you need to connect to the system to trigger the backup. The following statement can be used to trigger the backup:

CONNECT TARGET *
STARTUP;

Enter the target database password to connect to the target database. The following line should appear:

Connected to target database: <applicable value>

RUN
{
ALLOCATE CHANNEL zmanda_sbt DEVICE TYPE sbt TRACE=5
PARMS="SBT_LIBRARY=/usr/lib64/amanda/application/amml.so  
ENV=(BACKUP_LEVEL=smart,BKPSET=t2_rman,SID=cdb1) ";
BACKUP DATABASE;
}

Note: The above statement has assumed values. You will need to substitute them with the values applicable to your case for:

• BACKUP_LEVEL can be smart, full or incremental
• BKPSET (Name of backup set the source(Sid) is linked with)
• SID (Sid for which backup is to triggered)

Once the above lines are run on the RMAN utility. The following values with applicable values substituted will appear on the screen:

using target database control file instead of recovery catalog
allocated channel: zmanda_sbt
channel zmanda_sbt: SID=44 device type=SBT_TAPE
Channel zmanda_sbt: AMANDA MEDIA MANAGEMENT LIBRARY FOR ORACLE
released channel: zmanda_sbt

Verifying Configuration of Backups

To verify your configuration is working correctly:

1. Run a test backup using a small tablespace
2. Check the job status in Zmanda Classic’s History section
3. Verify the backup appears in the backup set’s history

Advanced RMAN Database Backup Options

You can also leverage RMAN’s powerful backup capabilities while using this integration. Here are some advanced RMAN database backup options you might find useful, and you can also customize these based on your specific requirements:

1. Incremental Oracle Database Backup

To perform an incremental backup that only backs up blocks that have changed:

2. Backing Up Specific Tablespaces

For backing up only selected tablespaces rather than the entire database:

Backing Up Archive Log Files

To back up all archived redo log files and maintain copies of backups:

3. Combined Database and Archive Log Backup

For a complete backup including both the database and all archive log files:

4. Compressed Database Operations

To reduce backup size through compression:

These RMAN backup options can be integrated into your RMAN script with the SBT parameters shown earlier to create a comprehensive Oracle system backup strategy tailored to your specific requirements.

Moving Forward with RMAN Triggers

The RMAN-triggered Oracle database backup approach streamlines database administration by allowing database administrators to initiate Oracle database backup directly using familiar RMAN backup commands. This integration combines the power of Oracle’s native RMAN utility with enterprise-grade backup infrastructure, providing deduplication, compression, encryption, and flexible storage options for Oracle database backup.

By eliminating the need to switch between different interfaces and leveraging existing Oracle RMAN expertise, this approach increases overall Oracle database backup efficiency within organizations. Database administrators can continue using the RMAN backup tools they’re already comfortable with while still benefiting from comprehensive backup management across multiple databases.

To discover more about Zmanda and incorporate it in your backup environment, please feel free to sign up for a free trial. If you have any questions, don’t hesitate to open a support ticket on the Network Zmanda or send an email to our sales team at [email protected]. Our team will be delighted to assist you!