• |
MySQL failover clustering environment in place – You must have a properly configured MySQL Cluster environment. |
• |
Separate NetVault Backup Server machine – The machine that is to serve as the NetVault Backup Server must be properly configured and it must exist outside the MySQL Server cluster, but have network connectivity to the nodes (hosts) within the cluster. |
• |
Assign a name to the Virtual Client – Dell strongly recommends that the network name assigned to the MySQL Clustered Service be used as the NetVault Backup Virtual Client name. When a Virtual Client is browsed, NetVault Backup will locate the node currently in control of the clustered service, and reveal the MySQL Server instance (for example, on the NetVault Backup Selections page). With a Virtual Client name set up as the MySQL Clustered Service network name, it is easier to recognize the MySQL Server instance for which the Virtual Client was created. |
• |
Only include relevant cluster nodes in the Virtual Client – The hosts that are to be included in the creation of a Virtual Client should only be those nodes within the cluster that are relevant to the MySQL Clustered Service that is to be backed up and restored. |
1 |
In the Navigation pane of the NetVault Backup WebUI on the NetVault Backup Server, click Create Backup Job, and click Create New next to the Selections list. |
3 |
4 |
5 |
On the Configure dialog, set the applicable configuration options. |
IMPORTANT: You must add each cluster instance in the Instances field of the Configure dialog. To add an instance, specify the MySQL Clustered Service name as VIRTUAL SERVER NAME\INSTANCE NAME. |
7 |
Click OK to save the settings. |
NOTE: When you back up or restore data, make sure that you execute the process using the Virtual Client and not from one of the nodes. If you open or expand one of the nodes and drill down through the hierarchy, you will see the MySQL Clustered Service and, depending on which node is active, you might be able to drill down and select items. While the system might use this instance in maintaining log information, you should not attempt to execute any processes at this level. |
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Términos de uso Privacidad Cookie Preference Center