Highlighted
Stefan Wusowski Super Contributor.
Super Contributor.
430 views

DP 10.30 MySQL Integration for customizer MySQL installation

Hello,

i want to integration MySQL DB 5.7 into DP 10.30, but the MySQL installation is customized.

I fiil in the information for the integration

- user, password, port

- path to mysqlbackup

Following Error appears:

check configuration failed.
System error
(2) No such file or directory
/usr/bin/mysqlbinlog

yes, there is no "/usr/bin/mysqlbinlog" there are only mysqlbinlogmove, ..purge, ..rotate, but no mysqlbinlog

mysqlbinlog is under /opt/mysql/app/product/bin - there is also the mysqlbackup

 

from /etc/opt/omni/server/integ/config/MySQL i see 2 configfiles

-rw-r----- 1 root hpdp 66 May 23 08:11 muncxuserdb12a_vip%_OB2_GLOBAL

INSTANCE_LIST=('USR_395');
MEB_path='/opt/mysql/app/product/bin';

-rw-r----- 1 root hpdp 164 May 23 08:11 muncxuserdb12a_vip%USR_395

MYSQL_home='/usr/bin';                                                                 what is necessary here? howto chage this path?
MYSQL_inst2='/usr/libexec';                                                           is not exsisting
defaultsFile='';
MYSQL_inst='/usr/sbin';                                                                   what is necessary here? howto chage this path?
MYSQL_PARAM={
user='';
socket='';
};

Is there a commandline option for util_mysql.pl (like util_oracle.pl)

Select the Use parameters from custom MySQL configuration file option and specify the path to the custom MySQL configuration file (option file) on the MySQL host from where the parameters are obtained.

what must be the content of this custom MySQL Configuration file?

 

THX

 

OK Commandline Option

muncxuserdb12b:/opt/omni/lbin # ./util_mysql.pl -help
util_mysql.pl
-version|-help
-app
-chkconf <INSTANCE NAME>
-config <INSTANCE NAME>
-meb_path <MYSQLBACKUP PATH>
-user <USER>
-password <PASSWORD>
-port <PORT>
-defaults_file <DEFAULTS FILE>
-objs0 <INSTANCE NAME>
-objs1 <INSTANCE NAME> <DATABASE NAME>

Tags (3)
0 Likes
9 Replies
Micro Focus Expert
Micro Focus Expert

Re: DP 10.30 MySQL Integration for customizer MySQL installation

Hello @Stefan Wusowski

According to the documentation, you need to follow some steps when you have custom configuration. Have you follow that? 

https://docs.microfocus.com/itom/Data_Protector:2019.02/mySQLIntegration#Configure_the_integration

Regards, 

Andres Fallas Salazar
Customer Support Engineer

If you find that this or any other post resolves your issue, please be sure to mark it as an accepted solution.
If you are satisfied with anyone’s response please remember to give them a LIKE by clicking on the bottom at the left of the post and show your appreciation.
0 Likes
Knowledge Partner
Knowledge Partner

Re: DP 10.30 MySQL Integration for customizer MySQL installation

Hi @Stefan Wusowski,

Have you considered creating symlinks to the binaries missing so that the MySQL integration is able to locate the binaries in the expected directories?

Regards,
Sebastian Koehler

---
Please use the Like button below, if you find this post useful.
0 Likes
Stefan Wusowski Super Contributor.
Super Contributor.

Re: DP 10.30 MySQL Integration for customizer MySQL installation

Hey Sebastian,

I did not test it with symlinks. Here is the question of what else should be linked? I will try.

Thanks

0 Likes
Stefan Wusowski Super Contributor.
Super Contributor.

Re: DP 10.30 MySQL Integration for customizer MySQL installation

I had read this, but at my point DP is not able to find the necessary binaries. Maybe this can add to a "custom MySQL configuration option file", but i did not find any information about the syntax for this file.

I had open already a ticket, maybe they can help.

0 Likes
Knowledge Partner
Knowledge Partner

Re: DP 10.30 MySQL Integration for customizer MySQL installation

Hi @Stefan Wusowski,

I agree that the documentation should be improved. Maybe you can ask for this after digging into this?

What I found is the integration configuration file client.domain.com%INSTANCE in OmniBack\Config\Server\Integ\Config\MySQL (on Windows CM) which contains the following. Changing MYSQL_instMYSQL_inst2 and MYSQL_home might be enough.

