https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IyMDkzIiwiaGFzaCI6IjYyNGQwNzI2LTM0YzMtNGEyYS05MThlLTM4NjYzNDMwZTI2YSJ9
1-800-691-1991 | 9am - 8pm ET
EN

How to change the Oracle Redo Log file location during Application-Aware Backup

Purpose

Storing Redo Log files under /tmp location might cause the production Server run out of free space, which can lead to the Oracle Server to go down if no actions have been performed in advance.

This article explains how to change the Oracle Redo log file location during Application-Aware Backup.
 

Solution

Linux-based Oracle Server:
 
Place VeeamOracleAgent.xml to the Veeam agent starting location (it is /tmp by default)
     <config OracleTempLogPath=”/location”></config>
 
Make sure that the /location path has appropriate permissions for write/read.
 
Windows-based Oracle Server:
 
Create the following registry key and value on the Oracle VM:
Key: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\
String value (REG_SZ): OracleTempLogPath
KB ID:
2093
Product:
Veeam Backup & Replication
Version:
9.x
Published:
2016-02-01
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later