"Starting of aux server failed": A Block-Level Table-Level Restore Operation or a Clone Restore Operation Fails

Article ID: MSQL0017 A MySQL restore job from a block-level backup operation fails with errors.

Symptom

A block-level table level restore operation or a clone restore operation fails with the following error message:

Error Code: [87:18]
Description: MySQL Database: [~Starting of aux server failed~] Restore Failed.

Cause

The restore operation might be failing because of one of the following reasons:

  • The MySQL bin directory path is incorrect.
  • The mysqld_safe binary is not in the bin directory.
  • MySQL server ID is not provided.
  • Clone working directory or staging location is not writable for the "mysql" user.

Resolution

To resolve this problem, use one of the following methods:

  • If the MySQL bin directory path is incorrect, provide the correct path, and then resubmit the table level or clone restore operation.
  • If the mysqld_safe binary is not in the bin directory, complete the following steps, and then resubmit the table level or clone restore operation:
    1. Use the following example command to create a symbolic link for mysqld, with the name mysqld_safe:
      ln -s /usr/sbin/mysqld /usr/bin/mysqld_safe
    2. Create the additional setting sAdvancedStartServerOptions, and set its value as shown below:
      --user=<unix_username>
  • If you do not have the MySQL server ID, at the destination client, create the additional setting sAdvancedStartServerOptions, and set its value as shown below:
--server-id = <server-id>
  • If the clone working directory or the staging location is not writable for the "mysql" user, at the destination client, create the additional setting sAdvancedStartServerOptions, and set its value as shown below:
--user = <UNIX user to start MySQL server>