KB ID: | 2871 |
Product: | Veeam Backup & Replication | 10 | 11 | 12 | 12.1 | 12.2 |
Published: | 2019-01-25 |
Last Modified: | 2024-02-29 |
Languages: | JP |
Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest
Please, try again later.
Collect logs found within the plugin folder indicated below on the Veeam Backup Server and all Backup Repositories*.
*For repositories other than Windows and Linux, the log files will be located on the Gateway server associated with the repository.
%ProgramData%\Veeam\Backup\Plugin\
/var/log/VeeamBackup/Plugin/
If the backup is managed by Veeam Backup & Replication, please also collect the following:
%programdata%\Veeam\Backup\Rescan\
/tmp/veeam_plugin_logs/
The command below will automate the collection of logs from the /tmp/veeam_plugin_logs/:
cd /tmp/veeam_plugin_logs/ && tar -cvf - . | gzip -9 > ~/$(hostname)-$(date +"%Y-%m-%d_%H-%M-%S-%z-")-veeam_plugin_logs.tar.gz && cd -
The command above is formatted to allow for universal usage with Linux, Solaris, and AIX. The output file will be written to the home folder of the account running the command. The exported log file's name will be unique and include the hostname, date stamp, and timezone.
/tmp/OracleProxyLogs/
The command below will automate the collection of logs from the /tmp/OracleProxyLogs/ :
cd /tmp/OracleProxyLogs/ && tar cvf - . | gzip -9 > ~/$(hostname)$(date +"%Y-%m-%d_%H-%M-%S-%z-")-OracleProxyLogs.tar.gz && cd -
The command above is formatted to allow for universal usage with Linux, Solaris, and AIX. The output file will be written to the home folder of the account running the command. The exported log file's name will be unique and include the hostname, date stamp, and timezone.
/var/log/VeeamBackup/
Alternatively, collect all logs from the /var/log/VeeamBackup/ folder with this command:
cd /var/log/VeeamBackup/ && sudo tar -cvf - . | gzip -9 > ~/$(hostname)-$(date +"%Y-%m-%d_%H-%M-%S-%z-")-veeam_deployment_logs.tar.gz && cd -
%ProgramData%\Veeam\Backup\RmanPluginLogs\
Save information about failed RMAN operations. This can be achieved in different ways, as shown below. Discuss with your system administrator which way they feel is most appropriate. It’s important for a support engineer to see RMAN client output for the failed operation. Save the output of RMAN client operations in a text file for Veeam Support.
RMAN> SPOOL LOG TO '/tmp/rman.log'; RMAN> … Actual client commands … RMAN> SPOOL LOG OFF;(Note: https://docs.oracle.com/cd/B28359_01/backup.111/b28273/rcmsynta046.htm#RCMRF156)
$ rman TARGET / LOG=/tmp/rman.log APPEND RMAN> … Actual client commands … RMAN> EXIT(Note: https://docs.oracle.com/database/121/BRADV/rcmcnctg.htm#BRADV8122)
$ rman target / | tee -a /tmp/rman.log
Run the following queries from an RMAN client command prompt:
RMAN> LIST BACKUP; RMAN> LIST ARCHIVELOG ALL; RMAN> SHOW ALL;
Save the output of the above queries in a text file.
To provide the support engineer with overall information about the software installation on the Oracle server:
$ sqlplus / as sysdbaand run the following queries:
SQL> SELECT * FROM V$VERSION; SQL> SELECT STATUS FROM V$INSTANCE; SQL> SELECT LOG_MODE FROM V$DATABASE; SQL> SELECT NAME FROM V$CONTROLFILE; SQL> SELECT USERNAME,SYSDBA FROM V$PWFILE_USERS; SQL> SHOW PARAMETER SPFILE; SQL> SHOW PARAMETER PFILE;Save the output of the above queries in a text file for Veeam Support.
oratab (by default it's located in /etc) inventory.xml (by default it's located in $ORACLE_BASE/oraInventory/ContentsXML) oraInst.loc (by default it's located in $ORACLE_HOME)
oratab (by default it's located in /var/opt/oracle) inventory.xml (by default it's located in $ORACLE_BASE/oraInventory/ContentsXML) oraInst.loc (by default it's located in $ORACLE_HOME)
Your feedback has been received and will be reviewed.
Please, try again later.
Please try select less.
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
Your feedback has been received and will be reviewed.
Please, try again later.