Yes, it is.
A possible scenario is to use latest CentOS 7.5 + MySQL 5.7.
I suggest you to first familiarize with the HPE IMC on Linux scenario by reading the HPE Intelligent Management Center MySQL 5.7 Installation and Configuration Guide (for Linux) which is valid for HPE IMC 7.3 E0703 and was published few weeks ago, in June 2019.
I'm not totally sure that that guide, even if recently published, is de-facto updated and that can be used as a really step-by-step installation guide...but, at least, it will give you an idea of what you need for a working setup (I recall there are few things that I fixed along the way with regard to MySQL configuration but, generally, it is a good starting point).
Other HPE IMC related guides can be (not easily) found on support.hpe.com...try this filtering: https://support.hpe.com/hpesc/public/km/search#q=%22Intelligent%20Management%20Center%22&t=Documents&sort=%40hpescuniversaldate%20descending&layout=table&f:@kmdoclanguagecode=[cv1871448,cv1871440]&hpe=1
I'm not an HPE Employee
Hello,
The MySQL 5.7 Guide is not entirely accurate at the moment, and a new version will be published soon with some enhancements and changes that I've asked for.
For Linux installation requirements and demo you can also refer to this video: https://www.youtube.com/watch?v=Ymz-I9F4Hko
Below is a working MySQL 5.7 /etc/my.cnf file, since there are issues with the one provided by the guide. Note that you only need the deployment issue workaround (validate_password_policy settings) when installing MySQL using 'yum' instead of 'rpm', since the rpm-based method does not install validate_password plugin by default.
NOTE: Binary logging is enabled here with log_bin = bin.log which is useful for debugging purposes, but would recommend disabling it for production use, as it logs every single transaction to binary logs, which can take up a lot of space on the filesystem over time.
[client]
port = 3306
socket = /var/lib/mysql/mysql.sock
[mysqld]
port = 3306
socket = /var/lib/mysql/mysql.sock
symbolic-links=0
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
server-id = 1
user = mysql
bind_address = 0.0.0.0
autocommit =1
character_set_server=latin1
skip_name_resolve =1
max_connections = 800
max_connect_errors = 1000
datadir = /var/lib/mysql
transaction_isolation = READ-COMMITTED
explicit_defaults_for_timestamp =1
join_buffer_size = 134217728
tmp_table_size = 67108864
tmpdir = /tmp
max_allowed_packet = 200M
sql_mode = "STRICT_TRANS_TABLES,NO_ENGINE_SUBSTITUTION,NO_ZERO_DATE,NO_ZERO_IN_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER"
interactive_timeout = 1800
wait_timeout = 1800
read_buffer_size = 16777216
read_rnd_buffer_size = 33554432
sort_buffer_size = 33554432
default-storage-engine = INNODB
lower_case_table_names = 1
########IMC deployment issue workaround########
validate_password_policy=LOW
validate_password_special_char_count=0
validate_password_length=0
validate_password_mixed_case_count=0
validate_password_number_count=0
########log settings########
log_error = error.log
slow_query_log = 1
slow_query_log_file = slow.log
log_queries_not_using_indexes = 1
log_slow_admin_statements = 1
log_slow_slave_statements = 1
log_throttle_queries_not_using_indexes = 10
expire_logs_days = 90
long_query_time = 2
min_examined_row_limit = 100
########replication settings########
master_info_repository = TABLE
relay_log_info_repository = TABLE
log_bin = bin.log
sync_binlog = 1
gtid_mode = on
enforce_gtid_consistency = 1
log_slave_updates
binlog_format = row
relay_log = relay.log
relay_log_recovery = 1
binlog_gtid_simple_recovery = 1
slave_skip_errors = ddl_exist_errors
########innodb settings########
innodb_page_size = 16384
innodb_buffer_pool_size = 512M
innodb_buffer_pool_instances = 8
innodb_buffer_pool_load_at_startup = 1
innodb_buffer_pool_dump_at_shutdown = 1
innodb_lru_scan_depth = 2000
innodb_lock_wait_timeout = 5
innodb_io_capacity = 4000
innodb_io_capacity_max = 8000
innodb_flush_method = O_DIRECT
innodb_file_format = Barracuda
innodb_file_format_max = Barracuda
innodb_log_group_home_dir = ./
innodb_undo_directory = ./
innodb_undo_logs = 128
innodb_undo_tablespaces = 0
innodb_flush_neighbors = 1
innodb_log_file_size = 512M
innodb_log_buffer_size = 16777216
innodb_purge_threads = 4
innodb_large_prefix = 1
innodb_thread_concurrency = 64
innodb_print_all_deadlocks = 1
innodb_strict_mode = 1
innodb_sort_buffer_size = 67108864
########semi sync replication settings########
plugin_dir=/usr/lib64/mysql/plugin/
plugin_load = "rpl_semi_sync_master=semisync_master.so;rpl_semi_sync_slave=semisync_slave.so"
loose_rpl_semi_sync_master_enabled = 1
loose_rpl_semi_sync_slave_enabled = 1
loose_rpl_semi_sync_master_timeout = 5000
[mysqld-5.7]
innodb_buffer_pool_dump_pct = 40
innodb_page_cleaners = 4
innodb_undo_log_truncate = 1
innodb_max_undo_log_size = 2G
innodb_purge_rseg_truncate_frequency = 128
binlog_gtid_simple_recovery=1
log_timestamps=system
transaction_write_set_extraction=MURMUR32
show_compatibility_56=on
[mysqldump]
quick
single-transaction
Justin
Working @ HPE
Hello,
CentOS is not a supported OS for IMC. Though that will work for IMC if you follow the documentation/video tutorials linked above.
Microsoft SQL though is only supported on Windows OS (Server 2012 and 2016). I understand there is a Microsoft SQL Server for Linux, but I highly doubt it will be detected by IMC. By the way, Microsoft SQL on Linux also doesn't support running it on CentOS (even if it is almost identical to RHEL).
If you are going to use RHEL, why not opt for MySQL (or Oracle DB), which are supported?
Justin
Working @ HPE
@ofcgreg0 wrote:I would like to use HPE IMC on a centOS server with the Microsoft SQL Server database.
Why mixing pears and apples? it looks really unreasonable...you need to explain us the exact meaning of that requirement...IMHO you seem a little bit too confused asking for that.
I'm not an HPE Employee
Hello,
Unfortunately migrating from one type of database to another is not possible. You cannot restore from an MSSQL backup to a MySQL system. MySQL to MySQL and MSSQL to MSSQL works, but not between the two. If you setup a new IMC system on Linux, you would need to start from scratch - though there are a few features, like Device View, where you can run an Export of the Device List, and Import that on the other system, which works regardless of DB type.
Justin
Working @ HPE