Backup

Prerequisites:

1. Ensure Zmanda Pro is installed and properly configured on the client machine.

2. backupmanager utility must be installed on the client machine.

3. You must know the Protected Item (PI) name and the Backup Script Name configured for the Oracle database.

4. The machine where you are running the backup must be registered to a Zmanda Pro server where the Oracle database’s protected item is registered.

---

Backup Methods

There are two ways to initiate a backup:

1. Client-triggered backup

2. Server-triggered backup

1. Client-Triggered Backup

Follow these steps to initiate a backup from the client machine:

1.1 Initiate the Backup Command

On the client machine, execute the following command in the terminal which you have configured as part of backupmanager configuration:

backupmanager rman backup --pi-name <Protected Item Name> --script-name <Script Name>

Example:

backupmanager rman backup --pi-name oracle-prod-db --script-name full-backup

1.2 Monitor Backup Progress

Once the backup is initiated, you can monitor its progress directly in the terminal. Watch for any warnings or errors during the backup process.

2. Server-Triggered Backup

Follow these steps to schedule and initiate a backup from the Zmanda Pro web portal:

2.1 Log into Zmanda Pro Web Portal

Access the Zmanda Pro web portal using your user credentials.

2.2 Navigate to Protected Item Configurations

Click on the "Backup" section to view all existing Protected Item configurations.

2.3 Backup

2.3.1 Schedule a Backup

1. Go to the "Schedule" tab within the protected item configuration.

2. Click on the backup rule named after the script you configured, then add or modify the schedule as needed.

3. Save the backup rule and protected item settings.

2.3.2 On Demand Server Triggered Backup

1. In the Zmanda Pro Server Web Portal, navigate to the Backup section.

2. Under the Run Backup modal, click on the Scheduled tab and select the schedule you wish to run as an on-demand backup.

2.4 Monitor Scheduled Backup Execution

Once the scheduled , the backup will be automatically triggered.

2.5 Review Backup Report

After the backup is complete, you can access the detailed backup report for the Protected Item on the Zmanda Pro server web portal. This report will provide comprehensive information about the backup operation.

Note: When a backup is triggered, a restore job log will appear alongside the backup job log in the Zmanda Pro User Server portal. This restore job log updates the inventory database with the latest backup run IDs. This step ensures that the backup run IDs are added to the most recent inventory, preventing any inconsistencies in the backup process.

Notes:

• Ensure that the Oracle database is in a consistent state before initiating a backup.

• Regular backups are crucial for data protection. Set up a backup schedule that aligns with your organization's recovery point objective (RPO).

• If you wish to backup ARCHIVELOG as part of the backup ensure the database is in ARCHIVELOG mode. Please follow the guide link if needed: Changing the Database Archiving Mode

Troubleshooting:

• If you encounter any issues during the backup process, check the following:

  • Verify that the Protected Item (PI) name and script name are correct.

  • Check network connectivity between the client and the Zmanda Pro server.

  • Review the logs for any specific error messages or warnings.

  • Staging Directory Permissions Issues (Windows): If the Oracle database user cannot access the staging directory, ensure that the directory permissions are correctly set in a way that it is accessible by oracle user/group.