MYSQL_PARAM={
	port='3306';
	user='root';
	password='<PASSWORD_ENCODED>';
};
MYSQL_inst2='/usr/libexec';
MYSQL_home='/usr/bin';
MYSQL_inst='/usr/sbin';
OSUSER='root';
OSGROUP='root';

Regards,
Sebastian Koehler

---
Please use the Like button below, if you find this post useful.
0 Likes
Stefan Wusowski Super Contributor.
Super Contributor.

Re: DP 10.30 MySQL Integration for customizer MySQL installation

Hey

i had done some test’s

when I link

lrwxrwxrwx 1 root root       32 May 24 10:11 (usr/bin/mysql -> /opt/mysql/app/product/bin/mysql

lrwxrwxrwx 1 root root       38 May 24 10:00 /usr/bin/mysqlbinlog -> /opt/mysql/app/product/bin/mysqlbinlog

 

create “/usr/libexec” (directory don not exist!)  and link lrwxrwxrwx 1 root root 33 May 24 10:19 /usr/libexec/mysqld -> /opt/mysql/app/product/bin/mysqld

 

then the integration configuration will end successful

mysql@muncxuserdb12b:/opt/omni/lbin> ./util_mysql.pl -config [DEFAULT] -meb_path /opt/mysql/app/product/bin/mysqlbackup -user root -password Root_001 -port 3306

*RETVAL*0

 

Configuration files:

[root@lnxp-5084 MySQL]# cat muncxuserdb12a_vip%[DEFAULT]
MYSQL_PARAM={
user='root';
port='3306';
password='XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX';
};
MYSQL_home='/usr/bin';
MYSQL_inst2='/usr/libexec';
MYSQL_inst='/usr/sbin';
OSUSER='mysql';
OSGROUP='oinstall';

[root@lnxp-5084 MySQL]# cat muncxuserdb12a_vip%_OB2_GLOBAL
MEB_path='/opt/mysql/app/product/bin/mysqlbackup';
INSTANCE_LIST=('[DEFAULT]','[DEFAULT]','[DEFAULT]','[DEFAULT]','[DEFAULT]','[DEFAULT]');

With any run of the util_mysql.pl the INSTANCE_LIST is increased !!! 😉

 

 

 

0 Likes
Knowledge Partner
Knowledge Partner

Re: DP 10.30 MySQL Integration for customizer MySQL installation

Hi @Stefan Wusowski,

This is something that needs to be passed to the documentation team. Use the feedback button on the documentation page and they will implement this soon.

mysql@muncxuserdb12b:/opt/omni/lbin> ./util_mysql.pl -config [DEFAULT] -meb_path /opt/mysql/app/product/bin/mysqlbackup -user root -password Root_001 -port 3306


INSTANCE_LIST=('[DEFAULT]','[DEFAULT]','[DEFAULT]','[DEFAULT]','[DEFAULT]','[DEFAULT]');

With any run of the util_mysql.pl the INSTANCE_LIST is increased !!! 😉


Well, this command does not check the configuration it creates a new instance. You're using the same instance name. So this could be either a bug or expected. Asking support (maybe in a seperate case) for this could be helpful.

Regards,
Sebastian Koehler

---
Please use the Like button below, if you find this post useful.
0 Likes
Knowledge Partner
Knowledge Partner

Re: DP 10.30 MySQL Integration for customizer MySQL installation

Hi @Stefan Wusowski,

Reconfiguring the MySQL instance in the GUI does not add additional entries to the INSTANCE_LIST so I guess this is a bug of util_mysql.pl -config.

Regards,
Sebastian Koehler

---
Please use the Like button below, if you find this post useful.
Stefan Wusowski Super Contributor.
Super Contributor.

Re: DP 10.30 MySQL Integration for customizer MySQL installation

So now I was able to successfully restore the MySQL Database. Another symlink was needed for "mysqladmin"
So for me the workaround looks like:

mkdir /usr/libexec
chmod 755 /usr/libexec
ln -s /opt/mysql/app/product/bin/mysqld /usr/libexec/mysqld
ln -s /opt/mysql/app/product/bin/mysql /usr/bin/mysql
ln -s /opt/mysql/app/product/bin/mysqlbinlog /usr/bin/mysqlbinlog
ln -s /opt/mysql/app/product/bin/mysqladmin /usr/bin/mysqladmin

Have fun ;-))

 

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.