To back up and restore MySQL data on an Amazon application, verify that your environment meets the requirements.
Before Configuring Backups, Verify Backup Gateway Region and Access to the Database
Before configuring backups of the database, do the following:
-
Verify that the AWS backup gateway is deployed in the same region and VPC as the AWS database.
-
Verify that the AWS backup gateway can access the AWS databases. For more information, go to Automatically connecting an EC2 instance and an RDS database on the Amazon RDS website.
-
See the following:
-
For instructions to create an AWS backup gateway, which is part of configuring backups, see the "Configuring Backups" page for the database, under AWS Cloud Databases. For example, see Configuring Backups for Amazon DocumentDB Instances.
Software Requirements
-
Packages that are required on access nodes:
-
Virtual Server Agent
-
MySQL Agent
-
-
For information on supported Amazon EC2 instances as access nodes, see Supported Amazon EC2 Instance Families.
-
Access nodes that you run backup and restore operations on must have one of the following operating systems:
|
Operating system |
Processor architecture |
|---|---|
|
Amazon Linux 2023 AMI |
Note Supported only from MySQL 8.0.x onwards |
|
Amazon Linux 2 AMI (HVM) - Kernel 5.10, SSD Volume Type |
|
|
CentOS 9.x, 8.x |
|
|
Oracle Linux Enterprise 9.x, 8.x |
|
|
Red Hat Enterprise Linux (RHEL) 9.x, 8.x |
|
|
Rocky Linux 9.x, 8.x |
|
|
Windows 2022, 2019, 2016 |
|
Note
If you have network configuration enabled on the access nodes, before you deploy the Linux proxy, configure a firewall on the cloud proxy and on-premises. For more information, see Configuring a Firewall to Install the Virtual Server Agent on a Cloud VM or Instance.
Hard Drive
A minimum of 100 GB of disk space is recommended. If a staging directory is required on the access node, the actual space needed will depend on the database being backed up and the configured settings.
Network Connectivity
-
Access nodes must have Layer 3 network connectivity to the upstream MediaAgent on port 8403. If the MediaAgent and the access node are in different accounts or in different Virtual Private Clouds (VPCs), you can configure Amazon VPC peering. For information, see VPC peering basics in the AWS documentation.
-
Access nodes must have connectivity to regional and global AWS service endpoints. For information, see Requirements for Connectivity to AWS Service Endpoints.
-
Access node machines must be able to connect to the RDS instance over its database port (For example, 3306 for MySQL), unless a custom port is configured.
Note
If you have network configuration enabled on the access nodes, before you deploy the Linux proxy, configure a firewall on the cloud proxy and on-premises.
Supported MySQL Versions
-
MySQL 8.4.x
-
MySQL 8.0.x
-
MySQL 5.7.x
Note
To back up and restore data using MySQL version 8 on Windows, install Microsoft Visual C++ libraries.
User Account Requirements
The MySQL user account must have the following minimum permissions to perform cloud based backup and restore operations using dump-based solutions:
|
|
Example:
CREATE USER 'new_master_user'@'%' IDENTIFIED BY 'StrongPassword!';
GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, RELOAD, PROCESS, REFERENCES, INDEX, ALTER, SHOW DATABASES, CREATE TEMPORARY TABLES, LOCK TABLES, EXECUTE, REPLICATION SLAVE, REPLICATION CLIENT, CREATE VIEW, SHOW VIEW, CREATE ROUTINE, ALTER ROUTINE, CREATE USER, EVENT, TRIGGER ON *.* TO 'new_master_user'@'%' WITH GRANT OPTION;
FLUSH PRIVILEGES;
SSL and TLS Support
SSL is supported for MySQL version 5.7 and later. The supported TLS versions to create Amazon SSL encrypted MySQL instances are TLS 1.0, 1.1, and 1.2.