MySQL¶

MySQL is the transactional database for HPE Morpheus Software, storing all operational data including Instances, users, tenants, policies, automation configurations, and billing records. This page covers preparing an external MySQL service for use with HPE Morpheus Software.

Supported Versions¶

• MySQL 8.4.8 (embedded in HPE Morpheus Software 9.0.0)

• MySQL 8.0.x FIPS (v8.0.36)

The appliance supports configuration of an external MySQL service, including the 8.4 LTS family. Configuration support does not by itself certify every MySQL patch, managed-service variant, later major version, or innovation release. Confirm the certified external versions in the compatibility information for the specific HPE Morpheus Software release before installation or upgrade; 8.4 or greater is not an unconditional compatibility statement.

When to Externalize¶

Consider running MySQL externally when:

• You need high availability with multi-master replication or InnoDB Cluster

• You want to use a managed database service (e.g., Amazon RDS, Azure Database for MySQL, Google Cloud SQL)

• Your organization requires databases to be managed by a dedicated DBA team

• You need cross-region replication for disaster recovery

• The appliance’s all-in-one footprint is constrained and you want to offload database I/O

Preparing the External Database¶

Perform the following on your external MySQL host or cluster to prepare it for HPE Morpheus Software.

Step 1 — Create the database

CREATE DATABASE morpheus CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci;

Step 2 — Create the Morpheus database user

This user will be used by HPE Morpheus Software application nodes to authenticate with MySQL:

CREATE USER 'morpheus'@'%' IDENTIFIED BY '<secure-password>';

Step 3 — Grant permissions

GRANT ALL PRIVILEGES ON morpheus.* TO 'morpheus'@'%' WITH GRANT OPTION;
GRANT SELECT, PROCESS, SHOW DATABASES, RELOAD ON *.* TO 'morpheus'@'%';
FLUSH PRIVILEGES;

MySQL HA / InnoDB Cluster¶

For high availability, MySQL can be configured in a clustered topology. Common approaches:

InnoDB Cluster (Recommended)

InnoDB Cluster provides built-in high availability using Group Replication with automatic failover:

• Minimum 3 nodes for quorum-based failover

• Supports single-primary (one writer) or multi-primary (multiple writers) mode

• Single-primary mode is recommended for HPE Morpheus Software to avoid write conflicts

• Use MySQL Router as a connection proxy between HPE Morpheus Software and the cluster for automatic failover routing

Multi-Master Replication

Traditional MySQL replication with multiple writable masters:

• Can be configured with no replication delay within the same region

• Allow some replication delay for cross-region replicas

• Increases risk of job overlap between regions, though concurrent operations typically self-correct

Managed Services

Cloud-managed MySQL services (RDS, Azure Database, Cloud SQL) handle replication, failover, and backups automatically. Ensure:

• The exact service variant and MySQL 8.4.x patch are certified for the installed HPE Morpheus Software release

• utf8mb4 character set is available

• The HPE Morpheus Software appliance nodes can reach the service endpoint on port 3306

• The service allows the GRANT permissions listed above

Network Requirements¶

TLS Connections¶

To connect to an external MySQL instance over TLS, configure the MySQL server with a valid certificate and enable TLS on the HPE Morpheus Software side via morpheus.rb. Consult the MySQL documentation for server-side TLS setup.

HPE Morpheus Software will use TLS when the external MySQL server requires it — no additional morpheus.rb settings are needed beyond the host/user/password configuration if the MySQL server enforces TLS for all connections.

Database Sizing¶

MySQL storage requirements grow with:

• Number of managed Instances and hosts

• Billing and usage record retention

• Audit log history

• Backup metadata

For most environments, start with 50 GB of database storage and monitor growth. Large environments (10,000+ managed resources) may require 200 GB+ and should consider dedicated I/O-optimized storage.

Refer to Capacity and Planning for general sizing guidance.

Backup Considerations¶

For external databases:

• Configure automated backups through your MySQL HA solution or managed service

• Test restore procedures regularly

• For mysqldump-based backups, use --single-transaction to avoid locking tables

• Retain at least one backup from before each HPE Morpheus Software upgrade