ERROR 2013 (HY000): Lost connection to MySQL server during query

Recently had a problem with a MySQL iDA backup on a Linux platform. I was seeing a failure where we would get the error below (and per subject) included in the CommVault backup error.

ERROR 2013 (HY000): Lost connection to MySQL server during query

Upon further investigation it was determined that the error was being triggered during a MySQL query as performed by the MySQL iDA during backup attempt. When we attempted to do the same query manually against a MySQL connection we’d also get the same error. It was determined from the MySQL iDA logs that the database causing us the problem was called “prod”.

See the example below;

# mysql -u root -p
Enter password:
Welcome to the MySQL monitor.  Commands end with ; or g.
Your MySQL connection id is 4
Server version: 5.1.32-community-log MySQL Community Server (GPL)

Type 'help;' or 'h' for help. Type 'c' to clear the buffer.

mysql> use prod
Database changed
mysql> show table status;

ERROR 2013 (HY000): Lost connection to MySQL server during query

As you can see the error was reproducible. Further investigation determined that the database was corrupt in some way, as we could see a large number of errors in the MySQL logs. Fix the corruption on the database and/or exclude it from the backups until resolved by the MySQL DBA.

Simpana v10 – New ESD media released – Now includes SP4

With the release of Service Pack 4, a new ESD media release has also taken place. This media is marked September 2013 and includes SP4. It can be downloaded from Commvault’s Maintenance Advantage Portal.

Highly recommend it’s downloaded and all old media copies are destroyed.

Simpana 10 – Oracle iDA – Backup current controlfile via RMAN command line

Quick demo on how you can backup from command line using RMAN and still have this backup go via Simpana 10 and the Oracle iDA. This backup is a control file only backup, follow on from the GUI based example in my last post.

Simpana 10 documentation link covering this can be found here.

Contents of my backup.txt from screen cast on this post.

run {
allocate channel ch1 type 'sbt_tape'
backup current controlfile;
release channel ch1;


Simpana 10 – Oracle iDA – Configuration – Instance creation and GUI based backup control file test

Follow on from my last post, this is now the configuration of the instance in the GUI/console.

Next up we create a subclient to just backup the control file of the orcl instance and of course run the job immediately to demo that it works.

Simpana 10 Oracle iDA installation onto Linux client

Demo deployment of Simpana 10 Oracle iDA installation onto Linux client.

You’ll note I first check to see which user is running the pmon process for our database, in this case it’s “oracle”.

Next I change to the user oracle and determine the users primary group. As this group will be used for the installation. In this example it’s “oinstall”.

I’ll be posting another part to this, as the installation is merely the first step. Once installed you have to do some configuration from the Simpana console. i.e. create the oracle instance etc.

Commvault documentation covering the install above can be found here.

Simpana 10 Local uninstall of Simpana services on Linux

Demo of a Simpana 10 Local uninstall of Simpana services on Linux.

Note that I select the option only to remove the software/services on the client and not update the commserve about this removal. As I want to keep the backup history of my client in the commserve. This will enable me to reinstall the software with the same details on this client to continue my backups.

MediaAgent Installation on Linux – Simpana 10

Needed to install the Simpana 10 MediaAgent onto a Linux client in my test environment and I thought it might be a good idea to record and share.

The install is an interactive one using the media (DVD3).

As you can see in the video my freshly installed client still had it’s hostname associated with the localhost entry in the hosts file. The installer detects this and recommends you fix it. So I did.

In addition, I also fixed up the services file entries for 8400 and 8402. Installer will see these and not allow you to pick those ports during the install, so since I know this condition was going to happen next I edit these files too. That condition is going to be resolved in a future service pack, so you won’t need to do that.


MySQL backup via Simpana fails with Error Code 87:15

So you’ve just deployed the Simpana MySQL iDA and attempt your first backup, however get an error per below;

Error Code: [87:15]

Description: MySQL Database: [~client~] Data Backup Failed with MySQL Error: [~mysqldump: Got error: 1227: Access denied; you need the RELOAD privilege for this operation when doing refresh ~].

This failure is talking about the MySQL user that you configured in the GUI for the MySQL iDA. Basically the account lacks “RELOAD” privilege, so you should go fix it up before trying again.

Simpana 10 – SAP for Oracle backup failure

Came across an Simpana 10 SAP for Oracle iDA condition where the job would fail per below;

Error Code: [18:45]
Description: Snap Initialization failed with an error: [Backup Index Initialization failed. Please check the logs.]
Source: clientname, Process: backint_oracle

If you look into the $SAPDATA_HOMEsapbackup directory for the detail file associated with the failed backup you should also see something like below;

Rel 10.0.0(BUILD116) - CS=<commserve> CC=<clientname> retCode=1 bUpgradeFlag=208 upgradeTo9oTime=0
Got Mangled MediaAgent=<*ma*8400*8402> from Archive Manager
creating BCD dir=</opt/simpana/iDataAgent/jobResults/2/115/417/> failed with retCode=<-1>

BR0280I BRBACKUP time stamp: 2013-04-30 14.52.41
BR0279E Return code from '/sapmnt/OBK/exe/uc/rs6000_64/backint -u OBK -f backup -i /oracle/OBK/sapbackup/.belcejum.lst -t file -p /oracle/OBK/112_64/dbs/initOBK.utl -c': 2

This failure is indicative of a permissions error. i.e. Simpana installation path and/or jobResults  (if been placed outside of the Simpana installation path) have permissions that restrict the SAP user from writing. Since the SAP for Oracle backups are ran via a Unix SAP user account.