Failed RMAN Plugin

[Fegume]

Hello I install the plugin on my server Suse and then run the wizard:

oracleserver:~ # OracleRMANConfigTool --wizard
Enter backup server name or IP address [172.29.0.30]:
Enter backup server port [10006]:
Enter username [domain\Veeadmin]:
Enter password for domain\Veeadmin [(do not change the existing password)]:
Veeam repositories:
1. vsa01.domain.local
Specify up to 4 Veeam repositories to use as target using whitespace as a separator [1]:
Enter the number of data streams (From 1 to 254) to send to each repository concurrently(RMAN DEVICE PARALLELISM value). Channel count per device [1]:
Enable Veeam compression? (Y/n):

Failed to connect to the following Oracle instances:
ORACLE_SID=TEST ORACLE_HOME=/software/oracle/product/12.2.0.1/dbhome_1

Please apply the following RMAN settings manually:
CONFIGURE DEFAULT DEVICE TYPE TO SBT_TAPE;
CONFIGURE CHANNEL DEVICE TYPE SBT_TAPE
PARMS 'SBT_LIBRARY=/opt/veeam/VeeamPluginforOracleRMAN/libOracleRMANPlugin.so'
FORMAT 'fe83bf55-4ccb-4f5b-b8a3-f74a0d4697f4/RMAN_%I_%d_%T_%U.vab';
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1;
CONFIGURE DEVICE TYPE SBT_TAPE PARALLELISM 1;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO '%F_RMAN_AUTOBACKUP.vab';


Channel definition for RMAN scripts:
ALLOCATE CHANNEL VeeamAgentChannel1 DEVICE TYPE SBT_TAPE
PARMS 'SBT_LIBRARY=/opt/veeam/VeeamPluginforOracleRMAN/libOracleRMANPlugin.so'
FORMAT 'fe83bf55-4ccb-4f5b-b8a3-f74a0d4697f4/RMAN_%I_%d_%T_%U.vab';

Save configuration?
1. Apply configuration to the Oracle environment
2. Export configuration into a file for manual setup
3. Cancel without saving
Enter: 1

*** No Oracle database instances were configured ***

I login with root user, any idea?

Thanks!!

[Fegume]

Fix it:

Log in to the Oracle server with an account which is a member of the DBA group.

I login with root and not user member DBA group.

[Andreas Neufert]

2 options, the Oracle instance is down or the user has no access to the database.
In your case as you used root to configure the plug-in and root has no access to the database.

Please follow the instructions carefully here: https://helpcenter.veeam.com/docs/backu ... ml?ver=100

Potentially you have to remove the Veeam configuration XML file as it was created now under root with wrong access rights.

[EmmyU]

I am also having same issue. Any help is appreciated.

[Gostev]

If the above information is not sufficient, then feel free to open a support case for assistance.

[mjicwr]

Hi.

Could be your oracle SID in the /etc/oratab is wrong

[PetrM]

Hello Madzrul and Welcome to Veeam R&D Forums!

We appreciate your willingness to share one more idea of what makes sense to check, that's true, an "inconsistent" oratab can impact our detection logic. Anyway, I strongly recommend contacting our support team in case of the issue mentioned above to all future readers of this topic. Also, you may share a case ID so that we can keep an eye on it.

Thanks!

[Andreas Neufert]

1) Check your /etc/oratab that it points to the right folders and instances
2) Check that ORACLE_HOME and ORACLE_SID are set correctly at the environment variables in the "Oracle" user that you use for running the configuration wizard.
3) Check your Oracle configuration.
In Linux environment, The value of ORACLE_HOME and ORACLE_SID is obtained by parsing the ORATAB FILE and OraInventory
On windows, Veeam parses the service names under windows services to obtain ORACLE_HOME and ORACLE_SID
4) Install the plug-in with root
5) Start the Oracle Instance (database open) with a oracle user
6) Login with an "oracle" user into the operating system and start the Veeam configuration wizard

If you used the "root" user by mistake to run the Veeam configuration wizard it will create a veeam configuration file + logfile folders with root as the owner and root as the group. This way the plug-in can not work as the plug-in will be started by RMAN later and this user will not have access to it then. You need to change the owner and group rights to for example oracle:oinstall (depending on what you use) of the Veeam configuration file and the /tmp/ veeam log folders and files. (or remove them to start over again).