If you deal with large databases, you will probably need more than the provisioned storage of the default Amazon AMI (8GB).
- Create a new storage volume at the Amazon console (or using AWS API). Make sure it is big enough to accommodate storage, log files, bin files and future growth. Notice! verify the new drive is in the same availability zone as the target instance.
- Write down the mount name you chosen. For example: /dev/sdf.
- Mount the disk to your system according to Chris Dean post:
- sudo mkfs.ext3 /dev/sdf where /dev/sdf is the mount name you chose.
- sudo mkfs.ext3 /dev/sdf where /dev/sdf is the mount name you chose.
- Shutdown the MySQL daemon: sudo /etc/init.d/mysql stop
- Move your current MySQL data directory to a temporary directory: sudo mv /var/lib/mysql /var/lib/mysql.old
- Recreate the MySQL data directory and provide the needed permissions:
- sudo mkdir /var/lib/mysql
- sudo chown mysql:mysql /var/lib/mysql
- sudo mkdir /var/lib/mysql
- Mount the new disk to the new directory:
- Add another line to /etc/fstab (sudo vi /etc/fstab): /dev/sdf /var/lib/mysql ext3 defaults 1 2
- Mount the disk: sudo mount /var/lib/mysql
- Verify everything is Okay with df
- Add another line to /etc/fstab (sudo vi /etc/fstab): /dev/sdf /var/lib/mysql ext3 defaults 1 2
- Move the files from the temporary directory back to the new data directory sudo mv /var/lib/mysql.old/* /var/lib/mysql
- Remove the old directory: sudo rmdir /var/lib/mysql.old
- Restart you MySQL: sudo /etc/init.d/mysql start
Bottom Line
A combination of cloud knowledge, Linux sysadmin, MySQL expertise and careful work will help you go through the scale and growth challenges.
{{ parent.title || parent.header.title}}
{{ parent.tldr }}
{{ parent.linkDescription }}
{{ parent.urlSource.name }}