UNSOLVED
NMDA 8.2 for MySQL backups?
Has anyone had experience with this good or bad? I don't have experience with MySQL backups, but we are unable to backup the binary logs. It seems the NMDA initiated process is looking for them in the wrong path. No useful suggestions so far from the EMC SR I have opened.
NW server: CentOS 6, NW 8.2.2
NW client:
Oracle Linux 6 OS
MySQL version 5.6, MEB version is 3.12
NMDA 8.2 and NW client 8.2
example errors in the report (this is from a full backup attempt):
87651:nsrdasv: Cannot get status on path '/mysql56/data/devdb_vm-bin.000066': No such file or directory
87651:nsrdasv: Cannot get status on path '/mysql56/data/devdb_vm-bin.000067': No such file or directory
87651:nsrdasv: Cannot get status on path '/mysql56/data/devdb_vm-bin.000068': No such file or directory
87651:nsrdasv: Cannot get status on path '/mysql56/data/devdb_vm-bin.000069': No such file or directory
87651:nsrdasv: Cannot get status on path '/mysql56/data/devdb_vm-bin.000070': No such file or directory
87651:nsrdasv: Cannot get status on path '/mysql56/data/devdb_vm-bin.000071': No such file or directory
87651:nsrdasv: Cannot get status on path '/mysql56/data/devdb_vm-bin.000072': No such file or directory
87651:nsrdasv: Cannot get status on path '/mysql56/data/devdb_vm-bin.000072': No such file or directory
92825:nsrdasv: Could not save the binary logs (error code 1).
devdb-vm.FQDN:MYSQL:/devdb-vm_bkp: retried 1 times.
Here is the my.cnf file. It seems NMDA is pulling the datadir parameter to backup the binary logs, rather than the log_bin path. Why would that be?
# For advice on how to change settings please see
# http://dev.mysql.com/doc/refman/5.6/en/server-configuration-defaults.html
[client]
socket = /var/lib/mysql/mysql.sock
port = 3306
[mysqld_safe]
pid-file = /var/lib/mysql/devdb-fqdn.pid
[mysqld]
port = 3306
user = root
basedir = /usr/
datadir = /mysql56/data
pid-file = /var/lib/mysql/devdb-vm.fqdn.pid
tmpdir = /tmp
innodb_data_home_dir = /mysql56/data
innodb_log_group_home_dir= /mysqllog/binlog
innodb_data_file_path = ibdata1:10M:autoextend
log_bin = /mysqllog/binlog/devdb_vm-bin
default-storage-engine=InnoDB
query_cache_min_res_unit = 8192
query_cache_size = 100M
query_cache_limit = 200M
join_buffer_size = 250M
key_buffer_size = 512M
sort_buffer_size = 50M
read_buffer_size = 100M
read_rnd_buffer_size = 100M
tmp_table_size = 3M
## set to keep 7 days worth of binary logs
expire_logs_days = 7
general_log_file = /mysqllog/devdb_vm.log
innodb_buffer_pool_size = 4096M
innodb_log_file_size = 1900M
innodb_log_buffer_size = 8M
max_binlog_size = 1073741824
max_connections = 151
sql_mode = NO_ENGINE_SUBSTITUTION,STRICT_TRANS_TABLES
thanks in advance for any suggestions.
joe
ShubhamMishra
40 Posts
2869
0
Posted December 18th, 2016 23:00
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 "
Parallel Backup Operations Performance, time reducing parallel multi-threaded processing 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?
NickVanPijlen
1 Rookie
•
22 Posts
2869
0
Posted April 7th, 2017 04:00
Hi Wallace, can you provide some information on this sr? What was the typo that was made?
Thanks in advance!
NickVanPijlen
1 Rookie
•
22 Posts
2869
0
Posted April 10th, 2017 03:00
Ì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'.
Name Cmd-Line Option File System Var Var Scope Dynamic log-bin Yes Yes Yes Global No log_bin Yes Global No 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...
ble1
6 Operator
•
14354 Posts
•
56186 Points
2869
0
Posted January 28th, 2016 12:00
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.