Home > Workload Solutions > Oracle > Guides > Design Guide — MySQL InnoDB Cluster on Dell EMC PowerStore T > Production database storage design
For the PROD InnoDB Cluster database, we created four volume groups:
We also created dedicated LUNS for the Data, BIN Log, and TEMP disk groups. This design meets the requirement to create a consistent snapshot of all the DATA volumes and BIN Log volumes. The TEMP volume is not required to be a part of the snapshot. We separated data in this manner because the I/O patterns of data files and log files and Undo files differ.
Note: Redo log files, and binary log files are sequentially written data to the logs. Data files are randomly written data to the disk. Undo segments are random I/O oriented.
The optimal use of snapshot technology requires the ability to restore data files independently.
Note: Because of these InnoDB I/O characteristics, Dell Technologies recommends the following storage design layout.
The following table shows a list of the volumes for the MySQL PROD and DEV databases:
Volume group |
Name |
Description |
Size |
Number of volumes |
Data reduction |
Thick |
OS |
PROD_VM |
Guest VM operating system |
600 GB |
1 |
Yes |
Yes |
DATA |
PROD_DATA |
Data files |
2 TB |
1 |
Yes |
Yes |
LOG |
PROD_LOG |
Log |
2 TB |
1 |
Yes |
Yes |
TEMP |
PROD_TEMP |
Temporary |
100 GB |
1 |
Yes |
Yes |
To map these production database volumes to three PROD database servers, we created the host group MySQL_PROD_Host_Group. This host group consists of three servers, as shown in the following figure: