Oracle Windows
When Amanda is licensed and configured for Windows Oracle backup, Amanda uses the Oracle VSS writer to take the back up of Oracle data files, control files, and archive logs.
Requirements for Windows Oracle Backup and Restore
These instructions assume you have already installed and licensed the Amanda server, and the Windows client that hosts the Oracle server being backed up. There are a number of additional requirements:
1. Right-click the My Computer icon and choose Manage from the popup menu.
2. Expand the Services and Applications tree and locate the Volume Shadow Copy Service.
3. If it is not started, do so.
4. If necessary, change the General Properties to make the Start-up. Select Automatic rather than Manual.
Database log mode No Archive mode
or
Database log mode Archive mode
Configuring Oracle Backups from the ZMC Backup What Page
Managing Oracle database backup and recovery requires an experienced Oracle administrator. Before you begin configuring Oracle backups, you may want to review the following links from Oracle regarding DB administration, backup and recovery concepts, and procedures:
Oracle database control files are backed up by Volume Shadow Copy Service snapshots. The backed-up files are referred to as Snapshot Control files. For example, a control file by the name of 'CONTROL01.CTL' is backed up under the name SNCFSID_NAME.ORA (SNCFDATA.ORA, if the database SID name is DATA). This snapshot control file is restored on the Oracle machine during restore, and is used for manual recovery.
Once you have ensured that the databases are in the proper state for the type of backup you are creating (i.e., ARCHIVELOGMODE or NOARCHIVELOGMODE, component-based or volume-based, etc.), create a dedicated backup set for each Windows Oracle server you intend to back up. On the Sources page, click on ADD SOURCE you are prompted to select what type of object you want to back up. Choose database and select the Oracle Windows from the source type. The following options are displayed:
Host Name
The name of the machine running the Oracle database server you intend to back up.
BackupSet
The name of the BackupSet for which you want to bound the Oracle Windows Source
Encryption
Select any of the encryption type from Encryption Strategy dropdown to encrypt the backup image before transfer to the Amanda backup server
Compression
Select any of the compression type from Compression Strategy dropdown to compress backup images before transfer to the Amanda backup server.
Deduplication
Select dedup option to eliminating redundant data in a data. In the process of deduplication, extra copies of the same data are deleted, leaving only one copy to be stored
After you have set the options, click SAVE to add the Windows Oracle object to the backup set. You can then configure the backup set just as you would any other by setting the options on Backup Where, Backup How, and Backup When, etc.
Note that the Zmanda Agent for Windows Oracle backup process only the databases, logs, and control files. If you wish to protect other Oracle-related files (such as the installation directory), create a standard backup template on the Zmanda Windows Client to include these files.
Recovering Windows Oracle Databases using the ZMC and Oracle sqlplus
Recovering an Oracle database is a two-part process:
Before starting the restore process, make sure that the Oracle server being restored is installed in the same location as the original backup source. Oracle databases, archive log, and control file locations should also match those on the original server.
Restoring the Backup Using the Zmanda Management Console
To restore a Windows Oracle database, follow these steps:
Manually Completing the Recovery
After the Oracle databases, control files, server parameter file and archive log files are restored to the Oracle server, there are a number of manual steps you must follow to complete the database recovery. The exact steps you follow will depend on what type of backup you are recovering from, and what the recovery goals are. If you are unfamiliar with Oracle backup/recovery concepts and procedures, please review this documentation from Oracle before proceeding.
The following examples are provided to show you what the steps would be for two typical scenarios:
Example for NOARCHIVELOGMODE Recovery
The Oracle database is now recovered. To verify that the database is in the open state (read/write mode), use the following command:
SQL> select name, open_mode from v$database;
Example ARCHIVELOGMODE Recovery
The Oracle database is now recovered. To verify that the database is in the open state (read/write mode), use the following command:
SQL> select name, open_mode from v$database;
Troubleshooting
If a Windows Oracle backup fails (or you are unable to verify the client through the ZMC), follow these troubleshooting steps: