Instances - MySQL

Overview

As MySQL instances reference a MySQL server, you must create a MySQL instance for each of the MySQL servers that you want to back up. In order to create a MySQL instance, the MySQL User should have DBA and SYSDBA privileges.

See Instances for an overview of Instances. Given below is a list of what you need to provide before creating a MySQL instance.

A name for the MySQL server instance
The MySQL User account which will be used to perform all system operations
The path to the MySQL server Binary directory. For example, /usr/bin.
The path to the Log Data directory. For example, /var/lib/mysql/mysqllogs.
The path of the configuration file for the instance. For example, /etc/my.cnf.
The path to the socket file For example, /var/lib/mysql/mysql.sock.

Configurable Properties

Once installed, the agent is configured and is therefore able to manage the data or volumes on the client computer. However, you can change certain aspects of the instance configuration to manage the data in the manner that best suits your needs.

You can view or change the instance configuration from the Instance Properties dialog box. The following information can be configured.

Enable Automatic Discovery of Databases

For the MySQL iDataAgent, you can assign the system to search the instance for unconfigured databases and add them to the system. See Modify an Instance for step-by-step instructions.

Change the Designated Home Directory

For the Oracle, Oracle RAC, and SAP for Oracle iDataAgents, you can change the Oracle Home directory. Similarly, you can change the Informix (Home) directory for the Informix iDataAgent, the Sybase Home directory for the Sybase iDataAgent, the MySQL Home directory for the MySQL iDataAgent, the PostgreSQL home directory for the PostgreSQL iDataAgent, and the Instance Home directory for the DB2 DPF pseudo-client.

See Change the Home Directory for step-by-step instructions.

Change the Log Data Directory

When you enable binary log, an index file (.index extension) is generated and reside in data directory. Archive log Index file is a text file which comprises of all the running list of transaction logs for MySQL database. Typically, this file is used to backup the logs. For the MySQL iDataAgent, you can change the path of the archive log index file for the instance. See Change the Archive Log Index File for step-by-step instructions. If binary log is disabled on the MySQL server, then the path of the data directory is displayed.

Change the Configuration File

You can change the path of the configuration file for the instance. See Change the Configuration File for step-by-step instructions.

If you encounter any compatibility mismatch between Calypso and Linux/Linux flavored operating system, you should rename and map it to common library that you are using for both OS and Calypso.

For Example: If a log reports an error: MySQL iDataAgent unable to configure instance - /opt/<instance_name>/Base/libgcc_s.so.1: version `GCC_4.2.0' not found (required by /usr/lib64/libstdc++.so.6)

Do not delete "/opt/<instance_name>/Base/libgcc_s.so.1". Instead, rename it as "/opt/<instance_name>/Base/libgcc_s.so.1.bkp".

Change the Socket File

For the MySQL iDataAgent, you can change the path of the socket file for the instance. See Change the Socket File for step-by-step instructions.

User Accounts

Use the Accounts tab to identify the account that the system uses to access the associated instance.

See MySQL iDataAgent section in User Accounts and Passwords for more information.

For step-by-step instructions on changing the user accounts for the instance, see Change Account for Accessing Instances.

View and Change Instance-level Storage Policies

From the Log Backups tab, you can change the storage policy for backing up the logs on the selected instance. (See Storage Policies for an overview.)

For step-by-step instructions, see Select a Storage Policy for Log Backups.

User Security

You can perform the following functions:

Identify the user groups to which this CommCell object is associated.
Associate this object with a user group.
Disassociate this object from a user group.

For more information, see User Administration and Security.

Configuring User Accounts

The MySQL iDataAgent requires a MySQL Server user account that has sufficient privileges for the software to:

Perform backups and restores
Access the MySQL Server application
Stop or start the MySQL Server services

The following table illustrates the necessary privileges the user account should have to perform backup and restore operations:

Operations	Privileges MySQL user should have:	Example Query to grant the Permission
Backup	SHOW DATABASES SUPER RELOAD SELECT LOCK	mysql> GRANT SHOW DATABASES, SELECT, LOCK TABLES, RELOAD,SUPER ON . to <backup_agent username>@localhost IDENTIFIED BY '<backup_agent password>'; However, it is recommended to grant all Database Administrator privileges to perform backup operations too. mysql> GRANT ALL PRIVILEGES ON . TO <backup_agent username>@localhost IDENTIFIED BY '<backup_agent password>';
Restore	Full Database Administrator privileges	mysql> GRANT ALL PRIVILEGES ON . TO <restore_agent username>@localhost IDENTIFIED BY '<restore_agent password>' WITH GRANT OPTION;

At the Instance Level

Use the following steps to change the MySQL Server user account for an Instance:

From the CommCell Browser, navigate to Client Computers | <Client> | MySQL.
Right-click the <Instance> and click Properties.
Click the Accounts tab.
Type the SA user name in the SA User Name box.
Type the password in the SA Account Password box and retype it in the SA Confirm Password box.
Click OK.