Skip to main content
Skip table of contents

Transition from Azure MariaDB to MySQL: A Smooth Path Forward

As Azure deprecates MariaDB, we're here to ensure that your transition to an alternative database is as seamless as possible. The most straightforward option for migration is MySQL, which is fully supported by EJBCA Cloud. This move not only aligns with Azure’s strategic direction but also offers robust performance and reliability improvements.

Why MySQL?

  • Seamless Integration: EJBCA Cloud includes providers that work seamlessly with both MariaDB and MySQL.

  • Enhanced Performance: MySQL is known for its speed and efficiency, ensuring that your applications run smoothly.

  • Community and Support: MySQL has a vast community and extensive documentation, making troubleshooting and enhancements easier.

Migration Overview

To make your migration process smooth, follow these simplified steps:

  1. Provision the New Database

    • Set up your new MySQL database instance on Azure.

  2. Configure Access

    • Ensure that your EJBCA nodes have access to the new database instance.

  3. Export Existing Database

    • Use the mysqldump tool to export your current MariaDB database to a SQL file.

  4. Pause Operations

    • Temporarily stop your EJBCA nodes to avoid any data inconsistency.

  5. Import Data

    • Use the MySQL CLI to import the SQL dump into your new MySQL database.

  6. Update Configuration

    • Edit the /opt/wildfly/bin/start.sh script to point to the new MySQL database.

  7. Resume Operations

    • Restart your EJBCA nodes to complete the migration process.

Additional Resources

For more detailed instructions and official guidance, refer to Microsoft’s documentation:

Need Assistance?

Our Professional Services team is here to help! While this migration falls outside the scope of our standard support, Keyfactor Sales can provide expert assistance to ensure a successful transition. Don't hesitate to reach out for the support you need.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.