V11 SP8
Loading...

IntelliSnap - Troubleshooting - MySQL iDataAgent

SS0026: An IntelliSnap Backup or a Block-Level Backup Job Fails When You Have a Dangling Symbolic Link

Symptom

An IntelliSnap backup or a block-level backup job fails with the following error message:

Error Code: [7:202]
Description: Snap initialization failed with an error:[Failure populating mountpoints to snap manager utility]

You can also find the below error in the MySqlBackup.log file:

18528 4860 04/20 20:19:42 359284 UnixSymbolicLink::getPhysicalPath(138) - isLink failed for '/5GB' :0xECCC0002:{CQiPath::IsLink(317)} + {CQiPath::IsLink(303)/ErrNo.2.(No such file or directory)-Failed to identify if file is link, FileName=/5GB}

Cause

Backup job fails because there is a dangling symbolic link present in the MySQL data directory.

Resolution

Remove the dangling symbolic link from the MySQL data directory, and then run the backup job again.

SS0025: Restore Operation From an IntelliSnap Backup Job Fails

Symptom

Restore operation from an IntelliSnap backup job fails with the following error message:

Error Code: [87:86]
Description: Failure:[~Error [ERROR 1062 (23000) at line 72 in file: '/tmp/635048/862220/ArchiveEvents.sql': Duplicate entry '6' for key 'PRIMARY' ] in applying the logs~]
Source: sde52-mysql, Process: MySqlRestore

You can also find the below error in the MySqlRestore.log file:

27687 6c27 01/24 13:41:17 310941 MySqlLogRestore::ApplyLogWithOffset() - Creating Process as: [ /usr/bin/mysql --defaults-file=/opt/commvault/Base/Temp/galaxy_bkp_mycnf_900_1485245470_27687_27687_310941 --default-character-set=utf8 --max_allowed_packet=524288000 -u root --socket=/var/lib/mysql/mysql.sock -e "source /clone/310941/395235/ArchiveEvents.sql" ]

27687 6c27 01/24 13:41:17 310941 MySqlChildProcess::Wait() - Child died after receiving signal 1

Cause

Restore job fails due to continuous data population that might have happened during the snap backup job.

Resolution

Before running a restore operation, change the mysql binlog name in the MySQL configuration file using the following command:

[mysqld]
log-bin=mysql-bin-new

Then, run a restore operation from the IntelliSnap backup job.

SS0024: An IntelliSnap Backup Copy Fails When You Have an ext3 or ext4 LVM Volume for the Hardware Array

Issue

An IntelliSnap backup copy fails on the following agents when you have an ext3 or ext4 LVM volume for the hardware engine:

  • MySQL
  • PostgreSQL
  • SAP HANA
  • SAP on Oracle

Resolution

If you use Red Hat 7.x or CentOS 7.x for the backup copy proxy, perform the following operations:

  1. Disable and stop the lvm2-lvmetad. On the command line, type the following commands:

    systemctl disable lvm2-lvmetad
    systemctl stop lvm2-lvmetad

  2. Disable the lvmetad parameter in the LVM config file. Edit the /etc/lvm/lvm.conf file, and add the following line to the file:

    use_lvmetad = 0

SS0023: MySQL server does not start automatically after the IntelliSnap restore operation is complete

Symptom

After the data restore (as part of MySQL IntelliSnap restore operation) is complete, the MySQL server starts automatically only if the installed MySQL service name is "MySQL". The server does not start automatically if the service is installed with any other name.

Resolution

Follow these steps to automatically start the MySQL server after the data restore (as part of MySQL IntelliSnap restore operation) is complete, even if the installed service name is not "MySQL".

  1. From the CommCell Browser, navigate to Client Computers.
  2. Right-click the <Client> to be configured and then click Properties.
  3. Click Advanced.
  4. Click the Additional Settings tab and then click Add.
  5. In the Name field, type sServerStartCmd.
  6. In the Value field, type any one of the following commands:
    • service <MySQLInstanceName> start for a UNIX client
    • NET START <MySQLInstanceName> for a Windows client
    • Any other command that you use to launch the MySQL server

    To start the MySQL server manually after the data restore (as part of MySQL IntelliSnap restore operation) is complete, set the value for bManualServerStart as 1 from the MySQL Client Computer Properties dialog box.

  7. Click OK to save the key.
  8. Click OK.
  9. Start the backup operation.

SS0022: Database is kept in a quiesce mode while performing an IntelliSnap backup operation on a Windows client

Symptom

Database is kept in a quiesce mode while performing an IntelliSnap backup operation on a Windows client. If the data is very huge, then the database may remain in the quiesce mode for a very long time.

Resolution

To reduce the time for the database to remain in the quiesce mode, follow these steps:

  1. From the CommCell Browser, navigate to Client Computers.
  2. Right-click the <Client> to be configured and then click Properties.
  3. Click Advanced.
  4. Click the Additional Settings tab and then click Add.
  5. In the Name field, type sFIND_FILELIST_FROM_SNAPSHOT.
  6. In the Value field, type Y.
  7. Click OK to save the key.
  8. Click OK.
  9. Start the backup operation.

SS0020: IntelliSnap restore operation fails if MySQL server is running

IntelliSnap restore operation fails with the following error message:

Description: Failure:[~Restoring from snap based backup, the destination MySQL server should be offline. Please shutdown the server and resume the job.]

Symptom

Restoring databases from a snapshot or backup copy fails if you attempt to restore while the MySQL server is running.

Resolution

Before you start the restore, make sure that the MySQL server is offline.

If you attempt to restore while the server is running, the software will notify you to shutdown the server and then resume with the restore:

Completed with one or more errors

Backup jobs from MySQL iDataAgent will be displayed as "Completed w/ one or more errors" in the Job History in the following cases:

  • If the subclient contains multiple databases, and some of the database backups encounter errors and other database backups run successfully.

  • If the subclient contains multiple databases, and some databases in the subclient are corrupted or removed from the database server.

Restore jobs from MySQL iDataAgent will be displayed as "Completed w/ one or more errors" in the Job History in the following cases:

  • During Logs Restore, if applying log into a database fails, it marks such databases as non-recoverable and continues with other databases.