1
2
3
4
5
6
7
8
9
10
11
12 |
/ ** MySQL settings - You can get this info from your web host ** ///** The name of the database for WordPress */define('DB_NAME', 'bitnami_wordpress');/** MySQL database username */define('DB_USER', 'bn_wordpress');/** MySQL database password */define('DB_PASSWORD', 'thepassword');/** MySQL hostname */define('DB_HOST', 'localhost:3306'); |
With this information available we can create the backup of the database. First create a directory in the home directory and then create the actual backup:
cd
mkdir backup
mysqldump -u bn_wordpress -pthepassword bitnami_wordpress > backup/backup.sql
Now make sure the backup exists:
ls -ltr backup/
total 36
-rw-rw-r-- 1 bitnami bitnami 33238 Dec 11 16:23 backup.sql
The next step is to setup a separate database on its own server in the cloud. To do this I make use of AWS RDS. In the remainder of the post I will show how to set this up. In this case I will aim for maximum performance so I will place the database server in the same AZ as the WordPress server. To find the AZ select the WordPress instance in the EC2 overview:
In the AWS Console, go to the Amazon RDS tab, click “Launch DB Instance” and select the MySQL instance:
In the next screen choose the Micro instance (this one is only used for demo purpose so micro is sufficient here). Set the Multi-AZ deployment to No as we are going for maximum performance, the allocated Storage is 5 GB (minimum).
The DB Instance Identifier you can put a name for this instance. The user and Password shoul dmatch the user and password we selected earlier from the ‘wp-config.php’ file. Here is a screeshot with all settings in place:
In the next step match the database name from the ‘wp-config.php’ file and select the correct Availability Zone:
For the backups I just accept the defaults but of course in real life you would make some choices here that would match for your case:
In the final step you get an overview of all your choices and if all is okay launch the RDS:
You can see your instance in the overview while being created (will take a few minutes since it also creates a backup):
When the database is created you can select it to see the details and copy the public address assigned to it:
One thing we have to do before we can put the backup of the original WP database on the new one is to open up the access to the machine. By default it comes with the standard EC2 security: trust no one. To make the server available open up the security group screen and add the Security Group that is also associated with the WordPress EC2 instance (please note that the name of the DB security group is ‘default’ and has nothing to do with the EC2 security group created earlier):
Now go back to the SSH session on the WordPress server and put the backup into the new DB:
mysql -u bn_wordpress -pmypassword --database=bitnami_wordpress --host=wpdatabase.c6flxs4tenda.eu-west-1.rds.amazonaws.com < backup/backup.sql
where you have to make sure that the host matches your database endpoint.
Now configure the WordPress instance to use this database instead of the local one. Modify the ‘wp-config.php’ so the host matches the remote host:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18 |
// ** MySQL settings - You can get this info from your web host ** ///** The name of the database for WordPress */define('DB_NAME', 'bitnami_wordpress');/** MySQL database username */define('DB_USER', 'bn_wordpress');/** MySQL database password */define('DB_PASSWORD', 'd314c809ea');/** MySQL hostname */define('DB_HOST', 'wpdatabase.c6flxs4tenda.eu-west-1.rds.amazonaws.com:3306');/** Database Charset to use in creating database tables. */define('DB_CHARSET', 'utf8');/** The Database Collate type. Don't change this if in doubt. */define('DB_COLLATE', ''); |
That’s it. Now test your installation by opening a web browser with your fixed IP and you should see your blog again:
If it is working then this is a good point to create a snapshot of your database so you can easily reinstall it later.