FAQ - SAP Oracle iDataAgent
- Can we protect data on non-global zones if the File System iDataAgent is installed only on the global zone?
- How do we protect SAP Oracle data on a non-global zone?
- Can I perform the multi streamed backups if the data is distributed across several physical volumes?
- Can I perform a log only backup from RMAN command line without selecting a log storage policy?
- What does "Job Completed with Errors" mean?
- How do I enable SAP Oracle Tracing?
- Does the Sap Oracle Agent support backups of multiple archive log destinations?
- What is the SAP recov_interval parameter used for?
- Can archive logs be deleted based on how old the archive log is?
Can we protect data on non-global zones if the File System iDataAgent is installed only on the global zone?
Yes. We can protect file system data on non-global zones if the File System iDataAgent is installed only on the global zone. However, in order to enable consistent backups of application specific data on the non-global zones, you will need to install the corresponding application specific iDataAgent on the non-global zone.
In order to enable consistent backups of SAP Oracle data on a non-global zone, you need to install the SAP Oracle iDataAgent on the non-global zone.
Can I perform the multi streamed backups if the data is distributed across several physical volumes?
Yes. You can perform the multi streamed backups if the data is distributed across several physical volumes.
However, since arbitration is done taking the disk slices or partitions as Physical Volumes, when multiple slices are present on the same hard-disk, each of those is considered as a separate physical volume and arbitrated. When more than one stream tries to read from the same hard-disk (even if it contains multiple physical volumes), the performance may be slow. By default, if the data is distributed across several physical volumes, an efficient file arbitration is in effect and an improved throughput is anticipated.
You can configure the sCLASSIC_ARBITRATION additional setting to disable the traditional way of disk arbitration. If you set this additional setting to Y, the multi-streamed backups backint interface parent arbitrates the files sequentially to its children.
Yes. the log storage policy that is configured at instance level is automatically selected when you perform a log only backup from RMAN command line.
If the backup job gets killed while backing up some data, then the job status is shown as "Job Completed with Errors".
Yes, ASM and raw devices are supported only if RMAN_UTIL device interface is used for backups. They are not supported for other device interfaces like UTIL_FILE and UTIL_FILE_ONLINE.
Follow these steps to enable SAP Oracle Tracing.
- From the CommCell Browser, navigate to Client Computers.
- Right-click the <Client> to be configured and then click Properties.
- Click Advanced.
- Click the Additional Settings tab and then click Add.
- In the Name field, type nTRCBACKINT.
- In the Value field, type 11.
- Click OK to save the additional setting.
- Click OK.
No, BR*Tools supports backing up archive logs from the default location. If multiple archive log destinations are configured, BRTools only backs up the archive logs from the first destination.
The SAP recov_interval is set in the init<SID>.sap profile file and defines the time interval that the BRRESTORE and BRRECOVER commands search for the data and log backup details files in the summary file. By default, this value is 30 days.
Set this parameter based on your restore and recover options. For example, if you want to restore a log sequence number that was generated n days ago, you must set the SAP recov_interval parameter to the following in the init<SID>.sap file.
recov_interval >= n days
For example, if you wanted to set the value to 120 day, use the following:
recov_interval = 120 days
Note: If this interval is not set correctly, the BRRESTORE or BRRECOVER commands will not find the backups, and you will receive the following SAP error in the BRRESTORE logs:
BR0439E No offline redolog files found in /orahome/app/oracle11g/product/dbhome_1/TRD/saparch/archTRD.log for processing for device type TAPE/BACKINT/RMAN in recovery interval of 30 days
BR0435E Last successful backup not found in /orahome/app/oracle11g/product/dbhome_1/TRD/sapbackup/backTRD.log in recovery interval of 30 days
If you use the RMAN_UTIL interface, you can use the native archived redo log deletion policy.
If you use the util_file or util_file_online options, you can delete the log the logs after they are backed up, or you can create a secondary copy of the logs and then delete the logs. For more information on this subclient configuration, see Subclient Properties.
If you use the util_file third party command line, see Backup Archive Logs for more information.