I don't have experience with this, but isn't module just calling MEB and picking up data from there?  My understanding of this (after reading it for 10 minutes) is that MEB will use backup_dir and NMDA will pick it up from there (on NMDA you control this via MYSQL_BACKUP_DIR).  I could not see, at least in NMDA CFG file anything else to control different folders for data and log so I assume this is between MEB and MySQL itself.

... but just to rule out NMDA, you can set debug and see which variables are passed from NMDA itself and I assume you can do similar on MEB side.

Hi Hrvoje and others,

Apologize for hijacking the question, but do we support multistreaming backups of MySQL with NetWorker, at link: MySQL :: MySQL Enterprise Backup Features and Benefits it says that MySQL supports "

how do we configure it in NetWorker any information on the same...

Parallel backup options, if they depend on base NW package, are set on client level I believe (I never tested it to be honest).  On the other hand, if this feature comes specifically by NMDA for MySQL, then some sort of configuration parameter should be there and documented in NMDA admin guide.

Hi Joe,

Did you already find a solution or got your SR answered? I'm experiencing a similar error trying to back up a MySQL instance using NW/NMDA 9.0.1.

The MEB part finishes successfully (and by the way, already includes the binlog files up to that point), after that, NMDA also tries to back up the logs (as MYSQL_LOG_OPTIONS = "INCLUDE_LOGS" in NW client config)

From the nsrdasv log:

#################################################

backup_logs: Entering.

...

mysql_api_is_binlog_enabled: Entering.

mysql_api_is_binlog_enabled: Exiting.

Flushing binary logs.

mysql_api_flush_logs: Entering.

mysql_api_flush_logs: Exiting.

mysql_api_get_bin_logs: Entering.

mysql_api_get_bin_logs: Exiting.

mysql_api_get_bin_log_path: Entering.

mysql_api_get_bin_log_path: Exiting.

validate_log_path: Exiting.

log base name: bin-log starting log: 5 ending log 14

create_save_list: Entering.

create_save_list: Exiting.

create_binlog_cmd_line: Entering.

...

save command line arguments:

...

argument=28, value=-I

argument=29, value=/nsr/apps/tmp/binlog_output_ssssssssss_pppp.txt

...

create_binlog_cmd_line: Exiting.

backup_logs: Exiting with error: Could not save the binary logs (error code 1).

...

********** Start of List of logs to be backuped up: output **********

/var/lib/mysql/data/bin-log.000005

...

/var/lib/mysql/data/bin-log.000014

*********** End of List of logs to be backuped up: output ************

#################################################

The logs are in /var/lib/mysql/logs, not in /var/lib/mysql/data. So, NMDA uses some api to flush the logs and get the binlog paths, but then still generates a wrong input file for the save command, containing the data path?

The original question was posted on Jan 28, 2016.

Based on notes in the service request, the issue was resolved after fixing an unspecified my.cnf typo error. 

Hi Wallace, can you provide some information on this sr? What was the typo that was made?

Thanks in advance!

Unfortunately, the service request did not document what the actual typo error was within the my.cnf file.

If the original poster does not respond, then I suggest a new service request be created so that Dell EMC tech support can assist you.

Ìt seems that NMDA does not like ‘log_bin’. We adjusted it to ‘log-bin’ and backup works.

-Nick

The 'log_bin' and 'log-bin' variables are actually from MySQL.  They are not NetWorker or NMDA variables.

I am definitely not a MySQL expert, but based on what I found...

     16.1.2.4 Binary Log Options and Variables

     https://docs.oracle.com/cd/E17952_01/mysql-5.0-en/replication-options-binary-log.html

There is definitely a difference between using 'log_bin' and 'log-bin'.

Please take a look at the above link, and/or refer to your MySQL documentation for further information.

So looks like you used the correct variable in your my.cnf file.    Cheers...