googleespocrm

Modify the MySQL data directory

NOTE: We are in the process of modifying the file structure and configuration for many Bitnami stacks. On account of these changes, the file paths stated in this guide may change depending on whether your Bitnami stack uses native Linux system packages (Approach A), or if it is a self-contained installation (Approach B). To identify your Bitnami installation type and what approach to follow, run the command below:

 $ test ! -f "/opt/bitnami/common/bin/openssl" && echo "Approach A: Using system packages." || echo "Approach B: Self-contained installation."

The output of the command indicates which approach (A or B) is used by the installation, and will allow you to identify the paths, configuration and commands to use in this guide. Refer to the FAQ for more information on these changes.

Approach A: Bitnami installations using system packages

  • Bitnami installation that use system packages contain the MySQL data at the /bitnami/mysql/data directory, by default. Check it by running the following command:

    $ cat /opt/bitnami/scripts/mysql-env.sh | grep DB_DATA_DIR
    export DB_DATA_DIR="${DB_VOLUME_DIR}/data"
    

    NOTE: The DB_VOLUME_DIR environment variable is set to /bitnami/mysql.

  • To change the location of the MySQL data directory, modify the /opt/bitnami/scripts/mysql-env.sh file as shown below:

    ...
    export DB_DATA_DIR=/bitnami/mysql/data
    ...
    
  • Finally, move the data/ directory to the new location and restart the database.

Approach B: Self-contained Bitnami installations

  • For self-contained Bitnami stacks, the data directory for MySQL is set located at /opt/bitnami/mysql/data by default. To change the location of this folder, modify the /opt/bitnami/mysql/my.cnf file as shown below:

    ...
    datadir=/opt/bitnami/mysql/data
    ...
    
  • Modify the /opt/bitnami/mysql/scripts/ctl.sh file to reflect the new directory location:

    --datadir=/opt/bitnami/mysql/data
    
  • Finally, move the data/ directory to the new location and restart the database.

Last modification June 3, 2020