MySQL Requirements for Application-Based Backups

For standalone MySQL databases, you can perform application-based backups from a VSA subclient, then use the MySQL database agent to restore a database. You can run application-based backups for Windows and Linux VMs that host MySQL databases.

Before performing a VSA backup, install the MySQL Agent on the virtual machine where the MySQL database instance is running and configure the MySQL instance on the CommCell. After you perform a VSA backup, the MySQL default subclient properties are updated to use Virtual Server Application Snap as the snapshot engine.

You can only run full or incremental backups for a VSA subclient that is configured for application-based backups of MySQL. Whether you perform a full or incremental VSA backup, the resulting MySQL IntelliSnap backup is always a full backup.


  • You must run the application-based backup from the VSA subclient, which automatically initiates the MySQL IntelliSnap backup. You cannot manually run a backup from the MySQL Agent.

  • Do not reconfigure the MySQL default subclient to perform block-level backups. You cannot perform application-based backups for MySQL subclients that are configured for block-level backups.

  • Synthetic full backups are not supported.

Linux Requirements

  • For streaming or IntelliSnap VMware backups of MySQL, use a Linux proxy that is configured as a File Recovery Enabler for Linux and has the Virtual Server Agent installed.

    The Linux proxy is also used to mount application snapshots for restores.

  • MySQL requirements: For Linux VMs running MySQL, ensure that the following requirements are met:

    • The DNS hostnames for Linux VMs must be the same as the machine names for the VMs.

    • Logical Volume Manager (LVM) should be configured to use native snapshots.

    • Ensure that the psmisc package is installed.

    • lvmetad daemons should not be running on the VSA proxy that is used for backups. See Disabling lvmetad for Linux VMs.

  • To back up a Linux VM running MySQL, ensure that the volume group has free space that is at least 4 GB greater than the size of the database. If multiple LVs are registered to a volume group, ensure that additional free space of 4 GB is available for each LV.

    For Linux LVM snaps, there must be adequate free space in the LVM volume group for snapshot creation. The default COW cache size is set to 4096 MB or 5% of the volume size, whichever is greater. To increase the COW cache size, configure the nSnapCowSizeMB additional setting. For instructions on adding the additional setting, see Adding or Modifying Additional Settings from the CommCell Console.

Application Credentials

To perform backups and restores for MySQL databases, a user account with admin privileges for the application and database is required.

Subclient Configuration

Include virtual machines running MySQL in a separate subclient under a Virtual Server instance.


Perform full or incremental backups for VM groups (subclients) that are configured for application-based backups. Synthetic full backups are not supported. Scheduled synthetic full backups are converted automatically to full backups for VM groups and subclients that are configured for application-based backups.