Topics | How To | Related Topics
Things to Consider when Creating and Configuring MySQL Subclients
The following table shows subclient creation and configuration details specific to the MySQL iDataAgent.
Agent |
Type of Data | Default Subclient created during install of the Agent | Supports Default Subclient | Supports User Defined Subclient | Contents of the default subclient when user-defined subclient is present | Other Types of subclients supported by the Agent | Notes |
| MySQL iDataAgent | MySQL Server databases, transaction logs | No | Yes | Yes | database objects not assigned to other subclients, unless otherwise configured* | None | Default subclient is created
when the instance is configured *See Caution Against Re-configuring Default Subclient Content. |
The MySQL iDataAgent is designed to back up and restore MySQL Server databases along with the associated administration files and transaction logs. After you install a MySQL iDataAgent, a default subclient is created by the system only after you first configure a MySQL instance from the CommCell Console. Since a MySQL instance references a MySQL Server, the default subclient includes all the databases for the MySQL Server associated with that instance. However, you can use the CommCell Console to create user-defined subclients to distribute some of the database content by configuring the Subclient Properties (Content) tab. Any content that you do not distribute to the user-defined subclients will remain in the default subclient.
When you configure subclient content, you click the Subclient Properties (Content) tab for the subclient and then Configure to view the eligible databases for inclusion into the subclient content. You then include the desired databases into your subclient content by associating the databases with the user-defined subclient. Once you do this, the subclient contents may be displayed as follows:
In this example, db2, db3, db4,db5,db6, and db7 are the databases that are included in the subclient content.
A useful way to distribute subclient content for this iDataAgent is to create separate user-defined sublients for frequently used databases. For example, if the db2 and db3 databases shown above undergo frequent changes, you can create a separate subclient for each database. For example:
Content:
db2
Content:
db3
Distributing the client data using subclients in this way can help improve backup performance by organizing the workload on the client into logical groupings.
Data protection filtering is not applicable for this agent.
Wildcards and regular expressions are not supported for this agent when defining subclient content.
For more information, see Things to Consider when Creating and Configuring MySQL Subclients.
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 subclient configuration to manage the data in the manner that best suits your needs.
You can view or change the subclient configuration from the Subclient Properties dialog box. The following information can be configured.
You can enable or disable all operations for this CommCell object and all objects below it. For more information, see Activity Control.
You can define the content of the subclient. Most agents include a configure button that displays a dialog where you can add or modify the data included as subclient content. For step-by-step instructions, see Configure Subclient Content.
Several configurable options to efficiently use available resources for transferring data secured by data protection operations are provided in the subclient. This includes the following:
You can enable or disable the encryption of data for transmission over unsecure networks and for storage on media. For more information, see Data Encryption.
You can view the data paths associated with the primary storage policy copy of the selected storage policy or incremental storage policy. You can also modify the data paths for the subclient including their priority. For additional information, see Configuring Alternate Data Paths for Subclients.
You can add, modify or view Pre/Post processes for the subclient. These are batch files or shell scripts that you can run before or after certain job phases. For more information, see Pre/Post Processes.
You can associate the subclient to a storage policy. For more information, see Storage Policies.
You can rename a subclient. For step-by-step instructions, see Rename a Subclient.
When creating and configuring subclients for the MySQL iDataAgent, keep in mind the following considerations:
We recommend that you do not re-configure the content of a default subclient because this would disable its capability to serve as "catch-all" entity for client data. As a result, the likelihood that some data will not get backed up or scanned for archiving would increase.