|AWS SDK for Java||AWS now provides a Java SDK that covers Amazon RDS and other AWS products. The SDK provides basic functions not included in the Amazon RDS API, such as request authentication, request retries, and error handling. For more information about the AWS SDK for Java, go to http://aws.amazon.com/sdkforjava.|
|InnoDB engine support only||Amazon RDS automated backups and DB Snapshots are currently supported for the InnoDB engine only. Use of these features with other MySQL engines, including MyISAM, may lead to unreliable behavior while restoring from backups. Specifically, since storage engines like MyISAM do not support reliable crash recovery, your tables can be corrupted in the event of a crash. For this reason, we encourage you to use the InnoDB storage engine.
If you choose to use MyISAM, you can attempt to manually repair tables that become damaged after a crash using the REPAIR command (see: http://dev.mysql.com/doc/refman/5.1/en/repair-table.html). However, as noted in the MySQL documentation, there is a good chance that you will not be able to recover all your data.
If you wish to take DB snapshots with MyISAM tables, follow these steps:|
(1) Stop all activity to your MyISAM tables (i.e., close all sessions).
(2) Lock and flush each of your MyISAM tables.
(3) Issue a CreateDBSnapshot API call or use the RDSCLI rds-create-db-snapshot command. When the snapshot has completed, release the locks and resume activity on the MyISAM tables.
These steps force MyISAM to flush data stored in memory to disk thereby ensuring a clean start when you restore from a DB snapshot.
Finally, if you would like to convert existing MyISAM tables to InnoDB tables, you can use alter table command (e.g., alter table
To find out the list of MyISAM tables owned by you, you can run the following query:
"select table_schema, table_name from information_schema.tables where engine='MyISAM' and table_schema not in ('mysql','information_schema');